From: Ard van Breemen <ard@kwaak.net>
To: lartc@vger.kernel.org
Subject: [LARTC] ip routing problems in 2.4.20
Date: Mon, 05 May 2003 11:09:50 +0000 [thread overview]
Message-ID: <marc-lartc-105213310523718@msgid-missing> (raw)
Hi,
Has anybody noticed that when:
ip addr add 192.168.0.1/32 dev eth0
ip route add 192.168.0.2/32 dev eth0
The system will not respond to arprequests from 192.168.0.2, even
when rp_filter=0, proxy_arp=1, etc...
I will investigate it further at another time, but this has
caused me a lot of headaches... Grrr...
--
mail up 170+00:33, 7 users, load 0.16, 0.22, 0.17
mistar1 up 28+18:37, 17 users, load 0.22, 0.08, 0.04
Let your government know you value your freedom: sign the petition:
http://petition.eurolinux.org
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-05-05 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 11:09 Ard van Breemen [this message]
2003-05-05 11:21 ` [LARTC] ip routing problems in 2.4.20 ulrich schwarz
2003-05-05 12:28 ` Ard van Breemen
2003-05-05 21:07 ` Julian Anastasov
2003-05-06 10:52 ` Ard van Breemen
2003-05-06 11:42 ` Julian Anastasov
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=marc-lartc-105213310523718@msgid-missing \
--to=ard@kwaak.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox