From: daniel.neri@sigicom.com (Daniel Néri)
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: question about bridging code.
Date: Thu, 30 Jan 2003 15:22:00 -0000 [thread overview]
Message-ID: <wkbs1ybra4.fsf@sigicom.com> (raw)
In-Reply-To: <NDBBICPJMKAJHBBNFIGPCECNGNAA.bguckel@cisco.com>
"bill guckel" <bguckel@cisco.com> writes:
> I'm hoping someone can answer a question about the function
> bridge_input() in net/tcpip/current/src/sys/net/if_bridge.c.
[code snipped]
> My question concerns the the passing of 'ether_dhost' to
> 'bridge_rtupdate()'. Why not 'ether_shost' ? This would seem to me
> (not a bridging expert) be a more important address to learn.
It seems you are right.
> Note that I may be using old code since it's been a while since I
> took new source.
As far as I can see, this bug still exists in recent source. Though it
was fixed in the original code two years ago:
http://www.openbsd.org/cgi-bin/cvsweb/src/sys/net/if_bridge.c.diff?r1=1.48&r2=1.49&f=h
Regards,
--
Daniel Néri, Sigicom AB, Sweden
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-01-30 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 15:09 [ECOS] " bill guckel
2003-01-30 15:22 ` Daniel Néri [this message]
2003-01-30 15:48 ` [ECOS] " Jonathan Larmour
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=wkbs1ybra4.fsf@sigicom.com \
--to=daniel.neri@sigicom.com \
--cc=ecos-discuss@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).