From: Roberto Arcomano <berto@fatamorgana.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proxy arp bug on shaper device
Date: Tue, 18 Sep 2001 19:46:58 +0200 [thread overview]
Message-ID: <01091819465801.01127@berto.casa.it> (raw)
> If this is true then you have to provide support for all
> other devices, for example, tunnels.
Yes, unfortunately I tried but without success to extend patch to all that: I
need some info to do it (particolary I cannot understand how extract
"priv->dev" from a unknown device cause each (for each device) could be
different.....)
The common for such setups is
> that asymmetric routing is used. OTOH, your change drops the ARP
> probe without updating the neighbour state. BTW, do you see any
> incoming traffic on the shaper device?
There should not be incoming traffic from shaper device (I never saw it).
Thank you for your help
Roberto Arcomano
> Regards
>
> --
> Julian Anastasov <ja@ssi.bg>
-------------------------------------------------------
next reply other threads:[~2001-09-18 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 17:46 Roberto Arcomano [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-18 17:46 [PATCH] proxy arp bug on shaper device Roberto Arcomano
2001-09-18 12:11 Julian Anastasov
2001-09-18 9:23 Roberto Arcomano
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=01091819465801.01127@berto.casa.it \
--to=berto@fatamorgana.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox