FW: Curiosity in IPFW/Freebsd bridge. [more] 802.1q VLAN at fault?

[Nickolay A. Kritsky]

Hello asegu,

This one should work OK. But do not forget to put parent interfaces in
up and promisc mode in your rc.conf, otherwise you will not see any
vlan-bridging. 

Sunday, December 19, 2004, 11:33:57 PM, asegu at borgtech.ca wrote:

abc> Ok, the whole discussion to date led to how VLAN traffic wasn't being
abc> registered by IPFW in my system. I think that it'll probably be too late
abc> for a code change to fix my problem, so I'm going to go the route of
abc> changing the network configuration.

abc> I've rebuilt to 4.10 and.. And I had no luck there (IPFW _really_ doesn't
abc> see the traffic now!). On the other hand, I've read about vlan pseudo-dev
abc> and goten myself access to the switch's configuration.

abc> So tomorrow evening I plan on changing the vlan id used to 3, and then in
abc> freebsd, use the following configuration(and I post this to the list to
abc> see if anybody knows that this is going to fail)

fxp1 -->> router (uses ID 2)
fxp0 -->> switch (uses ID 2, will switch to ID 3)
abc> ifconfig vlan1 vlan 3 vlandev fxp0
abc> ifconfig vlan0 vlan 2 vlandev fxp1

abc> sysctl net.link.ether.bridge_cfg=vlan1,vlan0
abc> sysctl net.link.ether.bridge_ipfw=1


abc> Does anybody think this will allow IPFW to see the packets? or that this
abc> will outright fail?


abc> Thank you everybody,
abc> Andrew



-- 
Best regards,
;  Nickolay A. Kritsky
; SysAdmin STAR Software LLC
; mailto:nkritsky at star-sw.com