Re: Disabling VLAN_HWTAGGING

From: Jacob S. Barrett (jbarrett_at_amduat.net)
Date: 03/27/04

  • Next message: leo luis: "MPD multilink with modems" 
    To: Ruslan Ermilov <ru@freebsd.org>
Date: Sat, 27 Mar 2004 08:48:37 -0800

    On Saturday 27 March 2004 07:53 am, Jacob S. Barrett wrote:
    > Well with a new "correct" MAC that pings go back and forth just fine now.
    > I will back out all my changes and see if they still work with the hardware
    > tagging/detagging enabled.

    OK, with the hardware support re-enabled the frame now enters the driver. It
    is detected as VLAN frame and sent to VLAN_INPUT_TAG. The frame is then
    delivered via lower hook to the ng_vlan where it doesn't match the vlan tag
    so it goes out the nomatch hook. I guess with the VLAN tag stripped from the
    frame that ng_vlan can't match it. Is this the expected behavior with
    ng_vlan? I can just comment out the VLAN stripping line in the driver if it
    is the expected behavior. That isn't a big deal really.

    I haven't done a whole lot with the network interface drivers other than a few
    minor fixes here and there, but would it be hard to add some sort of flag to
    enable/disable the tag stripping via ifconfig? I was thinking that could be
    down through a "linkx" flag right? If the driver got the say "link1" it
    would down the interface, set clear the stripping config bits, and then re-up
    the interface. Or would this be better handled by a sysctl option? Does
    that sound safe and do-able? 

    -- 
Jacob S. Barrett
jbarrett@amduat.net
www.amduat.net
"I don't suffer from insanity, I enjoy every minute of it."
_______________________________________________
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: leo luis: "MPD multilink with modems"

    Relevant Pages

    • Re: PATCH: VLAN support for 3c59x/3c90x
      ... > the MTU change information is given to the driver after it is already ... MTU change need not occur while the interface is up. ... but receiving packets not wholly contained in a single frame is SO ...
      (Linux-Kernel)
    • Re: Direct Copying To Share Memory In NDIS ProtocolReceive
      ... frame that is transmitted to the miniports via the protocol must ... Since the frame slots are limited, I do not want to try to ... one driver using IRp that is pended, ... is a count of the number of frame slots in my shared-by-everyone ...
      (microsoft.public.development.device.drivers)
    • Re: Direct Copying To Share Memory In NDIS ProtocolReceive
      ... access the buffer. ... one driver using IRp that is pended, ... Another concern is locking memory. ... frame that is transmitted to the miniports via the protocol must ...
      (microsoft.public.development.device.drivers)
    • Re: URGENT - BugCheck, STOP: 0x0000001E (0xC0000005, 0xA002FB6D, 0x00000000, 0x000D0100)
      ... Buggy device driver or system service. ... Disabling memory caching of the BIOS might also resolve the error. ... > This is a very common bugcheck. ... Frame IP not in any known module. ...
      (microsoft.public.windows.server.general)
    • Re: nested vlans and ethernet frame size
      ... setting maximum ethernet frame size in freebsd? ... 1518 does that not imply at you require hardware that supports jumbo ... frames to do VLAN tag nesting? ...
      (freebsd-net)