Did you power-cycle the modem? db
On 4/17/10, Jeppe Øland <[email protected]> wrote: > Hi there, > > Hopefully somebody can help me with how to diagnose this problem. > > I recently switched to Comcast, and I have been running great with > them for a few weeks. > They supplied me with a Ubee cablemodem, and last week I bought a > Motorola SB6120 to replace it. Shouldn't have done that! > > The modem itself seems to work fine ... if I plug my Windows PC > straight into it, it gets an address via DHCP and everything is fine. > If I plug pfSense into it however, it never gets an address (it tries > the cached one which is no good with Comcast), and the interface goes > up and down every so often ... presumably because of the pinger > script. > > Comcast, unsurprisingly, are not helpful :-( > > The hardware I'm running pfSense on is one of the new SuperMicro X7SPA-H > boards. > It worked great with the Ubee modem. > The pfSense I am currently running on it is: pfSense-2.0-BETA1-20100407-1435 > > In the system log I see this: > Apr 17 14:19:14 firewall kernel: em1: link state changed to UP > Apr 17 14:19:15 firewall dhclient: netstat > Apr 17 14:19:15 firewall dhclient: PREINIT > Apr 17 14:19:15 firewall dhclient[25679]: DHCPREQUEST on em1 to > 255.255.255.255 port 67 > Apr 17 14:19:16 firewall dhclient[25679]: DHCPREQUEST on em1 to > 255.255.255.255 port 67 > Apr 17 14:19:18 firewall dhclient[25679]: DHCPREQUEST on em1 to > 255.255.255.255 port 67 > Apr 17 14:19:22 firewall dhclient[25679]: DHCPDISCOVER on em1 to > 255.255.255.255 port 67 interval 1 > Apr 17 14:19:22 firewall check_reload_status: rc.linkup starting > Apr 17 14:19:26 firewall last message repeated 4 times > Apr 17 14:19:27 firewall dhclient[25679]: DHCPDISCOVER on em1 to > 255.255.255.255 port 67 interval 2 > Apr 17 14:19:35 firewall last message repeated 4 times > Apr 17 14:19:37 firewall dhclient[25679]: DHCPDISCOVER on em1 to > 255.255.255.255 port 67 interval 5 > Apr 17 14:19:42 firewall sshd[50919]: Accepted > keyboard-interactive/pam for root from 10.10.10.10 port 52603 ssh2 > Apr 17 14:19:42 firewall dhclient[25679]: DHCPDISCOVER on em1 to > 255.255.255.255 port 67 interval 9 > Apr 17 14:19:51 firewall dhclient[25679]: DHCPDISCOVER on em1 to > 255.255.255.255 port 67 interval 14 > Apr 17 14:20:05 firewall dhclient[25679]: DHCPDISCOVER on em1 to > 255.255.255.255 port 67 interval 8 > Apr 17 14:20:13 firewall dhclient[25679]: DHCPDISCOVER on em1 to > 255.255.255.255 port 67 interval 8 > Apr 17 14:20:21 firewall dhclient[25679]: DHCPDISCOVER on em1 to > 255.255.255.255 port 67 interval 2 > Apr 17 14:20:23 firewall dhclient[25679]: No DHCPOFFERS received. > Apr 17 14:20:24 firewall dhclient[25679]: Trying recorded lease 24.5.66.120 > Apr 17 14:20:24 firewall dhclient: netstat > Apr 17 14:20:24 firewall dhclient: TIMEOUT > Apr 17 14:20:24 firewall dhclient: Starting add_new_address() > Apr 17 14:20:24 firewall dhclient: ifconfig em1 inet 24.5.66.120 > netmask 255.255.248.0 broadcast 255.255.255.255 > Apr 17 14:20:24 firewall dhclient: New IP Address (em1): 24.5.66.120 > Apr 17 14:20:24 firewall dhclient: New Subnet Mask (em1): 255.255.248.0 > Apr 17 14:20:24 firewall dhclient: New Broadcast Address (em1): > 255.255.255.255 > Apr 17 14:20:24 firewall dhclient: New Routers (em1): 24.5.64.1 > Apr 17 14:20:26 firewall dhclient: New Routers (em1): 24.5.64.1 > Apr 17 14:20:26 firewall dhclient: Deleting old routes > Apr 17 14:20:26 firewall dhclient[25679]: bound: renewal in 107084 seconds. > Apr 17 14:20:27 firewall check_reload_status: rc.newwanip starting > Apr 17 14:20:28 firewall php: : rc.newwanip: Informational is starting . > Apr 17 14:20:28 firewall php: : rc.newwanip: on (IP address: ) > (interface: wan) (real interface: em1). > Apr 17 14:20:28 firewall php: /interfaces.php: DynDns: Running updatedns() > Apr 17 14:20:28 firewall php: /interfaces.php: DynDns: updatedns() starting > Apr 17 14:20:28 firewall php: /interfaces.php: There was an error > trying to determine the IP for interface - wan(em1). > Apr 17 14:20:28 firewall php: /interfaces.php: DynDns: _detectChange() > starting. > Apr 17 14:20:28 firewall php: /interfaces.php: DynDns: _checkIP() starting. > Apr 17 14:20:28 firewall php: /interfaces.php: DynDns debug > information: extracted from local system. > Apr 17 14:20:28 firewall php: /interfaces.php: DynDns: Current WAN IP: > Apr 17 14:20:28 firewall php: /interfaces.php: DynDns: Cached IP: > 24.5.66.120 > Apr 17 14:20:28 firewall php: /interfaces.php: DynDns debug > information: DynDns: cacheIP != wan_ip. Updating. Cached IP: > 24.5.66.120 WAN IP: > Apr 17 14:20:28 firewall php: /interfaces.php: DynDns: DynDns > _update() starting. > Apr 17 14:20:28 firewall php: /interfaces.php: DynDns: DynDns > _update() starting. Dynamic > Apr 17 14:20:28 firewall php: /interfaces.php: Curl error occurred: > Couldn't resolve host 'members.dyndns.org' > Apr 17 14:20:28 firewall php: /interfaces.php: DynDns: DynDns > _checkStatus() starting. > Apr 17 14:20:28 firewall php: /interfaces.php: DynDns: Current Service: > dyndns > Apr 17 14:20:28 firewall php: /interfaces.php: phpDynDNS: PAYLOAD: > Apr 17 14:20:28 firewall php: /interfaces.php: phpDynDNS: (Unknown Response) > Apr 17 14:20:29 firewall dnsmasq[4417]: exiting on receipt of SIGTERM > Apr 17 14:20:30 firewall dnsmasq[22204]: started, version 2.51 cachesize > 10000 > Apr 17 14:20:30 firewall dnsmasq[22204]: compile time options: no-IPv6 > GNU-getopt no-DBus I18N DHCP TFTP > Apr 17 14:20:30 firewall dnsmasq[22204]: no servers found in > /etc/resolv.conf, will retry > Apr 17 14:20:30 firewall dnsmasq[22204]: no servers found in > /etc/resolv.conf, will retry > Apr 17 14:20:30 firewall dnsmasq[22204]: read /etc/hosts - 7 addresses > Apr 17 14:20:34 firewall dhcpd: Internet Systems Consortium DHCP Server > V3.0.7 > Apr 17 14:20:34 firewall dhcpd: Copyright 2004-2008 Internet Systems > Consortium. > Apr 17 14:20:34 firewall dhcpd: All rights reserved. > Apr 17 14:20:34 firewall dhcpd: For info, please visit > http://www.isc.org/sw/dhcp/ > Apr 17 14:20:34 firewall php: /interfaces.php: Creating rrd update script > Apr 17 14:20:34 firewall apinger: Starting Alarm Pinger, apinger(28732) > Apr 17 14:20:35 firewall check_reload_status: reloading filter > Apr 17 14:20:36 firewall check_reload_status: updating dyndns > Apr 17 14:20:38 firewall php: : DynDns: Running updatedns() > Apr 17 14:20:38 firewall php: : DynDns: updatedns() starting > Apr 17 14:20:38 firewall php: : There was an error trying to determine > the IP for interface - wan(em1). > Apr 17 14:20:38 firewall php: : DynDns: _detectChange() starting. > Apr 17 14:20:38 firewall php: : DynDns: _checkIP() starting. > Apr 17 14:20:38 firewall php: : DynDns debug information: extracted > from local system. > Apr 17 14:20:38 firewall php: : DynDns: Current WAN IP: > Apr 17 14:20:38 firewall php: : DynDns: Cached IP: 24.5.66.120 > Apr 17 14:20:38 firewall php: : DynDns debug information: DynDns: > cacheIP != wan_ip. Updating. Cached IP: 24.5.66.120 WAN IP: > Apr 17 14:20:38 firewall php: : DynDns: DynDns _update() starting. > Apr 17 14:20:38 firewall php: : DynDns: DynDns _update() starting. Dynamic > Apr 17 14:20:38 firewall php: : Curl error occurred: Couldn't resolve > host 'members.dyndns.org' > Apr 17 14:20:38 firewall php: : DynDns: DynDns _checkStatus() starting. > Apr 17 14:20:38 firewall php: : DynDns: Current Service: dyndns > Apr 17 14:20:38 firewall php: : phpDynDNS: PAYLOAD: > Apr 17 14:20:38 firewall php: : phpDynDNS: (Unknown Response) > Apr 17 14:20:44 firewall apinger: ALARM: wan(24.5.64.1) *** down *** > Apr 17 14:20:59 firewall check_reload_status: reloading filter > > Anybody have an idea what could be going on, and how I can diagnose it? > I guess one thing I should try is to install on some other HW to see > if it's a Comcast/FreeBSD issue, or maybe the 1.2.3 release and see if > the problem happens there too. > > Regards, > -Jeppe > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > Commercial support available - https://portal.pfsense.org > > -- Sent from my mobile device --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Commercial support available - https://portal.pfsense.org
