Date: Thu, 20 Mar 2014 16:30:01 GMT From: Karl Pielorz <kpielorz@tdx.co.uk> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/163803: vlan does not work Message-ID: <201403201630.s2KGU1Bh031436@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/163803; it has been noted by GNATS. From: Karl Pielorz <kpielorz@tdx.co.uk> To: bug-followup@FreeBSD.org, kes-kes@yandex.ru Cc: Subject: Re: kern/163803: vlan does not work Date: Thu, 20 Mar 2014 16:22:36 +0000 Hi, I stumbled across this PR the other day - having a similar issue setting up VLANs under 10.x in this case. After much head scratching I found, for example on a freshly installed, run up FBSD 10.x box: ifconfig bge1.100 create ifconfig bge1.100 192.168.0.20 netmask 255.255.255.0 [and equivalent on the other side] Doesn't work - you see ARP requests flying around - but no traffic is exchanged. However, doing: ifconfig bge1 up (i.e. Bringing up the 'parent' / underlying NIC on both machines) After a few seconds - everything 'works', and traffic does flow over the VLAN (i.e. ARP requests are answered etc.) Whether this is the same issue, whether it's a "bug" that the interface isn't brought 'up' when the vlan virtual interface is created - who knows. Similar thing happens for LAGG interfaces - unless you have a dummy: ifconfig_bge1="UP" In /etc/rc.conf - LAGG configs don't work either. Anyway, just thought I'd post a followup to this - incase this 'fixes' (or at least sheds light) on the original issue. -Karl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201403201630.s2KGU1Bh031436>