On Sun, 2006-09-24 at 10:48 -0400, Ric Moore wrote: > Does anyone recognize this?? > > root@iam etc]# rc.d/init.d/network start > Bringing up loopback interface: [ OK ] > Bringing up interface eth0: RTNETLINK answers: Invalid argument You might want to post your networkworking scripts related to the ethernet. "ll /etc/sysconfig/network*" to go looking for them, or: "locate eth |grep /etc", if the drive has been indexed recently. > What is really strange is this... > > [root@iam etc]# more hosts > # Do not remove the following line, or various programs > # that require network functionality will fail. > 127.0.0.1 localhost.localdomain localhost iam > 70.145.234.214 iam.wayward4now.net wayward4now.net > > > Notice the alias iam on the localhost line? WTF? Since when would > anything get added other than localhost.localdomain and localhost? Depending on your network setup, you might want to go around disabling various auto-configuration systems. But we don't know enough about your network to start you off in the right direction. > This is pretty crucial as I have people from www.prisontalk.com "coming > in to visit today" after church... at least I don't have to dress or put > on clothes. Up again until 5AM, this is really old. Too much information, I think... That's a strange church you're involved with, don't drop the soap... Sorry, could not resist. > Now I'm back in DHCP mode with the DSL modem and still get Is your modem just a modem, or does it act as a router as well? Have you powered off and on your modem to reset it? What's DHCP doing? Your router configuring your internal network? Your ISP configuring your PC to have a real public IP? > Error while performing operation. > Host lookup failed: smtp.googlemail.com: Temporary failure in name > resolution > > It's slow as hell, too. Something somewhere having something to do with > named I'm guessing. Was that BIND issue resolved?? ls this helpful? From > messages: note: I'm in DHCP mode and STILL getting errors resolving! > > Sep 24 09:06:51 iam ntpd[1919]: sendto(192.168.1.254): Invalid argument > <----- that's the DSL modem, > Sep 24 09:23:56 iam last message repeated 3 times > Sep 24 09:24:04 iam last message repeated 2 times NTP (network time protocol) is hoping to use your router as its time server. It mightn't provide that. You might want to try pool.ntp.org instead. See <http://www.pool.ntp.org/> for more information. > Sep 24 09:37:34 iam named[1644]: unexpected RCODE (SERVFAIL) resolving 'oasc04008.247realmedia.com/AAAA/IN': 192.168.1.254#53 The AAAA bit is trying to find an IPv6 address for it. There may not be one (quite normal). Your ISP may not support IPv6 (quite common). You probably don't need to know it anyway, just about everything is still using IPv4 addressing. > Sep 24 09:37:45 iam named[1644]: lame server resolving 'oasc04a.247realmedia.com' (in 'oasc04a.247realmedia.com'?): 64.191.219.251#53 > Sep 24 09:37:45 iam named[1644]: lame server resolving 'oasc04a.247realmedia.com' (in 'oasc04a.247realmedia.com'?): 64.58.81.251#53 It's resolving it, but getting the answer in a bad way. > Sep 24 09:43:14 iam named[1644]: unexpected RCODE (SERVFAIL) resolving '97.1.168.192.in-addr.arpa/PTR/IN': 192.168.1.254#53 I can't resolve that, either. There may not be an reverse lookup answer to that (97.1.168.192.in-addr.arpa) address. > Sep 24 09:58:04 iam ntpd[1919]: sendto(192.168.1.254): Invalid argument > Sep 24 09:58:10 iam last message repeated 2 times > Sep 24 10:05:50 iam ntpd[1919]: can't open /var/lib/ntp/drift.TEMP: Permission denied > Sep 24 10:15:10 iam ntpd[1919]: sendto(192.168.1.254): Invalid argument > Sep 24 10:32:15 iam last message repeated 3 times Are you using your modem as your local DNS server? Do you want to / need to? > when I type route is stalls a bit then I get this: > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 > 169.254.0.0 * 255.255.0.0 U 0 0 0 eth0 > default 192.168.1.254 0.0.0.0 UG 0 0 0 eth0 Looks normal enough. > I don't recognize 169.254.0.0 either. Google up on link local, zeroconf, or bonjour (Apple's name for it). If there's no DHCP server to be found by a PC, it'll eventually try giving itself a randomly chosen 168.254.x.y IP, and will also try to avoid picking the same x and y values as something else on your local network. It's for all "peer-to-peer" networking, without any servers. Even if your system hasn't used a link local address on one of its interfaces, there always seems to be an entry preset for it in the routing table, just in case. In your case, I'd probably just ignore this. You might want to play with the dig tool, it'll let you query different name servers, and shows how long it took to get the answer. e.g. "dig google.com" will query whatever name servers you've got configured in your /etc/resolv.conf file. "dig google.com @216.239.38.10" will query the name server at the address after the @ sign - in this case, one of google's master name servers). You could try querying the name server on your PC (127.0.0.1), the one on your router (192.168.0.254), and your ISP's name servers. -- (Currently running FC4, occasionally trying FC5.) Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
