Linux Advanced Routing and Traffic Control list
 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 05:13:33 +0000	[thread overview]
Message-ID: <marc-lartc-101262685732129@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101260332616001@msgid-missing>

I am not sure what you mean by that but ifconfig shows the correct
ip/netmask/broadcast for each ip.  Did I miss something?

David

On Fri, 1 Feb 2002 23:27:28 -0500
"Admin Nplus" <admin@nplus.ca> wrote:

> did you tell the linux box what ip is where on what side ?
> 
> ----- Original Message -----
> From: "David Koski" <david@kosmosisland.com>
> To: "LARTC" <lartc@mailman.ds9a.nl>
> Sent: Friday, February 01, 2002 5:41 PM
> Subject: [LARTC] proxy arp and routing
> 
> 
> > Hello,
> >
> > Given the network map below, I am able to ping any ip on all networks from
> the
> > linux box.  However, from the cisco router, I cannot ping past eth1 on the
> linux
> > box.  The reverse is also true; I cannot ping past eth0 from a host on
> LAN.
> > proxy-arp is enabled on the linux box and the route to a.b.c.0/24 is added
> to
> > the cisco router.  I haven't a clue why either way, I can only get to the
> far
> > side of the linux box but no further.
> >
> > On second thought, maybe this is not an application for proxy-arp.  Your
> > thoughts are appreciated.
> >
> >     T1 to ISP
> >         |
> >         | /30 net
> >         |
> > +----------------+
> > | cisco router   |
> > +----------------+
> >         | FastEthernet0/0
> >         | a.b.c.1/28
> >         |
> >  (possible switch/hub here in future)
> >  (ip range = a.b.c.1-15)
> >         |
> >         | a.b.c.2/28
> >         | eth0
> > +----------------+
> > |                |
> > |           eth1 |---a.b.c.16/24-public-net-----> LAN
> > |                |   (ip range = a.b.c.16-255)
> > | linux box      |
> > |           eth2 |---192.168.1.0/24-- *
> > |                | * (not revelant to discussion)
> > +----------------+
> >
> > David Koski
> > david@KosmosIsland.com
> > _______________________________________________
> > LARTC mailing list / LARTC@mailman.ds9a.nl
> > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
> >
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

  reply	other threads:[~2002-02-02  5:13 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 [this message]
2002-02-02 17:44 ` David Koski
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-101262685732129@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox