netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: vlan@Scry.WANfear.com
Cc: netdev@oss.sgi.com
Subject: Re: [VLAN] VLAN patches
Date: Mon, 30 Sep 2002 09:19:39 -0700	[thread overview]
Message-ID: <3D98799B.9060008@candelatech.com> (raw)
In-Reply-To: D8B86D9BB607124BA1D54EDB7944DB0B140BC4@exchange.mabuhay

Dave Santucci wrote:
> Bjorn
> 	Since the data type for the vlan_id is specified as an "unsigned short",
> 	The comparison (vlan_id < 0) will always be false due to the range of the data
>  	type.
> 
> 	-ds
> 	
> 
> -----Original Message-----
> From: Andersson Björn [mailto:Bjorn.Andersson@ebc.ericsson.se] 
> Sent: Monday, September 30, 2002 1:24 AM
> To: netdev@oss.sgi.com
> Subject: [VLAN] VLAN patches
> 
> Hi,
> I hope you are the right receiver of 8021q-patches.
> We are running SuSe 8.0, i.e kernel 2.4.18.
> 
> - When addding several egress-mappings we get stuck in an eternal
> loop if they end up in the same hash-bucket, see vlan_dev.c.path.
> 
> - If we try to remove a vlan with VID 0, ifconfig stops working
> completly.
> We fixed it with vlan.c.patch.

Is there any reason to ever let someone add a VLAN of ID 0 in the first place?

Ben

> 
> 


-- 
Ben Greear <greearb@candelatech.com>       <Ben_Greear AT excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear

  reply	other threads:[~2002-09-30 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-30 15:55 [VLAN] VLAN patches Dave Santucci
2002-09-30 16:19 ` Ben Greear [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-30  8:23 Andersson Björn
2002-09-30  8:52 ` [VLAN] " Matti Aarnio
2002-09-30 16:02   ` Ben Greear

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D98799B.9060008@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=netdev@oss.sgi.com \
    --cc=vlan@Scry.WANfear.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).