Dhclient question
-
Unfortunately, still no dice… I ran through the wizard and saved, rebooted but still no change. Not sure what else to try.
-
Im on 32bit version, don't see a need for pfsense to be 64bit? Seems to have less issues as well ;)
But don't they have a newer snap - I show one dated
New version: Sat Oct 20 19:31:24 EDT 2012Is that the one your running? Im on
Built On: Fri Oct 19 15:19:38 EDT 2012I would either move forward or drop back on the snap.
-
I think you're right about the 64bit. Thanks for the assistance though. I guess I'll have to wait it out and see what happens.
-
I think you're right about the 64bit. Thanks for the assistance though. I guess I'll have to wait it out and see what happens.
Personally I'd delete the default WAN and re-create it, just for the sake of completeness.
Reason why I say this is because once I changed the default WAN to PPPoE and rebooted those entries were no longer appearing in the box, and after setting up the 2nd WAN (which is also DHCP and requires dhclient) they didn't reappear.
Something odd in the dhclient.cof on the first setup? just an educated guess…
-
Just to not leave anyone hanging, I deleted the WAN interface, rebooted but still every 2 minutes I'm getting those messages. I'm going to disable logging for a bit until I can figure it out.
-
I'm also seing this on a freshly built Intel D2500CCE (HDD install), em1 is my WAN interface which is configured for DHCP:
Oct 27 13:14:16 dhclient: XMT: Solicit on em1, interval 108120ms.
Oct 27 13:16:05 dhclient: XMT: Solicit on em1, interval 111070ms.
Oct 27 13:17:29 check_reload_status: Syncing firewall
Oct 27 13:17:56 dhclient: XMT: Solicit on em1, interval 110970ms.
Oct 27 13:17:57 check_reload_status: Syncing firewall
Oct 27 13:18:43 check_reload_status: Syncing firewall
Oct 27 13:19:04 check_reload_status: Syncing firewall
Oct 27 13:19:24 check_reload_status: Syncing firewall
Oct 27 13:19:24 check_reload_status: Reloading filter
Oct 27 13:19:48 dhclient: XMT: Solicit on em1, interval 125310ms.My build is:
2.1-BETA0 (amd64)
built on Thu Oct 25 18:52:59 EDT 2012
FreeBSD 8.3-RELEASE-p4 -
Those seeing this, you have DHCP6 set on WAN by chance? Guessing this is related to no DHCPv6 being available and recent changes with the DHCPv6 client.
-
@cmb:
Those seeing this, you have DHCP6 set on WAN by chance? Guessing this is related to no DHCPv6 being available and recent changes with the DHCPv6 client.
I already disabled IPv6 DHCP on the WAN interface some time ago, but I am still seeing these messages in the system log.
-
I had DHCPv6 on (default setting) on WAN. There is no IPv6 service on my WAN, so I turned it off today, but the messages keep coming.
-
I rebooted and the messages are gone. So I guess the DHCPv6 Client running on WAN does not get stopped when DHCPv6 is turned off in the GUI. But at boot time the scripts know not to bother starting it.
-
Under WAN interfaces, turning IPv6 Configuration Type to none and rebooting solved it for me. I don't see those messages any longer. Thanks!
-
I can also confirm that the reboot (After disabling DHCP for IPv6) has stopped these log entries from appearing.
