I've been troubleshooting proxy arp with m0n0wall 1.2b3 (last release of
m0n0wall based on FreeBSD4) because I am having some real-world problems
with it. On a test m0n0wall box I have set up the LAN interface with an
IP of 192.168.1.248 and I have set up proxy arp on the LAN interface
with an ip of 192.168.1.230. I only have one firewall rule on the LAN
interface and that is to accept all packets.

I am expecting the m0n0wall box to reply to ping attempts to the IP
address, however I am getting the following when pinging the IP:

segfault@virgil:~ $ ping -c 20 192.168.1.230
PING 192.168.1.230 (192.168.1.230) 56(84) bytes of data.
>From 192.168.1.248 icmp_seq=1 Destination Host Unreachable
>From 192.168.1.248 icmp_seq=2 Destination Host Unreachable
>From 192.168.1.248 icmp_seq=3 Destination Host Unreachable
>From 192.168.1.248 icmp_seq=4 Destination Host Unreachable
>From 192.168.1.248 icmp_seq=5 Destination Host Unreachable
>From 192.168.1.248 icmp_seq=6 Destination Host Unreachable
>From 192.168.1.248 icmp_seq=7 Destination Host Unreachable
>From 192.168.1.248: icmp_seq=8 Redirect Host(New nexthop: 192.168.1.230)
>From 192.168.1.248: icmp_seq=9 Redirect Host(New nexthop: 192.168.1.230)
>From 192.168.1.248: icmp_seq=10 Redirect Host(New nexthop:
192.168.1.230)
>From 192.168.1.248: icmp_seq=11 Redirect Host(New nexthop:
192.168.1.230)
>From 192.168.1.248: icmp_seq=12 Redirect Host(New nexthop:
192.168.1.230)
>From 192.168.1.248: icmp_seq=13 Redirect Host(New nexthop:
192.168.1.230)
>From 192.168.1.248 icmp_seq=14 Destination Host Unreachable
>From 192.168.1.248 icmp_seq=15 Destination Host Unreachable
>From 192.168.1.248 icmp_seq=16 Destination Host Unreachable

Is this normal behaviour?

Thanks
-- 
James Doherty - Systems Engineer
Zeald.com - Websites That Work!
Web: www.zeald.com | Ph: +64 9 415 7575