Mar 9 Update DNS-trouble and struggled boot
-
The snap from Mar 9 08:46:18 doesn't settle any DNS-servers provided by ISP. I have to set one manually via "General Setup", if not, no traffic on wan-if possible.
Til this update manually pressing "save" in "General Setup" settled the DNS-servers provided by ISP, but not any more. :-(When rebooting pfSense the Dyndns-Update-script is called before calling mpd. This is not really right…
here the logs in reverse order:
Mar 9 22:04:25 mpd: Multi-link PPP daemon for FreeBSD Mar 9 22:04:25 mpd: process 7632 terminated Mar 9 22:04:23 mpd: caught fatal signal term Mar 9 22:03:13 check_reload_status: syncing firewall Mar 9 22:03:13 check_reload_status: check_reload_status is starting Mar 9 22:03:12 php: : Resyncing configuration for all packages. Mar 9 22:03:11 dhcpd: For info, please visit http://www.isc.org/sw/dhcp/ Mar 9 22:03:11 dhcpd: All rights reserved. Mar 9 22:03:11 dhcpd: Copyright 2004-2008 Internet Systems Consortium. Mar 9 22:03:11 dhcpd: Internet Systems Consortium DHCP Server V3.0.7 Mar 9 22:03:10 php: : Creating rrd update script Mar 9 22:03:07 php: : The command '/sbin/ipfw table 2 flush' returned exit code '71', the output was 'ipfw: Warn: Failed to get the max tables number via sysctl. Using the compiled in defaults. The reason was: No such file or directory ipfw: setsockopt(IP_FW_TABLE_FLUSH): Protocol not available' Mar 9 22:03:07 php: : The command '/sbin/ipfw table 1 flush' returned exit code '71', the output was 'ipfw: Warn: Failed to get the max tables number via sysctl. Using the compiled in defaults. The reason was: No such file or directory ipfw: setsockopt(IP_FW_TABLE_FLUSH): Protocol not available' Mar 9 22:03:07 php: : The command '/sbin/ipfw /tmp/ipfw.cp.rules' returned exit code '69', the output was 'Line 1: getsockopt(IP_FW_ADD): Protocol not available' Mar 9 22:03:07 php: : The command '/sbin/ipfw -f delete set 1' returned exit code '69', the output was 'ipfw: rule 16777217: setsockopt(IP_FW_DEL): Protocol not available' Mar 9 22:03:06 php: : The command '/sbin/ipfw table all flush' returned exit code '71', the output was 'ipfw: Warn: Failed to get the max tables number via sysctl. Using the compiled in defaults. The reason was: No such file or directory ipfw: setsockopt(IP_FW_TABLE_FLUSH): Protocol not available' Mar 9 22:03:06 php: : The command 'sysctl net.inet.ip.fw.dyn_max=10000' returned exit code '1', the output was 'sysctl: unknown oid 'net.inet.ip.fw.dyn_max'' Mar 9 22:03:06 kernel: KLD ipfw.ko: depends on kernel - not available or version mismatch Mar 9 22:03:06 php: : The command '/sbin/kldload ipfw' returned exit code '1', the output was 'kldload: can't load ipfw: No such file or directory' Mar 9 22:03:06 dnsmasq[38817]: read /etc/hosts - 7 addresses Mar 9 22:03:06 dnsmasq[38817]: no servers found in /etc/resolv.conf, will retry Mar 9 22:03:06 dnsmasq[38817]: no servers found in /etc/resolv.conf, will retry Mar 9 22:03:06 dnsmasq[38817]: compile time options: no-IPv6 GNU-getopt no-DBus I18N DHCP TFTP Mar 9 22:03:06 dnsmasq[38817]: started, version 2.51 cachesize 10000 Mar 9 22:03:05 php: : phpDynDNS: (Unknown Response) Mar 9 22:03:05 php: : phpDynDNS: PAYLOAD: Mar 9 22:03:05 php: : DynDns: Current Service: dyndns Mar 9 22:03:05 php: : DynDns: DynDns _checkStatus() starting. Mar 9 22:03:05 php: : Curl error occurred: Couldn't resolve host 'members.dyndns.org' Mar 9 22:02:13 apinger: ALARM: wan(127.0.0.2) *** down *** Mar 9 22:02:07 sshlockout[35931]: sshlockout starting up Mar 9 22:02:07 sshlockout[35931]: sshlockout starting up Mar 9 22:02:07 sshd[35651]: Server listening on 0.0.0.0 port 22. Mar 9 22:02:07 sshd[35651]: Server listening on :: port 22. Mar 9 22:02:05 php: : DynDns: DynDns _update() starting. Dynamic Mar 9 22:02:05 php: : DynDns: DynDns _update() starting. Mar 9 22:02:05 php: : DynDns debug information: DynDns: cacheIP != wan_ip. Updating. Cached IP: 78.34.x.x WAN IP: Mar 9 22:02:05 php: : DynDns: Cached IP: 78.34.x.x Mar 9 22:02:05 php: : DynDns: Current WAN IP: Mar 9 22:02:05 php: : DynDns debug information: extracted from local system. Mar 9 22:02:05 php: : DynDns: _checkIP() starting. Mar 9 22:02:05 php: : DynDns: _detectChange() starting. Mar 9 22:02:05 php: : DynDns: updatedns() starting Mar 9 22:02:05 php: : DynDns: Running updatedns() Mar 9 22:02:03 kernel: bge1: link state changed to UP -
Now with the update from Mar 11, still no DNS passed from ISP:
Mar 11 20:10:06 dnsmasq[8893]: read /etc/hosts - 7 addresses Mar 11 20:10:06 dnsmasq[8893]: using nameserver 4.2.2.1#53 Mar 11 20:10:06 dnsmasq[8893]: reading /etc/resolv.conf Mar 11 20:10:06 dnsmasq[8893]: compile time options: no-IPv6 GNU-getopt no-DBus I18N DHCP TFTP Mar 11 20:10:06 dnsmasq[8893]: started, version 2.51 cachesize 10000 Mar 11 20:10:05 dnsmasq[34786]: exiting on receipt of SIGTERM Mar 11 20:10:05 dnsmasq[34786]: using nameserver 4.2.2.1#53 Mar 11 20:10:05 dnsmasq[34786]: reading /etc/resolv.conf Mar 11 20:10:05 dhcpd: For info, please visit http://www.isc.org/sw/dhcp/ Mar 11 20:10:05 dhcpd: All rights reserved. Mar 11 20:10:05 dhcpd: Copyright 2004-2008 Internet Systems Consortium. Mar 11 20:10:05 dhcpd: Internet Systems Consortium DHCP Server V3.0.7 Mar 11 20:09:42 check_reload_status: syncing firewall Mar 11 20:09:42 check_reload_status: reloading filter Mar 11 20:09:41 check_reload_status: rc.newwanip starting Mar 11 20:09:40 mpd: [wan] IFACE: Up event Mar 11 20:09:40 mpd: [wan] 87.79.194.109 -> 195.14.226.7 Mar 11 20:09:40 mpd: [wan] IPCP: LayerUp Mar 11 20:09:40 mpd: [wan] IPCP: state change Ack-Rcvd --> Opened Mar 11 20:09:40 mpd: [wan] IPADDR 195.14.226.7 Mar 11 20:09:40 mpd: [wan] IPCP: SendConfigAck #201 Mar 11 20:09:40 mpd: [wan] 195.14.226.7 is OK Mar 11 20:09:40 mpd: [wan] IPADDR 195.14.226.7 Mar 11 20:09:40 mpd: [wan] IPCP: rec'd Configure Request #201 (Ack-Rcvd) Mar 11 20:09:39 mpd: [wan] IPCP: state change Req-Sent --> Ack-Rcvd Mar 11 20:09:39 mpd: [wan] SECDNS 81.173.194.69 Mar 11 20:09:39 mpd: [wan] PRIDNS 81.173.194.76 Mar 11 20:09:39 mpd: [wan] IPADDR 87.79.194.109 Mar 11 20:09:39 mpd: [wan] IPCP: rec'd Configure Ack #3 (Req-Sent) Mar 11 20:09:39 mpd: [wan] SECDNS 81.173.194.69The "Allow DNS server list to be overridden by DHCP/PPP on WAN " is set. But no effect.
No one else having this?
-
I have installed 2010.03.08 01:34 in two different partitions on the same box.
In one partition I installed the uniprocessor kernel, in the other the embedded kernel.When using pfSense with the uniprocessor kernel, I get the same problem:
The WAN DNS is not picked up from DHCP.But with the embedded kernel, there is no such problem!
(I believe I have set the two systems up identically, but of course the culprit could be something else than the kernel)
-
Snap from today 13 has still the DNS-problem!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register LoginPrivacy Policy · Cookie Policy