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

From: Andrew Seguin (asegu_at_borgtech.ca)
Date: 12/26/04

  • Next message: James: "Receive path for ip_fastforward" 
    To: <freebsd-net@freebsd.org>
Date: Sun, 26 Dec 2004 19:10:29 +0100

    My apologies for not replying sooner.

    However, a few days before Christmas, I got the time to make the test and
    the news is... it works.

    A small curiosity however is that I had problem with the 'promisc' flag
    being turned off. I ended up creating a small startup script to set the
    sysctl and configure the netcards manually.

    I thank all who helped me get this working!
    Andrew

    -----Original Message-----
    From: Nickolay A. Kritsky [mailto:nkritsky@star-sw.com]
    Sent: Monday, December 20, 2004 7:32 PM
    To: asegu@borgtech.ca
    Cc: freebsd-net@freebsd.org
    Subject: RE: FW: Curiosity in IPFW/Freebsd bridge. [more] 802.1q VLAN at
    fault?

    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@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@star-sw.com
-- 
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.296 / Virus Database: 265.6.0 - Release Date: 12/17/2004
 
-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.296 / Virus Database: 265.6.4 - Release Date: 12/22/2004
 
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
  • Next message: James: "Receive path for ip_fastforward"