From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: routing problem with new subnet..
Date: Wed, 04 Dec 2002 04:36:09 +0000 [thread overview]
Message-ID: <marc-lartc-103897671902970@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103897073023358@msgid-missing>
: I have a debian (woody) box acting as router for my network and I am trying
: to setup a dmz (210.xxx.xxx.225/29).
<routing table snipped>
This is a classic case of a breaking a network in two with proxy ARP. You
can do this exactly as you indicate (assuming the xxx.xxx numbers are all
accurate).
: anyway, whenever a request comes in for one of the boxes in the dmz the
: gateway box doesn't seem to answer any arp requests for it. So the
: connection goes nowhere. How do i fix it? I've tried playing with arp proxy
: and manual arp entries to no avail. Do I need to add an extra route?
The routes look fine, according to the snipped routing table.
There are (at least) two ways to do it. I haven't documented the second
way yet...keep looking around but you can read up on one way to do it here
(with script and config file):
http://plorf.net/linux-ip/html/adv-proxy-arp.htm
One thing people frequently forget when using proxy ARP techniques is:
the upstream router (here at 210.xxx.xxx.141) needs to have
a /30 prefix length and a static route
OR
the upstream router needs to have a a /29 prefix length, and the
proxy ARPing device needs to proxy ARP for the "internal" network
I'd recommend using tcpdump on both eth0 and eth2 to determine where the
problem is.
-Martin
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-12-04 4:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 2:58 [LARTC] Re: routing problem with new subnet Craig Reeson
2002-12-04 4:36 ` Martin A. Brown [this message]
2002-12-04 7:58 ` Craig Reeson
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-103897671902970@msgid-missing \
--to=mabrown-lartc@securepipe.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.