Android and DHCP
-
Well, then you have a phone problem, not pfSense one.
-
Only Android phones…
-
Yes. And?
-
I would agree if the issue is with only one device. But when you try with 2-3 devices and the result is the same I guess some digging would help…
Other devices work as expected. I don't think PFSense is the problem, I just want to get some suggestions, maybe something I have overlooked. -
The phone sends DHCPREQUEST, gets DHCPOFFER, then it refuses that… Dig into your phone/Android.
-
"dhcpd: DHCPREQUEST for <android_generic_ip>(<android_generic_ip_broadcast>) from <android_mac>via em1: wrong network."
So its doing a request for wrong network?? Its so much easier to just see the sniff vs log, that your obfuscating mac addresses??
What IP is it asking for, did a ping go out and it comes back with an answer from your gateway??
"unexpected ICMP Echo Reply from <wan gateway="">"</wan></android_mac></android_generic_ip_broadcast></android_generic_ip> -
What IP is it asking for, did a ping go out and it comes back with an answer from your gateway??
"unexpected ICMP Echo Reply from <wan gateway="">"</wan>That part's just a quirk of dhcpd's listening, it sees gateway monitoring ping replies. Doesn't hurt anything as it just ignores it and log spams.
-
So much better to just sniff and see exactly what is going on, what gets requested, what gets offered, etc. etc..
-
Guys, thank you all for your ideas.
I solved the issue and I am happy to say that both Android and PFSense have no issues (it was kind of clear from the beginning).
The problem here was VMWare Workstation, let me explain: I use my desktop as a home lab and have a some network interfaces that I bridge in order to get all the networks I need. I did the whole config on Win 8.1 but when I migrated to 10, for some reason, it did not migrate the networks correctly and I had to redo them. It seems that even after this was done, there was one more issue. Workstation started the DHCP and NAT services in Windows, services that I had stopped and selected to start only manually.
For some reason DHCP was started and using VMNet1 as a custom network with IP 192.168.209.x/24 and some wireless devices went to this DHCP server for leases. It's interesting because VMNet1 is bridged with my LAN 10.10.0.X/24. The only way I can see the weird interface was if I used Virtual Network Editor without admin right (start Workstation not as an admin but as a normal user, screenshots attached). Screenshot 1 is taken without admin rights and screenshot 2 with admin rights and as you see they both have VMNet1. Windows does not report that virtual interface but for some reason it was there giving out IP leases. After I stopped Workstation DHCP service, everything is running smoothly.
Sorry for the long post and thanks for all your help.
Best regards,
Andrei
-
The problem here was VMWare Workstation
In future, you might want to mention this little nugget a little sooner. Virtualized installs add a whole other level of details & troubleshooting.
-
The network was hidden even with ipconfig /all so I didn't really know, only after some troubleshooting.
