From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Proxy ARP and UDP
Date: Mon, 20 Feb 2006 18:49:09 +0000 [thread overview]
Message-ID: <43FA0F25.93FC4722@iswest.com> (raw)
In-Reply-To: <925A849792280C4E80C5461017A4B8A20320BA@mail733.InfraSupportEtc.com>
Greg Scott wrote:
> I have 2 relevant interfaces. eth0 is external, eth1 is internal. My
> internal LAN is 10.10.10.0/24. My External range is 1.2.3.0/27 (dummied
> up). I have an H.323 videoconference device inside my internal LAN, but
> at IP Address 1.2.3.11/27. (IP Address dummied up.) I want to proxy
> ARP this device.
>
> My questions - was proxy ARP broken in the 2.4.27 days? Why doen't
> tcpdump show me packets on both interfaces of the firewall? Am I
> missing a setup ingredient someplace? Should the default GW on that
> H.323 device be .2 (the firewall) or .1 (the Internet router)? Does
> mixing NAT and proxy ARP create problems? Should I put the H.323 device
> in its own little DMZ?
>
> Thanks
>
> - Greg Scott
No, not broken; proxy ARP works fine in 2.4.25 - .32.
You should have a look at Martin Brown's proxy ARP script
http://yesican.chsoft.biz/lartc/proxy-arp.sh
and its config file
http://yesican.chsoft.biz/lartc/proxy-arp.conf
but I bet the problem is rp_filter.
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-02-20 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 13:15 [LARTC] Proxy ARP and UDP Greg Scott
2006-02-20 18:49 ` gypsy [this message]
2006-02-21 2:51 ` Greg Scott
2006-02-26 4:55 ` Greg Scott
2006-02-26 21:40 ` gypsy
2006-02-27 12:28 ` Greg Scott
2006-04-04 23:23 ` Greg Scott
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=43FA0F25.93FC4722@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.