Yep, proxyarp just tells everything to send that IP to you, doesn't bring up the IP on the box. You can always port forward the icmp traffic (hrm, does that work in pfsense?) to your internal box if you want ping's to reply. "other" is for traffic that is just routed to you - a pppoe /29 segment would be a good example of this - it's sole intention is to be able to use it in port forward statements ;) I want to rework some of this code post 1.0, but doing it right is rather time consuming.
--Bill On 9/18/06, Chris Godwin <[EMAIL PROTECTED]> wrote:
You've got to be kidding me. Hahahaha. All works and is good. Thanks. Cannot wait till carp doesn't kernel panic bsd. Chris Godwin Linux/Unix Consultant Network Logistic, Inc. Get help at http://www.networklogistic.com/help -----Original Message----- From: Scott Ullrich [mailto:[EMAIL PROTECTED] Sent: Monday, September 18, 2006 5:49 PM To: [email protected] Subject: Re: [pfSense-discussion] Proxy arp On 9/18/06, Chris Godwin <[EMAIL PROTECTED]> wrote: > The test was setting a proxy arp or other type ip and simply pinging it. > In the case where my behind is in a mess of hornets (work) I'm simply > using a laptop, switch and pfsense machine. In the other case (home) I'm > also very simply using a cable modem, dell machine (pfsense), a netgear > switch and a clone workstation. In either case I cannot ping from the > locallan proxyarp ip's. I just tested at my bosses house and set a proxy > arp and other type virtual ip and am not able to ping it now. Proxyarp does not respond to ICMP traffic. Simply test the port forward or whatever you are trying to setup.
