All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Rusko <rusko@sunsite.mine.nu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Accepting packets with frame dest.addr. ff:ff:ff:ff:ff:ff
Date: Fri, 23 Apr 2004 08:50:21 +0000	[thread overview]
Message-ID: <4088D8CD.0@sunsite.mine.nu> (raw)
In-Reply-To: <4087740E.5050008@sunsite.mine.nu>

Hi Tony,

that traffic is generated by a wireless access point (Prism GT chipset, 
802.11g) and when it is used as "client bridge" it acts as a proxy ARP 
device. I think, there is a bug in a firmware, because it doesn't do an 
ARP request for IP addresses which it doesn't know and simply send IP 
packet in broadcasted ethernet frame. This bug makes also proxy ARP on 
router (which is right behind that client bridge) rather problematic, 
but not impossible (under current IP addressing scheme).

Temporarily, I workarounded this by Frame Diverter (which replace 
incorrect ff:ff... address with MAC address of router's interface) and 
now IP stack in kernel happily routes all packets.

After a new firmware release (I hope, that there will be any) I will 
switch to proxy arp.

Thank you very much.

    Best Regards

         mARTin

Tony Wasson wrote:
> Martin Rusko wrote:
> 
>> Hi all,
>>
>> do anybody know, whether is it possible to route packets incoming to 
>> ethernet interface as broadcasts?
>>
>> ~~~~~|WirelessDevice/WD|-----eth0-|LinuxRouter/RT|-eth1---(10.18.63.0/24)
>>
>> tcpdump: listening on eth0
>> 0:a:e6:ac:e8:7a ff:ff:ff:ff:ff:ff 98: 192.168.7.11 > 10.18.63.249: 
>> icmp: echo request (DF)
>> 0:a:e6:ac:e8:7a ff:ff:ff:ff:ff:ff 98: 192.168.7.11 > 10.18.63.249: 
>> icmp: echo request (DF)
>>
>> Please notice, that echo request packets are in ethernet frames, 
>> heading to broadcast address (ff:ff:ff:ff:ff:ff).
>>
>> Linux kernel seems to be, that refuse to route such packets (not 
>> intented for the MAC address of eth0 interface). But that interface 
>> received that packets, as seen in running tcpdump session. When that 
>> frames has "correct" MAC addresses, I mean destination is not a 
>> broadcast address, the same packet (source IP, destination IP) is 
>> routed without any problem.
>>
>> Do you have any explanation, for this? Or better, does any linux 
>> networking guru know some magic, how to make linux kernel start 
>> routing also broadcasted packets?
>>
>> Any help will be much appreciated. Also, when more info, why I see 
>> such packets is needed, I'm ready to serve.
>>
>>          Best regards
>>
>>               mARTin
>>
> 
> Hi Martin,
> 
> Routers are usually installed to seperate broadcast domains. They really 
> don't *LIKE* to forward broadcasts. I am imagining that this is a really 
> broken TCP/IP stack you are working with. Just for kicks, do you see 
> ARPs right before these echo requests? If so, proxy ARP would help 
> deliver your traffic.
> 
> Can you reveal more about what device is sending this interesting 
> traffic? You may be able to set an ARP entry for 10.18.63.249 on the 
> crazy network device as the linux box and "force" things to work.
> 
> Tony Wasson

-- 
Martin Rusko
PhD student
Department of Automation and Measurement
Faculty of Mechanical Engineering
Slovak University of Technology
--
E-mail: rusko@sunsite.mine.nu
Web:    http://sunsite.mine.nu/~rusko
--
motto: We are Microsoft! Resistance is futile. Open your
        source code and prepare for assimilation.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2004-04-23  8:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22  7:28 [LARTC] Accepting packets with frame dest.addr. ff:ff:ff:ff:ff:ff for routing Martin Rusko
2004-04-22 17:42 ` [LARTC] Accepting packets with frame dest.addr. ff:ff:ff:ff:ff:ff Tony Wasson
2004-04-23  8:50 ` Martin Rusko [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=4088D8CD.0@sunsite.mine.nu \
    --to=rusko@sunsite.mine.nu \
    --cc=lartc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.