Jagerhill97
asked on
Sonicwall Answering ARP requests on LAN
I have a Sonicwall 4060 running 2.5 OS Enhanced.
All the settings appear to be working except for one huge problem.
The Sonicewall LAN port is answering ARP requests on the LAN side.
I have a server sending out and ARP for 10.10.10.2 and the Sonicwall is responing "that's me" even though the Sonicwall is 10.10.10.1.
Any ideas?
All the settings appear to be working except for one huge problem.
The Sonicewall LAN port is answering ARP requests on the LAN side.
I have a server sending out and ARP for 10.10.10.2 and the Sonicwall is responing "that's me" even though the Sonicwall is 10.10.10.1.
Any ideas?
http://secunia.com/advisories/11026/
not sure if that's relevant to your prob or not. Is that what you're experiencing?
not sure if that's relevant to your prob or not. Is that what you're experiencing?
ASKER
The issue is similar except the ARP requests and response are on the LAN side. The other strange thing is both the Sonicwall and Server that is being ARPd and the machine that is sending the request are on the same subnet which by all reasoning should never happen.
I'm not extremely familiar with SonicWall, but a couple thoughts:
-Do you have any Network Address Translation configured (NAT)? If you have a NAT for 10.10.10.2 that would cause the SonicWall to answer the ARP.
-SonicWall has a bridging mode. That means that it is able to "secure" traffic between the same subnet. So if 10.10.10.3 tries to talk to 10.10.10.2 the firewall (10.10.10.1) will get in the middle. Look for any bridging options and shut it off.
-Make sure your netmask on the internal interface is correct. I assume it should be 255.255.255.0?
Shane
-Do you have any Network Address Translation configured (NAT)? If you have a NAT for 10.10.10.2 that would cause the SonicWall to answer the ARP.
-SonicWall has a bridging mode. That means that it is able to "secure" traffic between the same subnet. So if 10.10.10.3 tries to talk to 10.10.10.2 the firewall (10.10.10.1) will get in the middle. Look for any bridging options and shut it off.
-Make sure your netmask on the internal interface is correct. I assume it should be 255.255.255.0?
Shane
ASKER
I though of ther bridging mode and disabled it but never completed implementing it because of the issues that arose.
There is no NAT for the server in question.
There is no NAT for the server in question.
ASKER
There is a bug in the 2.5 Enchanced Firmware. I received the following information from Soniceall FINALLY
"If the public server wizard is used for to create the "Public Servers NAT" then this behavior is seen." It has been repaired and I am waiting on new firmware from them.
"If the public server wizard is used for to create the "Public Servers NAT" then this behavior is seen." It has been repaired and I am waiting on new firmware from them.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
is that what's happening?