Hi,
On Fri, 19 Jun 2009 12:16:18 am Nikos Vassiliadis wrote:
> 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.
> >
> > a) Is there a way to configure this so that I don't have to give ext0
done using ifconfig_em0_name="ext0" in rc.conf.
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.
You have to set up IP address to vlans, not main interface. It's the way
vlan's work.
Having 2 vlan's is like having
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
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.
a) Is there a way to configure this so that I don't have to give ext0 an IP
address?
Yes, you just have to "up" the interface:
ifconfig_em0="up
Hi,
I am currently using FreeBSD 7.2 - although the configuration below was
originally configured on FreeBSD 7.0.
I have a working VLAN configuration - two VLANS on one interface.
Let's call the interface ext0 and the VLANS bound to this interface vlan0 and
vlan1
The interface ext0 is actuall