I'm hoping the log entries below will help because I'm not familiar with tcpdump yet (spoiled GUI user where packet-capturing is concerned).
Mar 5 21:34:01 kernel: arpresolve: can't allocate route for 192.168.0.1 Mar 5 21:34:01 kernel: arplookup 192.168.0.1 failed: host is not on local network Mar 5 21:33:43 dhclient[80556]: bound: renewal in 27102 seconds. Mar 5 21:33:42 dhclient[80556]: Trying recorded lease 192.168.0.2 <-- This looks interesting Mar 5 21:33:42 dhclient[80556]: No DHCPOFFERS received. Mar 5 21:33:31 last message repeated 3 times Mar 5 21:33:12 kernel: arpresolve: can't allocate route for 192.168.0.1 Mar 5 21:33:12 kernel: arplookup 192.168.0.1 failed: host is not on local network Mar 5 21:33:00 kernel: arpresolve: can't allocate route for 192.168.0.1 Mar 5 21:33:00 kernel: arplookup 192.168.0.1 failed: host is not on local network Mar 5 21:32:58 dhclient[80556]: DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 11 Mar 5 21:32:48 dhclient[80556]: DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 10 Mar 5 21:32:43 dhclient[80556]: DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 5 Mar 5 21:32:41 dhclient[80556]: DHCPDISCOVER on sk0 to 255.255.255.255 port 67 interval 2 Mar 5 21:32:34 last message repeated 3 times Mar 5 21:32:28 php: : Not a valid interface action "" Mar 5 21:32:28 php: : Processing - Mar 5 21:32:28 php: : Not a valid interface action "" Mar 5 21:32:28 php: : Processing start - Mar 5 21:32:28 php: : HOTPLUG: Configuring optional interface - opt Mar 5 21:32:28 php: : DEVD Ethernet attached event for sk0 Mar 5 21:32:28 php: : Processing sk0 - start Mar 5 21:32:28 check_reload_status: rc.linkup starting Mar 5 21:32:26 dhclient[80556]: DHCPREQUEST on sk0 to 255.255.255.255 port 67 Mar 5 21:32:26 kernel: sk0: link state changed to UP Mar 5 21:32:24 kernel: sk0: link state changed to DOWN Mar 5 21:32:19 syslogd: kernel boot file is /boot/kernel/kernel -----Original Message----- From: Chris Buechler [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2008 3:27 PM To: support@pfsense.com Subject: Re: [pfSense Support] Message repeating in System Log, can't find the reason Michael Richardson wrote: > My reasons are two-fold. One is as Chris said, I work from home AND have > servers in the home that need to remain accessible to my hosted servers. > > The 2nd is because I do a significant amount of off-site backups in 2 > directions so a 2nd line allows me to saturate one with file transfers > without affecting my more casual activities. > > I'd like to thank everyone for engaging in this dialog and helping out. I'm > still having the same problem though. My 2nd WAN interface refuses to pull > an IP via DHCP and by testing with the 1st interface, and other devices I > know that the modem is more than happy to hand one out. How do I go about > troubleshooting this? > tcpdump on the interface and see what's really happening. Also I haven't read the entirety of this really long thread, if you've already sent logs from dhclient please re-send them. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
