Date: Thu, 18 Jun 2009 10:17:09 -0400 From: Steve Polyack <korvus@comcast.net> To: geoff@apro.com.au Cc: freebsd-questions@freebsd.org Subject: Re: Configuring VLANs - Why is IP address require on NIC connected to Trunk? Message-ID: <4A3A4C65.1010003@comcast.net> In-Reply-To: <200906182345.43828.geoff@apro.com.au> References: <200906182345.43828.geoff@apro.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Geoff Roberts wrote: > I find I have to give the ext0 interface an IP address in order for routing > and packet filtering to work on the attached VLANs. > This shouldn't be the case. The "ext0" interface should not need an IP address for the two vlanX interfaces to function correctly. Are you sure you're setting the vlandev on the child interfaces? Perhaps you need to force the ext0 interface "up". If em0 is your external/trunk interface, you should have something like: ifconfig_em0="up" cloned_interfaces="vlan0 vlan1" ifconfig_vlan0 ="inet X.X.X.X netmask X.X.X.X vlan 0 vlandev em0 up" ifconfig_vlan1 ="inet X.X.X.X netmask X.X.X.X vlan 1 vlandev em0 up" After that, you should be able to simply filter on the vlan0 and vlan1 interfaces using pf.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A3A4C65.1010003>