All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Koski <david@kosmosisland.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] proxy arp and routing
Date: Sat, 02 Feb 2002 17:44:38 +0000	[thread overview]
Message-ID: <marc-lartc-101267190118380@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101260332616001@msgid-missing>

On Sat, 2 Feb 2002 10:19:13 +0100
Leen Besselink <leen@wirehub.nl> wrote:

> * David Koski (david@kosmosisland.com) wrote:
> > I am not sure what you mean by that but ifconfig shows the correct
> > ip/netmask/broadcast for each ip.  Did I miss something?
> > 
> maybe you could show us the routing table(s) ?
> also did you turn on ip forwarding (/proc/sys/net/ipv4/ip_forward) ?

That would be tough because I had to revert back to get it back working. 
Currently, the public block is routed arround the linux box instead of through
it, just to keep it going.  But it looked just as I would expect given the
ifconfig and /etc/sysconfig/* settings.

I have a howto on an alternate method of proxy arp'ing.  It uses identical
assignments on eth0 and eth1 instead of using different netmasks.  But it uses
static routes.  Maybe I'll try that.  But I would still like to know why the
other did not work.  Is it possible that with the method I tried, proxy arp is
not necessary and only interferes?

David
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

  parent reply	other threads:[~2002-02-02 17:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01 22:41 [LARTC] proxy arp and routing David Koski
2002-02-02  5:13 ` David Koski
2002-02-02 17:44 ` David Koski [this message]
2002-02-02 19:19 ` David Koski
2002-02-04 14:59 ` Ard van Breemen
2002-02-04 17:58 ` David Koski

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-101267190118380@msgid-missing \
    --to=david@kosmosisland.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.