From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Does anyone have a working proxyARP setup?
Date: Sat, 09 Oct 2004 17:46:12 +0000 [thread overview]
Message-ID: <416823E4.A8CCD2D0@iswest.com> (raw)
In-Reply-To: <41676C12.72F7D09D@iswest.com>
Martin Volf wrote:
>
> gypsy wrote:
> ...
> > gypsy> ifconfig eth0 x.x.x.96 broadcast x.x.x.111 netmask
> > 255.255.255.240
> > gypsy> ifconfig eth1 x.x.x.96 broadcast x.x.x.111 netmask
> > 255.255.255.240
>
> I think you can't use x.x.x.96 here, because it is the address of your network
> x.x.x.96/28. Useable ip addresses are .97 - .110. And you can't have the same
> ip address and netmask on two interfaces. Use maybe 'netmask 255.255.255.255'
> on one of them.
> --
> Martin
I have tried all IPs in the range, but I have not tried different
netmasks. Thanks for that tip.
Could you please post the output of 'route -n', 'ip route' and 'ip neigh
show' as well as any 'ip route [add|del|*]' commands you run?
I really believe that either the kernel thinks there are spoofed IPs or
- most likely - that my routing table is junk.
Here is a quote from http://www.sjdjweis.com/linux/proxyarp/ which is
why I set both the same:
> After you have the above steps done, you will need to configure your network cards. This step should be done off of the
> network since you may end up with some conflicting addresses. Give two NIC's identical IP addresses, subnet masks, and
> gateways. The IP you choose needs to be an unused address on your network. In my case, I used x.x.x.98, since my router is
> at x.x.x.97. You could actually use about any address on the wire that isn't in use.
gypsy
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-10-09 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-09 4:41 [LARTC] Does anyone have a working proxyARP setup? gypsy
2004-10-09 8:05 ` Martin Volf
2004-10-09 17:46 ` gypsy [this message]
2004-10-12 13:33 ` gypsy
2004-10-12 16:55 ` Martin Volf
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=416823E4.A8CCD2D0@iswest.com \
--to=gypsy@iswest.com \
--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.