Weird Issue Getting IP from Cable Company
-
If you already did I missed it but can you try swapping interfaces wan for lan??
You might try a different modem if you can get your hands on one without expense just for giggles… May be a bad interaction going on...
With modems- the dumber the better IMO...
I'll try the swap on the cards in a couple…
I have to hard reset the modem to get online so it loses bridge mode.. So I'll get it back in bridge mode and then post back.
-
Switching NIC's didn't work…
I lost my IP like 10 minutes ago...
To get it back up what I had to do was unplug pfsense from the modem. Restart the modem. Wait for the modem to get all the way backup. Once up I reconnected the ethernet cord and walla it got an ip and no issues..
[edit]
Also changing modem isn't an option as it's docsis 3.0 and they seem to be overly restrictive on what we are allowed to do. -
Also changing modem isn't an option as it's docsis 3.0 and they seem to be overly restrictive on what we are allowed to do
Perhaps they have another model that they could swap out with you…
Is your account commercial or residential? Reason I ask is that commercial customers seem to have more leeway... (insert evil grin here.)
You might quiz them on whether they have done any recent firmware upgrades on that modem.
Ill go look later but does that modem have a gigabit port? If so- You might try swapping to a gigabit port on your router box if you don't already... Something could have changed firmware wise...
I recall having a bad line between my kids computer and the switch causing it dhcp issues... It would still browse and had good pings when I set it up static. Also would not connect at 1000mbps. Patch cord?
Keep in mind that the power outage could just be a coincidence.. and that something was ready to break.
-
Just a thought… But I have Time Warner RR service in NC and I just saw something recently that said they are doing some sort of massive upgrade on the East Coast. Might have something to do with your issue?
Also, which actual SuperMicro board are you using? Because if you are using one with IPMI, and you have it enabled, then em0 will be looking for 2 IP's. One for the IPMI as soon as the board gets power or the network is plugged in, and then one when PfSense boots up. And, I am pretty sure that your RR service will only dole out one IP address. I found it better to use em1 for the WAN.
PB...
-
Just a thought… But I have Time Warner RR service in NC and I just saw something recently that said they are doing some sort of massive upgrade on the East Coast. Might have something to do with your issue?
Also, which actual SuperMicro board are you using? Because if you are using one with IPMI, and you have it enabled, then em0 will be looking for 2 IP's. One for the IPMI as soon as the board gets power or the network is plugged in, and then one when PfSense boots up. And, I am pretty sure that your RR service will only dole out one IP address. I found it better to use em1 for the WAN.
PB...
Using the atom board..
http://www.newegg.com/Product/Product.aspx?Item=N82E16813182243
I believe I have impi off but I believe that point is mute as as you said em1 doesn't have impi and even when I switched to it to test if it was a nic issue it still happened..
I also have not heard anything about this RR upgrade.
-
I just checked and the notice came via email….
(Came on the 16th)
Dear Customer,
Over the next several days, Time Warner Cable will be upgrading its Digital Home Phone
and High Speed Internet delivery systems. We're excited to say that this upgrade will enable
us to offer even faster Internet speeds and improved reliability in the future. Look for more
information on new speed offerings soon. All necessary work will be performed at night
between midnight and 6 am in order to minimize the potential for service interruptions.
During this time you may experience a brief loss of Road Runner High Speed Online
and/or Digital Home Phone service. Once the upgrade is complete, your service
should be operating normally..............................................(There was more, but it's not relevant.)
I have the X7SPA-HF, which is a similar board, but not having any problems as long as I keep the LAN on em0, and the WAN on em1 as I stated above. Good luck.
-
I just checked and the notice came via email….
(Came on the 16th)
Dear Customer,
Over the next several days, Time Warner Cable will be upgrading its Digital Home Phone
and High Speed Internet delivery systems. We're excited to say that this upgrade will enable
us to offer even faster Internet speeds and improved reliability in the future. Look for more
information on new speed offerings soon. All necessary work will be performed at night
between midnight and 6 am in order to minimize the potential for service interruptions.
During this time you may experience a brief loss of Road Runner High Speed Online
and/or Digital Home Phone service. Once the upgrade is complete, your service
should be operating normally..............................................(There was more, but it's not relevant.)
I have the X7SPA-HF, which is a similar board, but not having any problems as long as I keep the LAN on em0, and the WAN on em1 as I stated above. Good luck.
Yeah thats the DOCSIS 3.0 for your area..
We already have done that and I am running DOSIS 3.
-
You know, I just had to mess with this because I am type A. Well, I wasn't spoofing a MAC, so I did and… At first it seemed to work fine, could not duplicate your problem. Then I powered down the Cable Modem and when it came back up pfSense could not get an IP address from it. Have to restart the pfsense box to get it back. Without a restart, I experience the same symptoms as your rig. I am running the AMD64 version from 13FEB. Will try an upgrade in the AM.
-
I'm running 2.0-BETA5 (i386)
built on Thu Feb 17 01:33:38 EST 2011When I first booted behind a modem it would not get an IP on the wan. Rebooting the modem gave it a 192.168 address, rebooting the pf box and a few release / renew clicks and I got a valid wan IP.
-
My cable modem does that when it doesn't have upstream connectivity.
If I can't get an IP at all? Probably need to reboot the modem, since it has an outdated/cached MAC address. If I get a local IP and not public? No upstream connection, or it's lost sync and is reconnecting. If I get a public IP - all OK.
-
I would like to bump this…
After getting some time to mess with this some more, the issue of being unable to pull/renew an IP address still exists in the latest RC, and is easily duplicated. I set up 2 networks as so to test... [cable modem-WAN] > [router-192.168.1.1] > [pfsense-192.168.2.1]. If the router loses power or the cable to pfsense is disconnected and then reconnected, pfsense will not be able to pull/renew the IP address from the router. It works the same when connected directly to the cable modem. Is this a bug or something, or a hardware issue? Attached is what I am seeing in the log. My hardware/software is:
Supermicro x7spa-hf
pfSense-2.0-RC1-i386-20110320-1800Mar 21 14:53:04 dhclient[1962]: connection closed
Mar 21 14:53:04 dhclient[1962]: connection closed
Mar 21 14:53:04 dhclient[1962]: exiting.
Mar 21 14:53:04 dhclient[1962]: exiting.
Mar 21 14:53:04 check_reload_status: reloading filter
Mar 21 14:53:04 apinger: Starting Alarm Pinger, apinger(14341)
Mar 21 14:53:04 apinger: bind socket: Can't assign requested address
Mar 21 14:53:05 kernel: arprequest: cannot find matching address
Mar 21 14:53:05 check_reload_status: Linkup starting em1
Mar 21 14:53:05 kernel: em1: link state changed to UP
Mar 21 14:53:06 kernel: arprequest: cannot find matching address
Mar 21 14:53:06 php: : DEVD Ethernet attached event for wan
Mar 21 14:53:06 php: : HOTPLUG: Configuring interface wan
Mar 21 14:53:06 dhclient[4755]: connection closed
Mar 21 14:53:06 dhclient[4755]: connection closed
Mar 21 14:53:06 dhclient[4755]: exiting.
Mar 21 14:53:06 dhclient[4755]: exiting.
Mar 21 14:53:06 dhclient: PREINIT
Mar 21 14:53:06 dhclient[12449]: DHCPREQUEST on em1 to 255.255.255.255 port 67
Mar 21 14:53:06 dhclient[12449]: DHCPACK from 192.168.1.1
Mar 21 14:53:06 dhclient: REBOOT
Mar 21 14:53:06 dhclient: Starting add_new_address()
Mar 21 14:53:06 dhclient: ifconfig em1 inet 192.168.1.206 netmask 255.255.255.0 broadcast 192.168.1.255
Mar 21 14:53:06 dhclient: New IP Address (em1): 192.168.1.206
Mar 21 14:53:06 dhclient: New Subnet Mask (em1): 255.255.255.0
Mar 21 14:53:06 dhclient: New Broadcast Address (em1): 192.168.1.255
Mar 21 14:53:06 dhclient: New Routers (em1): 192.168.1.1
Mar 21 14:53:06 dhclient: Adding new routes to interface: em1
Mar 21 14:53:06 dhclient: /sbin/route add default 192.168.1.1
Mar 21 14:53:06 dhclient: Creating resolv.conf
Mar 21 14:53:06 check_reload_status: rc.newwanip starting em1
Mar 21 14:53:06 dhclient[12449]: bound to 192.168.1.206 – renewal in 43200 seconds.
Mar 21 14:53:06 php: : rc.newwanip: Informational is starting em1.
Mar 21 14:53:06 php: : rc.newwanip: on (IP address: 192.168.1.206) (interface: wan) (real interface: em1).
Mar 21 14:53:06 php: : ROUTING: change default route to 192.168.1.1
Mar 21 14:53:07 apinger: Exiting on signal 15.
Mar 21 14:53:07 check_reload_status: Linkup starting em1
Mar 21 14:53:07 kernel: em1: link state changed to DOWN
Mar 21 14:53:07 php: : DEVD Ethernet detached event for wan
Mar 21 14:53:07 dhclient[29429]: connection closed
Mar 21 14:53:07 dhclient[29429]: connection closed
Mar 21 14:53:07 dhclient[29429]: exiting.
Mar 21 14:53:07 dhclient[29429]: exiting.
Mar 21 14:53:08 check_reload_status: reloading filter
Mar 21 14:53:08 apinger: Starting Alarm Pinger, apinger(41397)
Mar 21 14:53:08 apinger: bind socket: Can't assign requested address
Mar 21 14:53:08 kernel: arprequest: cannot find matching address
Mar 21 14:53:09 check_reload_status: Linkup starting em1
Mar 21 14:53:09 kernel: arprequest: cannot find matching address
Mar 21 14:53:09 kernel: em1: link state changed to UP -
I work for a cable company and I will say that cable modems can be a pain. If your signal levels are good, you should have no issues… But before turning your router on, you need to first turn on your cable modem. Once your cable modem locks, then turn on your pfsense box. Turning your cable modem on first will make sure your router will get either a private IP or a public IP, depending on how your modem is setup. My modem is a DOCSIS 3.0 modem/router. Since I have it in bridge modem(to get a public ip) When the modem starts to up it will give out a private IP then the public. BTW, all of TWC sites should be DOCSIS 3.0. But you only need a DOCSIS 3.0 modem if you want and pay for 50mps speeds... 20mps with speedboost is fine on a 2.0 modem.
My current setup is a multi-wan setup since i have a verizon 3g usb as a backup... I'll have to remove that and retest but I remember when i tried every outage i could think of on my X7SPA-HF, i had similar issues. I ended up using monit to ping monitor and reboot if it couldn't ping after 5 mins... Now that i'm multi-wan, i will have to change the ip it pings since the one i'm ping can be reached on TWC and Verizon.
This morning I reset my modem from work. The modem came back online, but OpenVPN, and upnp had some issues...I believe this is because the modem gave pfsense a Private IP first then after it fully finish booting, it gave the Public IP but OpenVPN and upnp didnt restart. I had to go into each of their setting tabs and click Save/Change for them to start up again. See my log below, this is right after i reset the modem.
i'm running the latest snapshot from yesterday with ipv6 code...i386
03-22-2011 10:11:01 Cron.Info pfsense /usr/sbin/cron[10149]: (root) CMD (/usr/local/pkg/vnstat2.sh) 03-22-2011 10:10:02 Cron.Info pfsense cron[41604]: (root) MAIL (mailed 1838 bytes of output but got status 0x0001 ) 03-22-2011 10:10:01 User.Notice pfsense root: Countryblock was found not running 03-22-2011 10:10:01 Cron.Info pfsense /usr/sbin/cron[41711]: (root) CMD (/usr/local/etc/rc.d/countryblock.sh) 03-22-2011 10:10:01 Cron.Info pfsense /usr/sbin/cron[41703]: (root) CMD (/usr/local/pkg/vnstat2.sh) 03-22-2011 10:09:17 Auth.Info pfsense sshd[21174]: subsystem request for sftp 03-22-2011 10:09:17 Auth.Info pfsense sshd[21174]: Accepted keyboard-interactive/pam for root from LIB-738CGH1 port 1963 ssh2 03-22-2011 10:09:01 Cron.Info pfsense cron[54812]: (root) MAIL (mailed 96 bytes of output but got status 0x0001 ) 03-22-2011 10:09:00 Cron.Info pfsense /usr/sbin/cron[54907]: (root) CMD (/usr/local/pkg/vnstat2.sh) 03-22-2011 10:08:56 Daemon.Info pfsense dnsmasq[25740]: using nameserver 2001:470:20::2#53 03-22-2011 10:08:56 Daemon.Info pfsense dnsmasq[25740]: using nameserver google-public-dns-a.google.com#53 03-22-2011 10:08:56 Daemon.Info pfsense dnsmasq[25740]: using nameserver dns-xxx.xxx.xxx.rr.com#53 03-22-2011 10:08:56 Daemon.Info pfsense dnsmasq[25740]: using nameserver xxx.sub-xxx-xxx-xxx.myvzw.com#53 03-22-2011 10:08:56 Daemon.Info pfsense dnsmasq[25740]: reading /etc/resolv.conf 03-22-2011 10:08:30 User.Notice pfsense check_reload_status: syncing firewall 03-22-2011 10:08:28 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 10:08:26 User.Warning pfsense php: : Gateways status could not be determined, considering all as up/active. 03-22-2011 10:08:26 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 10:08:25 User.Error pfsense apinger: Starting Alarm Pinger, apinger(25351) 03-22-2011 10:08:25 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 10:08:24 User.Error pfsense apinger: Exiting on signal 15. 03-22-2011 10:08:24 User.Warning pfsense php: : Removing static route for monitor xxx.sub-xxx-xxx-xxx.myvzw.com and adding a new route through xxx.xxx.xxx.xxx 03-22-2011 10:08:23 User.Warning pfsense php: : rc.newwanip: on (IP address: 192.168.201.1) (interface: opt2) (real interface: ovpns2). 03-22-2011 10:08:23 User.Warning pfsense php: : rc.newwanip: Informational is starting ovpns2. 03-22-2011 10:08:23 User.Notice pfsense check_reload_status: syncing firewall 03-22-2011 10:08:22 User.Notice pfsense check_reload_status: rc.newwanip starting ovpns2 03-22-2011 10:08:22 Kernel.Notice pfsense kernel: ovpns2: link state changed to UP 03-22-2011 10:08:22 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 10:08:20 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 10:08:19 User.Warning pfsense php: : Gateways status could not be determined, considering all as up/active. 03-22-2011 10:08:18 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 10:08:18 User.Error pfsense apinger: Starting Alarm Pinger, apinger(57467) 03-22-2011 10:08:18 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 10:08:17 User.Warning pfsense php: : Gateways status could not be determined, considering all as up/active. 03-22-2011 10:08:17 User.Error pfsense apinger: Exiting on signal 15. 03-22-2011 10:08:17 User.Warning pfsense php: : Removing static route for monitor xxx.sub-xxx-xxx-xxx.myvzw.com and adding a new route through xxx.xxx.xxx.xxx 03-22-2011 10:08:17 Daemon.Info pfsense dnsmasq[25740]: using nameserver 2001:470:20::2#53 03-22-2011 10:08:17 Daemon.Info pfsense dnsmasq[25740]: using nameserver google-public-dns-a.google.com#53 03-22-2011 10:08:17 Daemon.Info pfsense dnsmasq[25740]: using nameserver dns-xxx.xxx.xxx.rr.com#53 03-22-2011 10:08:17 Daemon.Info pfsense dnsmasq[25740]: using nameserver xxx.sub-xxx-xxx-xxx.myvzw.com#53 03-22-2011 10:08:17 Daemon.Info pfsense dnsmasq[25740]: reading /etc/resolv.conf 03-22-2011 10:08:16 User.Warning pfsense php: : rc.newwanip: on (IP address: 192.168.200.1) (interface: opt1) (real interface: ovpns1). 03-22-2011 10:08:16 User.Warning pfsense php: : rc.newwanip: Informational is starting ovpns1. 03-22-2011 10:08:16 User.Notice pfsense check_reload_status: syncing firewall 03-22-2011 10:08:14 User.Notice pfsense check_reload_status: rc.newwanip starting ovpns1 03-22-2011 10:08:14 Kernel.Notice pfsense kernel: ovpns1: link state changed to UP 03-22-2011 10:08:14 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 10:08:01 Cron.Info pfsense /usr/sbin/cron[48705]: (root) CMD (/usr/local/pkg/vnstat2.sh) 03-22-2011 10:07:44 Daemon.Notice pfsense miniupnpd[37349]: Listening for NAT-PMP traffic on port 5351 03-22-2011 10:07:44 Daemon.Notice pfsense miniupnpd[37349]: HTTP listening on port 2189 03-22-2011 10:07:44 Daemon.Error pfsense miniupnpd[37349]: Unable to open pidfile for writing /var/run/miniupnpd.pid: File exists 03-22-2011 10:07:44 User.Info pfsense miniupnpd: SNet version started 03-22-2011 10:07:44 User.Warning pfsense php: /pkg_edit.php: miniupnpd: Starting service on interface: lan 03-22-2011 10:07:44 User.Warning pfsense php: /pkg_edit.php: miniupnpd: Interface opt1 has no ip address, ignoring 03-22-2011 10:07:44 User.Notice pfsense check_reload_status: syncing firewall 03-22-2011 10:07:06 Daemon.Error pfsense miniupnpd[58853]: Failed to open sockets for sending SSDP notify messages. EXITING 03-22-2011 10:07:06 Daemon.Error pfsense miniupnpd[58853]: setsockopt(udp_notify, IP_MULTICAST_IF): Can't assign requested address 03-22-2011 10:07:06 Daemon.Warning pfsense miniupnpd[58853]: Failed to add multicast membership for address 192.168.200.1 03-22-2011 10:07:06 Daemon.Error pfsense miniupnpd[58853]: setsockopt(udp, IP_ADD_MEMBERSHIP): Can't assign requested address 03-22-2011 10:07:06 Daemon.Notice pfsense miniupnpd[58853]: HTTP listening on port 2189 03-22-2011 10:07:06 User.Info pfsense miniupnpd: SNet version started 03-22-2011 10:07:06 Daemon.Error pfsense miniupnpd[61543]: Failed to broadcast good-bye notifications 03-22-2011 10:07:06 Daemon.Error pfsense miniupnpd[61543]: SendSSDPGoodbye: sendto(udp_shutdown=16): Host is down 03-22-2011 10:07:06 Daemon.Notice pfsense miniupnpd[61543]: received signal 15, good-bye 03-22-2011 10:05:35 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:05:35 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:05:35 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:05:35 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:05:35 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:05:35 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:05:35 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:05:35 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:05:05 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:05:05 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:05:05 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:05:05 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:05:05 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:05:05 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:05:05 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:05:05 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:05:02 Cron.Info pfsense cron[24363]: (root) MAIL (mailed 1822 bytes of output but got status 0x0001 ) 03-22-2011 10:05:01 User.Notice pfsense root: Countryblock was found not running 03-22-2011 10:05:01 Cron.Info pfsense /usr/sbin/cron[24866]: (root) CMD (/usr/local/etc/rc.d/countryblock.sh) 03-22-2011 10:05:01 Cron.Info pfsense /usr/sbin/cron[24620]: (root) CMD (/usr/local/pkg/vnstat2.sh) 03-22-2011 10:04:34 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:04:34 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:04:34 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:04:34 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:04:34 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:04:34 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:04:34 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:04:34 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:04:04 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:04:04 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:04:04 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:04:04 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:04:04 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:04:04 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:04:04 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:04:04 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:04:00 Cron.Info pfsense /usr/sbin/cron[7174]: (root) CMD (/usr/local/pkg/vnstat2.sh) 03-22-2011 10:00:08 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 10:00:06 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 10:00:04 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 10:00:03 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:00:03 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:00:03 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:00:03 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:00:03 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:00:03 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:00:03 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:00:03 Daemon.Error pfsense miniupnpd[61543]: sendto(udp_notify=16, 192.168.200.1): Host is down 03-22-2011 10:00:02 Cron.Info pfsense cron[59493]: (root) MAIL (mailed 1822 bytes of output but got status 0x0001 ) 03-22-2011 10:00:02 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 10:00:01 User.Notice pfsense root: Countryblock was found not running 03-22-2011 10:00:00 Cron.Info pfsense cron[59837]: (root) MAIL (mailed 29 bytes of output but got status 0x0001 ) 03-22-2011 10:00:00 Cron.Info pfsense cron[59646]: (root) MAIL (mailed 28 bytes of output but got status 0x0001 ) 03-22-2011 10:00:00 Cron.Info pfsense cron[60112]: (root) MAIL (mailed 43 bytes of output but got status 0x0001 ) 03-22-2011 10:00:00 Cron.Info pfsense /usr/sbin/cron[60125]: (root) CMD (/usr/local/etc/rc.d/countryblock.sh) 03-22-2011 10:00:00 Cron.Info pfsense /usr/sbin/cron[60920]: (root) CMD (/usr/bin/nice -n20 newsyslog) 03-22-2011 10:00:00 Cron.Info pfsense /usr/sbin/cron[60469]: (root) CMD (/usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 virusprot) 03-22-2011 10:00:00 Cron.Info pfsense /usr/sbin/cron[60696]: (root) CMD (/usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 sshlockout) 03-22-2011 10:00:00 Cron.Info pfsense /usr/sbin/cron[60034]: (root) CMD (/usr/local/pkg/vnstat2.sh) 03-22-2011 09:59:59 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 09:59:57 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 09:59:55 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 09:59:53 User.Warning pfsense php: : Gateways status could not be determined, considering all as up/active. 03-22-2011 09:59:53 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 09:59:51 User.Warning pfsense php: : Gateways status could not be determined, considering all as up/active. 03-22-2011 09:59:50 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 09:59:50 User.Error pfsense apinger: Starting Alarm Pinger, apinger(62994) 03-22-2011 09:59:50 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 09:59:50 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 09:59:49 User.Error pfsense apinger: Exiting on signal 15. 03-22-2011 09:59:49 User.Warning pfsense php: : Removing static route for monitor xxx.sub-xxx-xxx-xxx.myvzw.com and adding a new route through xxx.xxx.xxx.xxx 03-22-2011 09:59:49 User.Warning pfsense php: : Removing static route for monitor xxx.sub-xxx-xxx-xxx.myvzw.com and adding a new route through xxx.xxx.xxx.xxx 03-22-2011 09:59:49 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 09:59:48 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 09:59:48 Kernel.Notice pfsense kernel: ovpns2: link state changed to DOWN 03-22-2011 09:59:48 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 09:59:48 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 09:59:48 Kernel.Notice pfsense kernel: ovpns1: link state changed to DOWN 03-22-2011 09:59:48 User.Warning pfsense php: : Resyncing OpenVPN instances for interface WAN. 03-22-2011 09:59:48 Daemon.Info pfsense dnsmasq[25740]: using nameserver 2001:470:20::2#53 03-22-2011 09:59:48 Daemon.Info pfsense dnsmasq[25740]: using nameserver google-public-dns-a.google.com#53 03-22-2011 09:59:48 Daemon.Info pfsense dnsmasq[25740]: using nameserver dns-xxx.xx.xxx.rr.com#53 03-22-2011 09:59:48 Daemon.Info pfsense dnsmasq[25740]: using nameserver xxx.sub-xxx-xxx-xxx.myvzw.com#53 03-22-2011 09:59:48 Daemon.Info pfsense dnsmasq[25740]: reading /etc/resolv.conf 03-22-2011 09:59:48 User.Warning pfsense php: : rc.newwanip: on (IP address: 192.168.201.1) (interface: opt2) (real interface: ovpns2). 03-22-2011 09:59:48 User.Warning pfsense php: : rc.newwanip: Informational is starting ovpns2. 03-22-2011 09:59:47 User.Warning pfsense php: : rc.newwanip: on (IP address: 192.168.200.1) (interface: opt1) (real interface: ovpns1). 03-22-2011 09:59:47 User.Warning pfsense php: : rc.newwanip: Informational is starting ovpns1. 03-22-2011 09:59:47 User.Warning pfsense php: : Forcefully reloading IPsec racoon daemon 03-22-2011 09:59:47 User.Notice pfsense check_reload_status: rc.newwanip starting ovpns2 03-22-2011 09:59:47 Kernel.Notice pfsense kernel: ovpns2: link state changed to UP 03-22-2011 09:59:47 User.Notice pfsense check_reload_status: rc.newwanip starting ovpns1 03-22-2011 09:59:47 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 09:59:47 Kernel.Notice pfsense kernel: ovpns1: link state changed to UP 03-22-2011 09:59:47 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 09:59:46 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 09:59:46 Kernel.Notice pfsense kernel: ovpns1: link state changed to DOWN 03-22-2011 09:59:46 Auth.Info pfsense sshd[2002]: Timeout, client not responding. 03-22-2011 09:59:46 User.Warning pfsense php: : Resyncing OpenVPN instances for interface WAN. 03-22-2011 09:59:46 User.Warning pfsense php: : Forcefully reloading IPsec racoon daemon 03-22-2011 09:59:44 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for 192.168.100.1 03-22-2011 09:59:41 User.Warning pfsense php: : phpDynDNS: (Unknown Response) 03-22-2011 09:59:41 User.Warning pfsense php: : phpDynDNS: PAYLOAD: 03-22-2011 09:59:41 User.Warning pfsense php: : DynDns: Current Service: dyndns 03-22-2011 09:59:41 User.Warning pfsense php: : DynDns: DynDns _checkStatus() starting. 03-22-2011 09:59:41 User.Warning pfsense php: : Curl error occurred: bind failed with errno 49: Can't assign requested address 03-22-2011 09:59:41 User.Warning pfsense php: : DynDns: DynDns _update() starting. 03-22-2011 09:59:41 User.Warning pfsense php: : DynDns debug information: DynDns: cacheIP != wan_ip. Updating. Cached IP: cpe-xxx-xxx-xxx-xxx-cable.com WAN IP: 03-22-2011 09:59:41 User.Warning pfsense php: : DynDns: Cached IP: cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:59:41 User.Warning pfsense php: : DynDns: Current WAN IP: 03-22-2011 09:59:41 User.Warning pfsense php: : DynDns debug information: extracted from checkip.dyndns.org 03-22-2011 09:59:41 User.Warning pfsense php: : DynDns: _checkIP() starting. 03-22-2011 09:59:41 User.Warning pfsense php: : DynDns: _detectChange() starting. 03-22-2011 09:59:41 User.Warning pfsense php: : DynDns: updatedns() starting 03-22-2011 09:59:41 User.Warning pfsense php: : DynDns: Running updatedns() 03-22-2011 09:59:40 User.Warning pfsense php: : DNS-O-Matic: (Unknown Response) 03-22-2011 09:59:40 User.Warning pfsense php: : DNS-O-Matic: PAYLOAD: 03-22-2011 09:59:40 User.Warning pfsense php: : DynDns: Current Service: dnsomatic 03-22-2011 09:59:40 User.Warning pfsense php: : DynDns: DynDns _checkStatus() starting. 03-22-2011 09:59:40 User.Warning pfsense php: : Request completed. DNS-O-Matic reported: bind failed with errno 49: Can't assign requested address 03-22-2011 09:59:40 User.Warning pfsense php: : DNS-O-Matic: DNS update() starting. 03-22-2011 09:59:40 User.Warning pfsense php: : DynDns: DynDns _update() starting. 03-22-2011 09:59:40 User.Warning pfsense php: : DynDns debug information: DynDns: cacheIP != wan_ip. Updating. Cached IP: cpe-xxx-xxx-xxx-xxx-cable.com WAN IP: 03-22-2011 09:59:40 User.Warning pfsense php: : DynDns: Cached IP: cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:59:40 User.Warning pfsense php: : DynDns: Current WAN IP: 03-22-2011 09:59:40 User.Warning pfsense php: : DynDns debug information: extracted from checkip.dyndns.org 03-22-2011 09:59:40 User.Warning pfsense php: : DynDns: _checkIP() starting. 03-22-2011 09:59:40 User.Warning pfsense php: : DynDns: _detectChange() starting. 03-22-2011 09:59:40 User.Warning pfsense php: : DynDns: updatedns() starting 03-22-2011 09:59:40 User.Warning pfsense php: : DynDns: Running updatedns() 03-22-2011 09:59:39 User.Warning pfsense php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. 03-22-2011 09:59:39 User.Warning pfsense php: : DynDns: Cached IP: cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:59:39 User.Warning pfsense php: : DynDns: Current WAN IP: cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:59:39 User.Warning pfsense php: : DynDns debug information: cpe-xxx-xxx-xxx-xxx-cable.com extracted from local system. 03-22-2011 09:59:39 User.Warning pfsense php: : DynDns: _checkIP() starting. 03-22-2011 09:59:39 User.Warning pfsense php: : DynDns: _detectChange() starting. 03-22-2011 09:59:39 User.Warning pfsense php: : DynDns: updatedns() starting 03-22-2011 09:59:39 User.Warning pfsense php: : DynDns: Running updatedns() 03-22-2011 09:59:39 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 09:59:38 User.Warning pfsense php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. 03-22-2011 09:59:38 User.Warning pfsense php: : DynDns: Cached IP: cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:59:38 User.Warning pfsense php: : DynDns: Current WAN IP: cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:59:38 User.Warning pfsense php: : DynDns debug information: cpe-xxx-xxx-xxx-xxx-cable.com extracted from local system. 03-22-2011 09:59:38 User.Warning pfsense php: : DynDns: _checkIP() starting. 03-22-2011 09:59:38 User.Warning pfsense php: : DynDns: _detectChange() starting. 03-22-2011 09:59:38 User.Warning pfsense php: : DynDns: updatedns() starting 03-22-2011 09:59:38 User.Warning pfsense php: : DynDns: Running updatedns() 03-22-2011 09:59:38 User.Warning pfsense php: : phpDynDNS: (Unknown Response) 03-22-2011 09:59:38 User.Warning pfsense php: : phpDynDNS: PAYLOAD: 03-22-2011 09:59:38 User.Warning pfsense php: : DynDns: Current Service: dyndns 03-22-2011 09:59:38 User.Warning pfsense php: : DynDns: DynDns _checkStatus() starting. 03-22-2011 09:59:38 User.Warning pfsense php: : Curl error occurred: Couldn't resolve host 'members.dyndns.org' 03-22-2011 09:59:37 User.Warning pfsense php: : Gateways status could not be determined, considering all as up/active. 03-22-2011 09:59:37 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for 192.168.100.1 03-22-2011 09:59:36 User.Warning pfsense php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. 03-22-2011 09:59:36 User.Warning pfsense php: : DynDns: Cached IP: cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:59:36 User.Warning pfsense php: : DynDns: Current WAN IP: cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:59:36 User.Warning pfsense php: : DynDns debug information: cpe-xxx-xxx-xxx-xxx-cable.com extracted from local system. 03-22-2011 09:59:36 User.Warning pfsense php: : DynDns: _checkIP() starting. 03-22-2011 09:59:36 User.Warning pfsense php: : DynDns: _detectChange() starting. 03-22-2011 09:59:36 User.Warning pfsense php: : DynDns: updatedns() starting 03-22-2011 09:59:36 User.Warning pfsense php: : DynDns: Running updatedns() 03-22-2011 09:59:36 User.Error pfsense apinger: Starting Alarm Pinger, apinger(52353) 03-22-2011 09:59:36 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 09:59:35 User.Error pfsense apinger: Exiting on signal 15. 03-22-2011 09:59:35 User.Warning pfsense php: : Removing static route for monitor xxx.sub-xxx-xxx-xxx.myvzw.com and adding a new route through xxx.xxx.xxx.xxx 03-22-2011 09:59:35 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for 192.168.100.1 03-22-2011 09:59:35 User.Warning pfsense php: : ROUTING: add default route to cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:59:34 User.Warning pfsense php: : rc.newwanip: on (IP address: cpe-xxx-xxx-xxx-xxx-cable.com) (interface: wan) (real interface: em3). 03-22-2011 09:59:34 User.Warning pfsense php: : rc.newwanip: Informational is starting em3. 03-22-2011 09:59:34 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for 192.168.100.1 03-22-2011 09:59:34 Daemon.Info pfsense dhclient[3576]: bound to cpe-xxx-xxx-xxx-xxx-cable.com -- renewal in 21300 seconds. 03-22-2011 09:59:34 User.Notice pfsense check_reload_status: rc.newwanip starting em3 03-22-2011 09:59:34 User.Notice pfsense dhclient: Creating resolv.conf 03-22-2011 09:59:34 User.Notice pfsense dhclient: /sbin/route add default cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:59:34 User.Notice pfsense dhclient: Adding new routes to interface: em3 03-22-2011 09:59:34 User.Notice pfsense dhclient: New Routers (em3): cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:59:34 User.Notice pfsense dhclient: New Broadcast Address (em3): 255.255.255.255 03-22-2011 09:59:34 User.Notice pfsense dhclient: New Subnet Mask (em3): 255.255.248.0 03-22-2011 09:59:34 User.Notice pfsense dhclient: New IP Address (em3): cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:59:34 User.Notice pfsense dhclient: ifconfig em3 inet cpe-xxx-xxx-xxx-xxx-cable.com netmask 255.255.248.0 broadcast 255.255.255.255 03-22-2011 09:59:34 User.Notice pfsense dhclient: Starting add_new_address() 03-22-2011 09:59:34 User.Notice pfsense dhclient: BOUND 03-22-2011 09:59:34 Daemon.Info pfsense dhclient[3576]: DHCPACK from 10.90.128.1 03-22-2011 09:59:34 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 255.255.255.255 port 67 03-22-2011 09:59:34 User.Notice pfsense dhclient: ARPCHECK 03-22-2011 09:59:33 Daemon.Info pfsense dnsmasq[25740]: using nameserver 2001:470:20::2#53 03-22-2011 09:59:33 Daemon.Info pfsense dnsmasq[25740]: using nameserver google-public-dns-a.google.com#53 03-22-2011 09:59:33 Daemon.Info pfsense dnsmasq[25740]: using nameserver dns-xxx.xxx.xxx.rr.com#53 03-22-2011 09:59:33 Daemon.Info pfsense dnsmasq[25740]: using nameserver xxx.sub-xxx-xxx-xxx.myvzw.com#53 03-22-2011 09:59:33 Daemon.Info pfsense dnsmasq[25740]: reading /etc/resolv.conf 03-22-2011 09:59:32 User.Notice pfsense dhclient: ARPSEND 03-22-2011 09:59:32 Daemon.Info pfsense dhclient[3576]: DHCPOFFER from 10.90.128.1 03-22-2011 09:59:32 Daemon.Info pfsense dhclient[3576]: DHCPDISCOVER on em3 to 255.255.255.255 port 67 interval 1 03-22-2011 09:59:32 Daemon.Info pfsense dhclient[3576]: DHCPNAK from 10.90.128.1 03-22-2011 09:59:32 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 255.255.255.255 port 67 03-22-2011 09:59:27 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 192.168.100.1 port 67 03-22-2011 09:59:25 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 192.168.100.1 port 67 03-22-2011 09:59:24 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 192.168.100.1 port 67 03-22-2011 09:59:23 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 192.168.100.1 port 67 03-22-2011 09:59:23 Auth.Info pfsense sshd[2287]: Timeout, client not responding. 03-22-2011 09:59:19 Auth.Info pfsense sshd[118]: Timeout, client not responding. 03-22-2011 09:59:19 Daemon.Info pfsense dhclient[3576]: bound to 192.168.100.2 -- renewal in 4 seconds. 03-22-2011 09:59:19 User.Notice pfsense dhclient: Creating resolv.conf 03-22-2011 09:59:19 User.Notice pfsense dhclient: RENEW 03-22-2011 09:59:19 Daemon.Info pfsense dhclient[3576]: DHCPACK from 192.168.100.1 03-22-2011 09:59:19 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 192.168.100.1 port 67 03-22-2011 09:59:16 User.Warning pfsense php: : DynDns: DynDns _update() starting. 03-22-2011 09:59:16 User.Warning pfsense php: : DynDns debug information: DynDns: cacheIP != wan_ip. Updating. Cached IP: cpe-xxx-xxx-xxx-xxx-cable.com WAN IP: 192.168.100.2 03-22-2011 09:59:16 User.Warning pfsense php: : DynDns: Cached IP: cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:59:16 User.Warning pfsense php: : DynDns: Current WAN IP: 192.168.100.2 03-22-2011 09:59:16 User.Warning pfsense php: : Dyndns debug information: Could not resolve checkip.dyndns.org to ip using interface ip 192.168.100.2. 03-22-2011 09:59:15 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 09:59:15 Daemon.Info pfsense dhclient[3576]: bound to 192.168.100.2 -- renewal in 4 seconds. 03-22-2011 09:59:15 User.Notice pfsense dhclient: Creating resolv.conf 03-22-2011 09:59:15 User.Notice pfsense dhclient: RENEW 03-22-2011 09:59:15 Daemon.Info pfsense dhclient[3576]: DHCPACK from 192.168.100.1 03-22-2011 09:59:15 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 192.168.100.1 port 67 03-22-2011 09:59:14 Daemon.Info pfsense dhclient[3576]: bound to 192.168.100.2 -- renewal in 2 seconds. 03-22-2011 09:59:13 User.Notice pfsense dhclient: Creating resolv.conf 03-22-2011 09:59:13 User.Notice pfsense dhclient: RENEW 03-22-2011 09:59:13 Daemon.Info pfsense dhclient[3576]: DHCPACK from 192.168.100.1 03-22-2011 09:59:13 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 192.168.100.1 port 67 03-22-2011 09:59:12 Daemon.Info pfsense dhclient[3576]: bound to 192.168.100.2 -- renewal in 1 seconds. 03-22-2011 09:59:12 User.Notice pfsense dhclient: Creating resolv.conf 03-22-2011 09:59:12 User.Notice pfsense dhclient: RENEW 03-22-2011 09:59:12 Daemon.Info pfsense dhclient[3576]: DHCPACK from 192.168.100.1 03-22-2011 09:59:12 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 192.168.100.1 port 67 03-22-2011 09:59:12 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 09:59:09 Daemon.Info pfsense dhclient[3576]: bound to 192.168.100.2 -- renewal in 3 seconds. 03-22-2011 09:59:09 User.Notice pfsense dhclient: Creating resolv.conf 03-22-2011 09:59:09 User.Notice pfsense dhclient: RENEW 03-22-2011 09:59:09 Daemon.Info pfsense dhclient[3576]: DHCPACK from 192.168.100.1 03-22-2011 09:59:09 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 192.168.100.1 port 67 03-22-2011 09:59:07 Daemon.Info pfsense dhclient[3576]: bound to 192.168.100.2 -- renewal in 2 seconds. 03-22-2011 09:59:07 User.Notice pfsense dhclient: Creating resolv.conf 03-22-2011 09:59:07 User.Notice pfsense dhclient: RENEW 03-22-2011 09:59:07 Daemon.Info pfsense dhclient[3576]: DHCPACK from 192.168.100.1 03-22-2011 09:59:07 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 192.168.100.1 port 67 03-22-2011 09:59:05 Daemon.Info pfsense dhclient[3576]: bound to 192.168.100.2 -- renewal in 2 seconds. 03-22-2011 09:59:05 User.Notice pfsense dhclient: Creating resolv.conf 03-22-2011 09:59:05 User.Notice pfsense dhclient: RENEW 03-22-2011 09:59:05 Daemon.Info pfsense dhclient[3576]: DHCPACK from 192.168.100.1 03-22-2011 09:59:05 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 192.168.100.1 port 67 03-22-2011 09:59:04 Daemon.Info pfsense dhclient[3576]: bound to 192.168.100.2 -- renewal in 1 seconds. 03-22-2011 09:59:04 User.Notice pfsense dhclient: Creating resolv.conf 03-22-2011 09:59:04 User.Notice pfsense dhclient: RENEW 03-22-2011 09:59:04 Daemon.Info pfsense dhclient[3576]: DHCPACK from 192.168.100.1 03-22-2011 09:59:04 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 192.168.100.1 port 67 03-22-2011 09:59:02 User.Error pfsense apinger: ALARM: HE_Net(2001:470:1f06:e7f::1) *** down *** 03-22-2011 09:59:02 Cron.Info pfsense cron[19049]: (root) MAIL (mailed 96 bytes of output but got status 0x0001 ) 03-22-2011 09:59:01 Daemon.Info pfsense dhclient[3576]: bound to 192.168.100.2 -- renewal in 3 seconds. 03-22-2011 09:59:01 Cron.Info pfsense /usr/sbin/cron[19279]: (root) CMD (/usr/local/pkg/vnstat2.sh) 03-22-2011 09:59:01 User.Notice pfsense dhclient: Creating resolv.conf 03-22-2011 09:59:01 User.Notice pfsense dhclient: RENEW 03-22-2011 09:59:01 Daemon.Info pfsense dhclient[3576]: DHCPACK from 192.168.100.1 03-22-2011 09:59:01 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 192.168.100.1 port 67 03-22-2011 09:59:01 Daemon.Info pfsense dhclient[3576]: bound to 192.168.100.2 -- renewal in 1 seconds. 03-22-2011 09:59:01 User.Notice pfsense dhclient: Creating resolv.conf 03-22-2011 09:59:01 User.Notice pfsense dhclient: RENEW 03-22-2011 09:59:00 Daemon.Info pfsense dhclient[3576]: DHCPACK from 192.168.100.1 03-22-2011 09:59:00 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 192.168.100.1 port 67 03-22-2011 09:59:00 Daemon.Info pfsense dhclient[3576]: bound to 192.168.100.2 -- renewal in 0 seconds. 03-22-2011 09:59:00 User.Notice pfsense dhclient: Creating resolv.conf 03-22-2011 09:59:00 User.Notice pfsense dhclient: RENEW 03-22-2011 09:59:00 Daemon.Info pfsense dhclient[3576]: DHCPACK from 192.168.100.1 03-22-2011 09:59:00 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 192.168.100.1 port 67 03-22-2011 09:58:56 Daemon.Info pfsense dhclient[3576]: bound to 192.168.100.2 -- renewal in 4 seconds. 03-22-2011 09:58:56 User.Notice pfsense dhclient: Creating resolv.conf 03-22-2011 09:58:56 User.Notice pfsense dhclient: RENEW 03-22-2011 09:58:56 Daemon.Info pfsense dhclient[3576]: DHCPACK from 192.168.100.1 03-22-2011 09:58:56 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 192.168.100.1 port 67 03-22-2011 09:58:55 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 09:58:53 User.Warning pfsense php: : Gateways status could not be determined, considering all as up/active. 03-22-2011 09:58:53 Daemon.Info pfsense dhclient[3576]: bound to 192.168.100.2 -- renewal in 3 seconds. 03-22-2011 09:58:53 User.Notice pfsense dhclient: Creating resolv.conf 03-22-2011 09:58:53 User.Notice pfsense dhclient: RENEW 03-22-2011 09:58:53 Daemon.Info pfsense dhclient[3576]: DHCPACK from 192.168.100.1 03-22-2011 09:58:53 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 192.168.100.1 port 67 03-22-2011 09:58:52 User.Warning pfsense php: : DynDns: _checkIP() starting. 03-22-2011 09:58:52 User.Warning pfsense php: : DynDns: _detectChange() starting. 03-22-2011 09:58:52 User.Warning pfsense php: : DynDns: updatedns() starting 03-22-2011 09:58:52 User.Warning pfsense php: : DynDns: Running updatedns() 03-22-2011 09:58:52 User.Error pfsense apinger: Starting Alarm Pinger, apinger(24322) 03-22-2011 09:58:52 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 09:58:51 User.Error pfsense apinger: Exiting on signal 15. 03-22-2011 09:58:51 User.Warning pfsense php: : Removing static route for monitor xxx.sub-xxx-xxx-xxx.myvzw.com and adding a new route through xxx.xxx.xxx.xxx 03-22-2011 09:58:51 User.Warning pfsense php: : ROUTING: change default route to 192.168.100.1 03-22-2011 09:58:50 User.Warning pfsense php: : rc.newwanip: on (IP address: 192.168.100.2) (interface: wan) (real interface: em3). 03-22-2011 09:58:50 User.Warning pfsense php: : rc.newwanip: Informational is starting em3. 03-22-2011 09:58:50 Daemon.Info pfsense dhclient[3576]: bound to 192.168.100.2 -- renewal in 3 seconds. 03-22-2011 09:58:50 User.Notice pfsense dhclient: Creating resolv.conf 03-22-2011 09:58:50 User.Notice pfsense dhclient: RENEW 03-22-2011 09:58:50 Daemon.Info pfsense dhclient[3576]: DHCPACK from 192.168.100.1 03-22-2011 09:58:50 Daemon.Info pfsense dhclient[3576]: DHCPREQUEST on em3 to 192.168.100.1 port 67 03-22-2011 09:58:50 Daemon.Info pfsense dhclient[32509]: bound to 192.168.100.2 -- renewal in 1 seconds. 03-22-2011 09:58:50 User.Notice pfsense check_reload_status: rc.newwanip starting em3 03-22-2011 09:58:50 User.Notice pfsense dhclient: Creating resolv.conf 03-22-2011 09:58:50 User.Notice pfsense dhclient: /sbin/route add default 192.168.100.1 03-22-2011 09:58:49 User.Notice pfsense dhclient: Adding new routes to interface: em3 03-22-2011 09:58:49 User.Notice pfsense dhclient: New Routers (em3): 192.168.100.1 03-22-2011 09:58:49 User.Notice pfsense dhclient: New Broadcast Address (em3): 192.168.100.255 03-22-2011 09:58:49 User.Notice pfsense dhclient: New Subnet Mask (em3): 255.255.255.0 03-22-2011 09:58:49 User.Notice pfsense dhclient: New IP Address (em3): 192.168.100.2 03-22-2011 09:58:49 User.Notice pfsense dhclient: ifconfig em3 inet 192.168.100.2 netmask 255.255.255.0 broadcast 192.168.100.255 03-22-2011 09:58:49 User.Notice pfsense dhclient: Starting add_new_address() 03-22-2011 09:58:49 User.Notice pfsense dhclient: BOUND 03-22-2011 09:58:49 Daemon.Info pfsense dhclient[32509]: DHCPACK from 192.168.100.1 03-22-2011 09:58:49 Daemon.Info pfsense dhclient[32509]: DHCPREQUEST on em3 to 255.255.255.255 port 67 03-22-2011 09:58:49 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:49 User.Notice pfsense dhclient: ARPCHECK 03-22-2011 09:58:47 User.Notice pfsense dhclient: ARPSEND 03-22-2011 09:58:47 Daemon.Info pfsense dhclient[32509]: DHCPOFFER from 192.168.100.1 03-22-2011 09:58:46 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:45 Daemon.Info pfsense dhclient[32509]: DHCPDISCOVER on em3 to 255.255.255.255 port 67 interval 2 03-22-2011 09:58:45 Daemon.Info pfsense dhclient[32509]: DHCPNAK from 192.168.100.1 03-22-2011 09:58:45 Daemon.Info pfsense dhclient[32509]: DHCPREQUEST on em3 to 255.255.255.255 port 67 03-22-2011 09:58:45 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:43 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 09:58:43 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:43 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:43 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:43 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:43 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:43 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:43 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:43 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:43 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:43 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:43 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:43 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:43 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:43 Daemon.Info pfsense dhclient[32509]: DHCPREQUEST on em3 to 255.255.255.255 port 67 03-22-2011 09:58:43 User.Notice pfsense dhclient: PREINIT 03-22-2011 09:58:43 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:43 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:43 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:42 User.Warning pfsense php: : MONITOR: WAN has high latency, removing from routing group 03-22-2011 09:58:42 User.Warning pfsense php: : HOTPLUG: Configuring interface wan 03-22-2011 09:58:42 User.Warning pfsense php: : DEVD Ethernet attached event for wan 03-22-2011 09:58:41 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 09:58:41 Kernel.Notice pfsense kernel: em3: link state changed to UP 03-22-2011 09:58:41 User.Notice pfsense check_reload_status: Linkup starting em3 03-22-2011 09:58:41 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:41 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:41 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:41 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:41 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:41 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:41 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:41 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:41 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:41 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:41 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:41 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:41 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:40 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:40 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:40 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:40 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:40 User.Warning pfsense php: : MONITOR: WAN has high latency, removing from routing group 03-22-2011 09:58:39 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 09:58:38 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 09:58:38 Kernel.Notice pfsense kernel: ovpns2: link state changed to DOWN 03-22-2011 09:58:38 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:38 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:36 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:36 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:35 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:34 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:33 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 09:58:33 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:33 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:33 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:33 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:33 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:33 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:33 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:33 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:33 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:33 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:33 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:33 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:33 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:33 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:33 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:33 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:33 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:33 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:33 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:33 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:33 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:33 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:32 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:32 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:32 User.Warning pfsense php: : MONITOR: WAN has high latency, removing from routing group 03-22-2011 09:58:31 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 09:58:29 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:29 User.Error pfsense apinger: alarm canceled: VERIZON3G(xxx.sub-xxx-xxx-xxx.myvzw.com) *** delay *** 03-22-2011 09:58:28 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:28 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:26 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:26 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:22 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:22 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:21 User.Error pfsense apinger: ALARM: VERIZON3G(xxx.sub-xxx-xxx-xxx.myvzw.com) *** delay *** 03-22-2011 09:58:19 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:19 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:19 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:17 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:16 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:16 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:13 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:11 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:11 User.Warning pfsense php: : Sending HUP signal to 28248 03-22-2011 09:58:11 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:11 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:11 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:11 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:11 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:11 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:11 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:11 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:11 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:11 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:10 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:10 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:10 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:10 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:10 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:10 User.Warning pfsense php: : Could not find IPv4 gateway for interface(wan). 03-22-2011 09:58:10 User.Warning pfsense php: : MONITOR: WAN has high latency, removing from routing group 03-22-2011 09:58:09 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:08 User.Notice pfsense check_reload_status: reloading filter 03-22-2011 09:58:03 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:03 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:03 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:03 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:03 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:03 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:03 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:03 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:03 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:03 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:01 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:58:01 Cron.Info pfsense /usr/sbin/cron[29340]: (root) CMD (/usr/local/pkg/vnstat2.sh) 03-22-2011 09:57:59 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:57:58 User.Error pfsense apinger: ALARM: HE_Net(2001:470:1f06:e7f::1) *** down *** 03-22-2011 09:57:58 User.Error pfsense apinger: ALARM: WAN(cpe-xxx-xxx-xxx-xxx-cable.com) *** down *** 03-22-2011 09:57:57 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:57:56 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:57:55 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:57:53 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:57:52 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:57:52 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:57:52 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:57:50 Kernel.Debug pfsense kernel: arpresolve: can't allocate llinfo for cpe-xxx-xxx-xxx-xxx-cable.com 03-22-2011 09:57:49 Daemon.Critical pfsense dhclient[10925]: exiting. 03-22-2011 09:57:49 Daemon.Error pfsense dhclient[10925]: connection closed 03-22-2011 09:57:49 User.Warning pfsense php: : DEVD Ethernet detached event for wan 03-22-2011 09:57:49 Kernel.Notice pfsense kernel: em3: link state changed to DOWN 03-22-2011 09:57:49 User.Notice pfsense check_reload_status: Linkup starting em3 -
I just remember the issue I had with my setup.. My IP address would renew if I: power cycle the modem, disconnected/reconnect the cable coax, and/or unplug/plug the LAN cable between the cable modem and my pfsense router. What didn't renew were the IP addresses to the cable providers DNS server. I setup monit to just reboot the box, that would fix it. Since i'm mulit-wan and have the ipv6 code on my box now, I manually added DNS IPs under the General Setup page.
-
Cino,
Thanks, I like the monit solution and will implement that as an interim solution. However, the question remains. Is this a freebsd driver issue, or a bug? Because I have 3 of these boxes, one running Ubuntu, one with Centos, and one with Pfsense. The first two have no problem renewing/pulling an IP after a disconnect. But, the Pfsense one will not perform correctly no matter what I put in front of it.
-
Administrator,
Please forgive me if I am beating a dead horse.
After some further testing and research in the forum, it seems this problem only happens when I spoof the WAN MAC address, And, it appears to be related to this other thread and bug already reported…
http://forum.pfsense.org/index.php?topic=34094.0
http://redmine.pfsense.org/issues/1337Is it the same or should it have it's own issue#? Thanks.
PB
Supermicro x7spa-hf
pfSense-2.0-RC1-i386-20110320-1800 -
I don't know if this will help, but update your bios if you haven't. X7SPA0.C17 http://www.supermicro.com/support/resources/getfile.aspx?ID=1124
