From owner-freebsd-bugs@freebsd.org Sun Nov 18 00:20:31 2018 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF2E1110C8CD for ; Sun, 18 Nov 2018 00:20:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 8966188786 for ; Sun, 18 Nov 2018 00:20:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 4D63A110C8CC; Sun, 18 Nov 2018 00:20:30 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2B691110C8C9 for ; Sun, 18 Nov 2018 00:20:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C079588785 for ; Sun, 18 Nov 2018 00:20:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id DB7701A5E3 for ; Sun, 18 Nov 2018 00:20:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id wAI0KSI3055419 for ; Sun, 18 Nov 2018 00:20:28 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id wAI0KSZb055410 for bugs@FreeBSD.org; Sun, 18 Nov 2018 00:20:28 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 233283] IPv6 routing problem when using FreeBSD as a VPS at a cloud provider Date: Sun, 18 Nov 2018 00:20:28 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: peo_s@incedo.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Rspamd-Queue-Id: 8966188786 X-Spamd-Result: default: False [-0.38 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_SHORT(-0.38)[-0.375,0]; ASN(0.00)[asn:10310, ipnet:2001:1900:2254::/48, country:US] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2018 00:20:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233283 Bug ID: 233283 Summary: IPv6 routing problem when using FreeBSD as a VPS at a cloud provider Product: Base System Version: 11.2-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: peo_s@incedo.org Hi I have recently seen a rising problem when I replaced a Linux server with FreeBSD. This is because it is used as a VPS at the cloud provider RamNode. They (i.e RamNode) have provided an IPv6 gateway that is outside my allotted /64 block. They have a /48 at each DC. And the IPv6 gw is outside my /64. So FreeBSD requires me to increase the net mask from /64 to /48 for internet access to work. They also state this here... https://clientarea.ramnode.com/knowledgebase.php?action=3Ddisplayarticle&id= =3D44 This means I have a problem to communicate with a set of servers over IPv6 related to the mask we have specified. I unfortunately now have a sever tha= t I can use IPv4 only to because of this. Linux and windows obviously accept having gateways outside its network scop= e. Why, I do not know... I of course think this is wrong. OpenBSD and FreeBSD don=E2=80=99t accept this handling of gateways outside the net mask scope= =E2=80=A6 If it is RFC compliant or not, I do not know. I have not checked=E2=80=A6. And I think F= reeBSD is actually behaving right.=20 I logged a case at RamNode... The problem is that RamNode states that most cloud providers behaves in the same way. So now it just became a problem if we want to use FreeBSD at the cloud providers with IPv6. RamNode stated: =E2=80=94snip=E2=80=94 This kind of setup does appear to be odd but if you search you will see the= re are a number of large providers that take the same approach. Users on these other providers also experience issues with the gateway being outside of the subnet on BSD. Unfortunately I do not have specific knowledge as to why our configuration is this way but it does appear to be common. =E2=80=94snip=E2=80=94 So=E2=80=A6 I am working primarily with security. As I do not see any immed= iate security issue doing this, is it possible to add an rc.conf flag to accept gateways outside the net-mask scope? Otherwise, FreeBSD is not the horse to= bet on for the future as VPS:es on the internet. /Peo --=20 You are receiving this mail because: You are the assignee for the bug.=