Re: sysctl net.link.vlan.link.proto

7;t ever sure if that was a true win, so I didn't contrib them. I could dig them up if you're really interested in spiffing up the VLAN code. ;-) - Steve -- C. Stephen Gunn <[EMAIL PROTECTED]> | Waterspout Communications, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED]

No Subject

ial ARP who-has broadcasts were lost, which could confuse ARP handling sometimes, when there was an IP address conflict. Unfortunately I no longer work for Purdue U where I did the vlan stuff, and had a testing lab setup.. - Steve -- C. Stephen Gunn <[EMAIL PROTECTED]> | Waterspout Co

Re: 802.1q vlans and STABLE

On Sat, 24 Feb 2001 12:13:03 EST, Mike Tancsa wrote: > At 11:17 AM 2/24/2001 -0500, C. Stephen Gunn wrote: > > >2/3 of our traffic started showing up on the wrong logical network. > > How did you work around it ? Or were you able to ? We had to disable CEF on those subnets.

Re: How to send arp request with no other traffic

which inspecting the kernel routing and arp table currently doesn't. - Steve -- C. Stephen Gunn <[EMAIL PROTECTED]> | Waterspout Communications, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message

Re: How to send arp request with no other traffic

ddress to an layer-3 broadcast address and voila, amplified responses. :-( - Steve -- C. Stephen Gunn <[EMAIL PROTECTED]> | Waterspout Communications, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message

Re: Problems with VLAN and natd.

gn conversation with the other projects _before_ integration into FreeBSD. - Steve -- C. Stephen Gunn <[EMAIL PROTECTED]> | Waterspout Communications, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message

Re: Problems with VLAN and natd.

Yup. I'd prefer to see FreeBSD take the higher-road and strive to be compatible and cooperative whenver possible. Instead of continued isolation, divergance, and proprietization. Hey, I don't even currently run Net/OpenBSD. ;-) - Steve -- C. Stephen Gunn URL: http:/

Re: 'no memory for rx list'

low syslogd to filter/combine/report them on your console. I'm sure you already know this, you could increase NBMCLUSTERS and friends in your kernel config, or at boot time. (For posterity in the list archives). - Steve -- C. Stephen Gunn URL: http://www.waters

Re: Problems with VLAN and natd.

ng planning, thought, and most importantly coordination with the other BSDs when possible. - Steve -- C. Stephen Gunn URL: http://www.waterspout.com/ WaterSpout Communications, Inc.Email: [EMAIL PROTECTED] 427 North 6th Street Phone: +1 765.742.6628 Laf

Re: Problems with VLAN and natd.

On Tue, 02 Jan 2001 10:02:20 MST, Wes Peters wrote: > Sure, but it would be nice to take over ARP too. FWIW. Jeoren <[EMAIL PROTECTED]> was looking at the NetBSD media-independant arp code. I'm not sure what he learned. - Steve -- C. Stephen Gunn

Re: Problems with VLAN and natd.

interfaces. - Steve -- C. Stephen Gunn URL: http://www.waterspout.com/ WaterSpout Communications, Inc.Email: [EMAIL PROTECTED] 427 North 6th Street Phone: +1 765.742.6628 Lafayette, IN 47901 Fax: +1 765.742.0646 To Unsu

Re: Problems with VLAN and natd.

f someone does the work to move EthII into netgraph, I can > certainly contribute a SNAP/LLC module, and maybe even extensions to > ifconfig so you can use it. ;^) If we continue to dicuss this, and this is the correct direction to head, I'd volunteer to take a

Re: Problems with VLAN and natd.

oesn't make much sense. If EthII and VLANS belong in Netgraph, then the plain old ethernet link code belongs there as well. Having different interfaces for similar operations makes little sense. You eventually end up with two protocol stacks. One that uses the legacy infrastructure, and futur

Re: Problems with VLAN and natd.

ility issues involved. If this discussion is non-casual, we should eventually migrate it over to -arch. - Steve -- C. Stephen Gunn URL: http://www.waterspout.com/ WaterSpout Communications, Inc.Email: [EMAIL PROTECTED] 427 North 6th Street

Re: Problems with VLAN and natd.

t the need for current work-arounds like if_vlan, and if_ef, and perhaps even if_tap. - Steve -- C. Stephen Gunn URL: http://www.waterspout.com/ WaterSpout Communications, Inc.Email: [EMAIL PROTECTED] 427 North 6th Street Phone: +1 7

Re: Problems with VLAN and natd.

On Fri, Dec 29, 2000 at 05:59:19PM +0100, Andrea Franceschini wrote: > > There is a patch for the xl driver, which can be found on > > http://www.physics.purdue.edu/~csg/FreeBSD/xl_vlan.patch Eek! That's still up on the net? I left Purdue Physics back in August.. ;-) > flags=8843 mtu 1496 > >