6.0-BETA3 bge0 and vlans

From: Gavin Atkinson (gavin.atkinson_at_ury.york.ac.uk)
Date: 08/30/05

  • Next message: Sam Leffler: "Re: ath bridge panic" 
    To: freebsd-current@freebsd.org
Date: Tue, 30 Aug 2005 18:23:49 +0100

    Hi,

    I'm having no success setting vlans up on a bge interface. Can anyone
    confirm they work? I've got no problems using them on fxp interfaces,
    so I'm pretty sure it's not user error... Everything looks good:

    bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
            options=1a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
            inet6 fe80::209:3dff:fe12:6c06%bge0 prefixlen 64 scopeid 0x1
            inet x.y.12.120 netmask 0xfffffe00 broadcast x.y.13.255
            ether 00:09:3d:12:6c:06
            media: Ethernet autoselect (100baseTX <full-duplex>)
            status: active
    [bge1/lo0 snipped]
    vlan76: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
            inet x.y.76.59 netmask 0xfffffe00 broadcast x.y.77.255
            inet6 fe80::209:3dff:fe12:6c06%vlan0 prefixlen 64 scopeid 0x4
            ether 00:09:3d:12:6c:06
            media: Ethernet autoselect (100baseTX <full-duplex>)
            status: active
            vlan: 76 parent interface: bge0

    ... but I can get no packets through the vlan interface (the parent
    interface works as expected). Can anyone actually confirm that vlans
    work with bge cards? My card is a BCM5704 (vend=0x14e4, prod=0x1648,
    rev=0x03)

    I've also just discovered that ifconfig is sensitive to the order that
    the options "vlandev" and "vlan" are passed to it.

    wiggum# ifconfig vlan76 vlandev bge0 vlan 76
    ifconfig: must specify both vlan tag and device
    wiggum# ifconfig vlan76 vlan 76 vlandev bge0
    wiggum#

    This to me seems counter-intuitive. Due to the design of ifconfig this
    doesn't seem to be easy to change, so maybe it should be documented?

    Thanks,

    Gavin
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Sam Leffler: "Re: ath bridge panic"

    Relevant Pages

    • Cisco 877w: Fa0-3 Interfaces up but no traffic passes
      ... Data Vlan101 only, no voice vlan required, WPA ... output errors, 0 collisions, 0 interface resets ... switchport trunk native vlan 101 ... bridge-group 101 subscriber-loop-control ...
      (comp.dcom.sys.cisco)
    • Re: 2600 router + 2924 switch and vlans
      ... I can route from a port ... assigned to the def vlan, but not from any port assigned to vlan 2 ... interface FastEthernet0/0 ... switchport trunk encapsulation isl ...
      (comp.dcom.sys.cisco)
    • Re: kern/109815: wrong interface identifier at pfil_hooks for vlans + if_bridge
      ... It is cleared when an mbuf chain is passed to another entity which may consume the frame in that mbuf chain, in case the entity re-enters ether_inputwith the same mbuf chain for local delivery (e.g. bridge, netgraph, vlan). ... "logical" interface. ...
      (freebsd-net)
    • Still cannot Route.
      ... interface FastEthernet0/0 ... description Blue Haven Servers VLAN 10 ...
      (comp.dcom.sys.cisco)
    • [NEWS] ARP Attacks Access Point Memory Exhaustion
      ... Get your security news from a reliable source. ... the command L2-FILTER BLOCK-ARP to each radio interface. ... interfaces in one VLAN and places wireless clients into different VLANs ... bridge-group 1 spanning-disabled ...
      (Securiteam)