From: Mike Ireton <mike@WillitsOnline.Com>
To: Joris <joriske@gmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: routing broadcast mac ethernet frames
Date: Sat, 05 Feb 2005 14:21:43 -0800 [thread overview]
Message-ID: <420546F7.3010907@WillitsOnline.Com> (raw)
In-Reply-To: <afcf620205020423242dbf2877@mail.gmail.com>
Joris -
Very astute of you. Yes, you're right on the money and is a recurring
'compatibillity' issue between wireless and wired networks.
You can try using the ebtables kernel patch, which will allow you to do
address translation on the ethernet destination address, so if you see a
broadcast frame, you can transparently re-write it with your nic's
ethernet address, thus your ip stack will receive and process the frame.
There may be some undesired side effects of doing this, depending on
your specfic configuration and goals, but since you got this far I'm
sure you can probbly use tcpdump effectively and hash those out.
Mike
>This is why: certain embedded devices, such as some wifi accesspoints
>and some DSL modems, seem to have a common bug/feature.
>They keep an arp table, and any traffic from any host not in that
>table is re-sent with a broadcast mac address (ff:ff:ff:ff:ff:ff).
>
>As far as I know, linux will happily accept packets like that when
>they're adressed to itself, but will not route them. This makes
>communication impossible in certain setups with linux as a router.
>A lot of people, especially wireless communities, are (knowingly or
>more likely unknowningly) suffering from this problem.
>
>Of course, those devices are buggy and should use ARP, but making
>linux 'compatible' is a lot easier than getting multiple hardware
>manufacturers to rewrite their firmware.
>
>
prev parent reply other threads:[~2005-02-05 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-05 7:24 routing broadcast mac ethernet frames Joris
2005-02-05 22:21 ` Mike Ireton [this message]
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=420546F7.3010907@WillitsOnline.Com \
--to=mike@willitsonline.com \
--cc=joriske@gmail.com \
--cc=netfilter@lists.netfilter.org \
/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