Every night when i check my mail with fetchmail I receive this message ... maurerfranklin@VMXLinux:~> fetchmail fetchmail: couldn't find canonical DNS name of mail.comcast.net (mail.comcast.net) fetchmail: Query status=11 (DNS) This is usually followed by a query status 2 temporary name server error, for my other email accounts.(no mail tonight) I have to ping the gateway in order to get fetchmail, and my internet connection, to work properly . It's odd that It works fine in the morning, if it didn't and i always had to ping the gateway I'd assume I had set it up wrong. I have tried leaving the computer on while at work but ran into the same problem when i got home. I have dhcp modify resolv.conf in yast. Which has ... search audubn01.nj.comcast.net nameserver 68.46.144.5 nameserver 68.46.144.6 I have the routing info set to 192.168.1.1 Has anyone run into this? or know how to fix it? I was blaming comcast but it seems to work when I go into windows(without pinging) but not until I ping the gateway using linux. I did notice this in my localmessages... Nov 1 21:12:32 linux dhcpcd[1229]: broadcasting DHCP_DISCOVER Nov 1 21:12:33 linux dhcpcd[1229]: broadcastAddr option is missing in DHCP server response. Assuming 192.168.1.255 Nov 1 21:12:33 linux dhcpcd[1229]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Nov 1 21:12:33 linux dhcpcd[1229]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec Nov 1 21:12:33 linux dhcpcd[1229]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec Nov 1 21:12:33 linux dhcpcd[1229]: DHCP_OFFER received from (192.168.1.1) Nov 1 21:12:33 linux dhcpcd[1229]: broadcasting DHCP_REQUEST for 192.168.1.100 Nov 1 21:12:33 linux dhcpcd[1229]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Nov 1 21:12:33 linux dhcpcd[1229]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec Nov 1 21:12:33 linux dhcpcd[1229]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec Nov 1 21:12:33 linux dhcpcd[1229]: DHCP_ACK received from (192.168.1.1) Nov 1 21:12:33 linux dhcpcd[1233]: terminating on signal 15 Nov 1 21:44:31 linux dhcpcd[1588]: terminating on signal 15 Nov 1 21:45:15 linux dhcpcd[8982]: terminating on signal 15 Nov 1 22:39:05 VMXLinux checkproc: checkproc: cannot stat /sbin/evSubagent: No such file or directory Nov 2 08:00:41 VMXLinux dhcpcd[945]: terminating on signal 15 Nov 2 08:04:58 VMXLinux dhcpcd[3146]: terminating on signal 15 Nov 2 22:17:21 VMXLinux checkproc: checkproc: cannot stat /sbin/evSubagent: No such file or directory Nov 8 18:59:07 VMXLinux dhcpcd[923]: terminating on signal 15 Nov 9 22:50:38 VMXLinux dhcpcd[968]: terminating on signal 15 TIA -- E.F.Maurer Using SuSE 9.0 Pro
On 11/10/2003 09:40 PM, E.F.Maurer wrote:
Has anyone run into this? or know how to fix it?
Nov 1 21:12:33 linux dhcpcd[1229]: DHCP_OFFER received from (192.168.1.1) Nov 1 21:12:33 linux dhcpcd[1229]: broadcasting DHCP_REQUEST for 192.168.1.100 Nov 1 21:12:33 linux dhcpcd[1229]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Nov 1 21:12:33 linux dhcpcd[1229]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec Nov 1 21:12:33 linux dhcpcd[1229]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec Nov 1 21:12:33 linux dhcpcd[1229]: DHCP_ACK received from (192.168.1.1) Nov 1 21:12:33 linux dhcpcd[1233]: terminating on signal 15 Nov 1 21:44:31 linux dhcpcd[1588]: terminating on signal 15 Nov 1 21:45:15 linux dhcpcd[8982]: terminating on signal 15
I would recommend using the ISC dhclient instead of dhcpcd. It has always worked flawlessly for me here, whereas dhcpcd was more flaky. I never even had the desire to track it down since I started with dhclient in 6.4 and was more familiar with it. dhcpcd must work OK for someone for SuSE to install it as the default, but I had more problems with it. YMMV. BTW, I am also on a cable modem. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
On Monday 10 November 2003 9:36 am, Joe Morris (NTM) wrote:
On 11/10/2003 09:40 PM, E.F.Maurer wrote:
Has anyone run into this? or know how to fix it?
Nov 1 21:12:33 linux dhcpcd[1229]: DHCP_OFFER received from (192.168.1.1) Nov 1 21:12:33 linux dhcpcd[1229]: broadcasting DHCP_REQUEST for 192.168.1.100
I would recommend using the ISC dhclient instead of dhcpcd. It has always worked flawlessly for me here, whereas dhcpcd was more flaky. I never even had the desire to track it down since I started with dhclient in 6.4 and was more familiar with it. dhcpcd must work OK for someone for SuSE to install it as the default, but I had more problems with it. YMMV. BTW, I am also on a cable modem.
Thanks Joe, I installed the isc dhclient, and removed dhcpd. I'll let you know if I run into the problem again. -- E.F.Maurer Using SuSE 9.0 Pro
On 11/11/2003 03:19 AM, E.F.Maurer wrote:
On Monday 10 November 2003 9:36 am, Joe Morris (NTM) wrote:
On 11/10/2003 09:40 PM, E.F.Maurer wrote:
Nov 1 21:12:33 linux dhcpcd[1229]: DHCP_OFFER received from
I would recommend using the ISC dhclient instead of dhcpcd. It has always worked flawlessly for me here, whereas dhcpcd was more flaky.
Thanks Joe, I installed the isc dhclient, and removed dhcpd. I'll let you know if I run into the problem again.
Just to be sure, we are talking about dhclient vs dhcpcd, not dhcpd. DHCPD is the ISC dhcp server program, dhclient is their client program. I don't know who makes dhcpcd, but wanted to make sure you uninstalled the correct program. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
On Monday 10 November 2003 7:11 pm, Joe Morris (NTM) wrote:
On 11/11/2003 03:19 AM, E.F.Maurer wrote:
On Monday 10 November 2003 9:36 am, Joe Morris (NTM) wrote:
On 11/10/2003 09:40 PM, E.F.Maurer wrote:
Nov 1 21:12:33 linux dhcpcd[1229]: DHCP_OFFER received from
I would recommend using the ISC dhclient instead of dhcpcd. It has always worked flawlessly for me here, whereas dhcpcd was more flaky.
Thanks Joe, I installed the isc dhclient, and removed dhcpd. I'll let you know if I run into the problem again.
Just to be sure, we are talking about dhclient vs dhcpcd, not dhcpd. DHCPD is the ISC dhcp server program, dhclient is their client program. I don't know who makes dhcpcd, but wanted to make sure you uninstalled the correct program.
Thanks for your reply, I have dhcp, dhcp-client, and dhcp-server installed, all of which mention isc. I guess I uninstalled dhcpcd(?) because dhcpd still shows in the run level editor... but then again my router is my dhcp server so the daemon was never running. Anyway, the problem resurfaced at about 6 pm. After i pinged the gateway fetchmail ran fine. This time there was no pertinant info in localmessages. Is there anything in linux that would need to make a connection to the namesarver every few hours that could be causing this? Or anything that would run or reset at about 6 pm? It happens right about dinner time, i usually get home from work at about 6:30 - 7 pm, which is when i notice it. I'm utterly confused about what is happening. Do I need anything in /etc/resolv.conf or is the router info sufficient? The router knows the nameservers, does linux need to know them to? Thanks for your help. -- E.F.Maurer Using SuSE 9.0 Pro
participants (2)
-
E.F.Maurer -
Joe Morris (NTM)