From owner-freebsd-bugs@freebsd.org Thu Aug 6 22:53:58 2015 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1DBA59B5E07 for ; Thu, 6 Aug 2015 22:53:58 +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 mx1.freebsd.org (Postfix) with ESMTPS id 0232E1A6D for ; Thu, 6 Aug 2015 22:53:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t76Mrvol086694 for ; Thu, 6 Aug 2015 22:53:57 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 202144] Routing stops working when we create a new vlan Date: Thu, 06 Aug 2015 22:53:58 +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: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: gondim@bsdinfo.com.br X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- 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: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Aug 2015 22:53:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202144 Bug ID: 202144 Summary: Routing stops working when we create a new vlan Product: Base System Version: 10.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: gondim@bsdinfo.com.br Let me illustrate a network topology, to tell where the problem occurs: PC station: 192.168.8.253/24 (FreeBSD 10.2-PRERELEASE) Router: 192.168.8.177/24 and 10.254.215.1/24 (FreeBSD 10.2-RC2) router(CPE): 10.254.215.188/24 (a customer) >From Router: =========== # ifconfig vlan201 vlan201: flags=8843 metric 0 mtu 1500 options=103 ether 70:71:bc:87:31:2d inet 10.254.215.1 netmask 0xffffff00 broadcast 10.254.215.255 inet6 fe80::7271:bcff:fe87:312d%vlan201 prefixlen 64 scopeid 0x1a nd6 options=21 media: Ethernet autoselect (1000baseT ) status: active vlan: 201 parent interface: em0 >From PC station (192.168.8.253): =============================== # ping -c 5 10.254.215.188 PING 10.254.215.188 (10.254.215.188): 56 data bytes 64 bytes from 10.254.215.188: icmp_seq=0 ttl=127 time=1.012 ms 64 bytes from 10.254.215.188: icmp_seq=1 ttl=127 time=0.864 ms 64 bytes from 10.254.215.188: icmp_seq=2 ttl=127 time=1.084 ms 64 bytes from 10.254.215.188: icmp_seq=3 ttl=127 time=1.618 ms 64 bytes from 10.254.215.188: icmp_seq=4 ttl=127 time=1.006 ms --- 10.254.215.188 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.864/1.117/1.618/0.261 ms It works perfectly. Now I'm going on the router and I just create a new vlan 202. >From Router: =========== # ifconfig vlan202 create # At that moment my PC station stops to ping the IP 10.254.215.188. >From PC station (192.168.8.253): =============================== # ping -c 5 10.254.215.188 PING 10.254.215.188 (10.254.215.188): 56 data bytes --- 10.254.215.188 ping statistics --- 5 packets transmitted, 0 packets received, 100.0% packet loss For all work again I need to restart the router. I don't know if I could correctly explain the problem. -- You are receiving this mail because: You are the assignee for the bug.