@stephenw10 said in Connectivity lost after clearing ARP table:
Hmm, interesting. So you actually see that address shown as current in the dhcp leases after reconnecting? But it's not in the arp table?
If you try to ping out from pfSense to 10.1.1.100 does that re-create the arp table entry?
ping -c5 10.1.1.100 before clearing arp table is successful as you can see below:
[2.8.0-BETA][admin@pfSense.home.arpa]/: ping -c5 10.1.1.100
PING 10.1.1.100 (10.1.1.100): 56 data bytes
64 bytes from 10.1.1.100: icmp_seq=0 ttl=64 time=3.432 ms
64 bytes from 10.1.1.100: icmp_seq=1 ttl=64 time=1.838 ms
64 bytes from 10.1.1.100: icmp_seq=2 ttl=64 time=1.840 ms
64 bytes from 10.1.1.100: icmp_seq=3 ttl=64 time=1.898 ms
64 bytes from 10.1.1.100: icmp_seq=4 ttl=64 time=79.029 ms
--- 10.1.1.100 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.838/17.607/79.029/30.717 ms
[2.8.0-BETA][admin@pfSense.home.arpa]/:
Executing ping -c5 10.1.1.100 after cleanup does not recreate arp entry and there is no response.
[2.8.0-BETA][admin@pfSense.home.arpa]/: ping -c5 10.1.1.100
PING 10.1.1.100 (10.1.1.100): 56 data bytes
ping: sendto: Invalid argument
ping: sendto: Invalid argument
ping: sendto: Invalid argument
ping: sendto: Invalid argument
ping: sendto: Invalid argument
--- 10.1.1.100 ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss
[2.8.0-BETA][admin@pfSense.home.arpa]/:
And again, restarting dhcp server brings everything back to life.
The dhcp lease is odd because that implies pfSense has sent some traffic to the client and must have known the MAC to do so. 🤔
Ok. Im currently connected to vlan 55 network and everything is working fine.
I executed arp -a |grep 10.1.1.100 and my pc address is clearly showing up in arp table as you can see below:
[2.8.0-BETA][admin@pfSense.home.arpa]/: arp -a |grep 10.1.1.100
? (10.1.1.100) at mac_address on igb5.55 permanent [vlan]
[2.8.0-BETA][admin@pfSense.home.arpa]/:
Then i log into pfsense web gui and perform arp clean and i immediately lose all connectivity. I then go to my switch, pull out the network cable and plug it into a port that has vlan 75 (management vlan) assigned to it, and now im able to access web gui and connect via ssh.
Once logged into a console, i executed arp -a |grep 10.1.1.100 and i got no search results for my ip as you can see below:
[2.8.0-BETA][admin@pfSense.home.arpa]/: arp -a |grep 10.1.1.100
[2.8.0-BETA][admin@pfSense.home.arpa]/:
Just to make sure that im receiving ip address from pfsense dhcp, i plug my cable back into a vlan 55 tagged port without resetting any services, and i receive ip address, but there is no connectivity at all. Then i execute arp -a 10.1.1.100 just to make sure that ip address is not there, and sure enough, its missing as you can see below:
[2.8.0-BETA][admin@pfSense.home.arpa]/: arp -a | grep 10.1.1.100
[2.8.0-BETA][admin@pfSense.home.arpa]/:
Now i go back to my switch again, i disconnect the cable from vlan 55 network, and plug it back into my vlan 75 management network. Then i connect to pfsense via web gui and restart dhcp service. I reconnect my cable back to my vlan 55 network and all connectivity is restored. Of course, executing arp -a |grep 10.1.1.100 produces this output again.
[2.8.0-BETA][admin@pfSense.home.arpa]/: arp -a |grep 10.1.1.100
? (10.1.1.100) at mac_address on igb5.55 permanent [vlan]
[2.8.0-BETA][admin@pfSense.home.arpa]/:
Is there any reason you are using static ARP entries?
For security reasons.
However, connection still hangs with or without static arp entires. It makes no difference at all.
