![]() ![]() I used the "dhcping" tool and none of the wireless routers (which are set to AP mode) responded. I've attached the dhcpd.log file and also a screenshot of my DHCP config. The issue is quite frustrating though since my TV and Android devices have no way to manually renew the DHCP lease so sometimes, I'll need to constantly disconnect and connect until they get a 10.8.8.x IP. I'm really not sure what might be causing this and I don't even know if pfsense is at fault. I looked at the dhcpd.log file and I see a lot of lines like this: Jan 2 02:36:50 pfsense dhcpd: DHCPREQUEST for 192.168.1.8 from f4:09:d8:ed:44:3a via dc0: wrong network. Got answer from: ~ » sudo dhcping -s 10.8.8.2 I've double-checked to make sure the wireless routers are set to AP mode and do not have a DHCP server running on them: ~ » sudo dhcping -s 10.8.8.1 My pfsense box is running 2.2.6 and the DHCP server configuration is just the default, except for the range being set to 10.8.8.100-10.8.8.254. ![]() I've had the exact same setup for a year now and nothing has changed in the network besides having a few new devices (tablets/phones). This is happening on just about every device (randomly), no matter if it's the smart TV, an Android device, or a Linux/Windows computer. ![]() Any ideas?Ģnd thing, All the D-link adapters appear as repeaters rather than clients.ģrd thing, Can the Router pass through DHCP requests and if it doesnt get a response, act as a DHCP server to the box?įinally, Boxes are using D-LINK USB Wireless adapters (which I'm not too happy with at the moment as it appears that the d-link provided drivers have some conflict with via chipsets and freeze systems).I've been having an issue recently where devices on the network are randomly getting 192.168.1.x when the DHCP server is configured for the 10.8.8.100 to 10.8.8.254 range. The router will displays this in the association window, but will not allow the router to ping that ip address. It authenticates fine, then after XP times out trying to get an ip it gives it a windows default. This morning one of our boxes just up and stopped dhcping, no change to the box, just wont pull an IP address through anymore. ![]() This is a testbed wireless network we have up and running before we start rolling it out on a wider scale, so trying to iron out all the little problems. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |