General Questions

I am getting this error repeatedly, and have searched as well, but found nothing relevant to my specific error/issue.

Here is my Setup.
ATT uVerse 12M connection, For those of you unfamiliar with uVerse this is an ISP/IPTV/VOIP package, that REQUIRES the use of a 2Wire "Residential Gateway"  which is really just a Router that has the QoS for the VOIP and IPTV setup already, the End user is unable to make very many configuration changes.
The Only way around this device is to use what they call DMZ plus.  A Network Device can be laced in this DMZ+ and is then assigned all traffic not bound for the IPTV and VOIP.

I have the latest Monowall in that DMZ+ running on a PIII with 256 Megs Ram. 
My CPU usage rarely gets above 10% even when VPN'd in (PPTP).

I continuously receive the following error

kernel: arp: 192.168.1.254 is on re0 but got reply from XX:XX:Xx:16:78:79 on rl0

Now here's the Rub.

My WAN is on rl0 and has been issued my Public IP via DCHP (this is the DMZ+ routine).
My LAN is re0.
192.168.1.254 is the IP address of the 2Wire uVerse Router, which is NOT inside my Network.
The MAC address in the error (XX:XX:Xx:16:78:79) is the MAC addres of the Same 2Wire Router.

I assume that WAN rl0 seeing XX:XX:Xx:16:78:79 is ok because that is the interface it is connected to as part of the DMZ+, what confuses me is why Monowall thinks 192.168.1.254 is "on rl0" which is the LAN.

I just thought of something while typing this.
The vlan on the rl0 is 192.168.1.0/24, I bet this is what's throwing Monowall off.

any thoughts?

In the meantime I will move the 2Wire Router to it's own subnet i.e. 192.168.2.254 and see if that alleviates it.

You got it figured.  The 192.168.1.x subnet is being seen on 2 interfaces, and that is triggering the error.  Change one of the networks, and it will go away.

Yup, worked.  Thanks

I guess I just had to write it out to see it...   

Thanks