Hi all, since the latest update(9.1) on startup KDM has a rather droll message in the log: <snip> Sep 2 13:41:36 buddha kdm[3406]: Cannot convert Internet address 4.0.1.64 to host name </snip> So I checked: host 4.0.1.64: Host 64.1.0.4.in-addr.arpa not found: 3(NXDOMAIN) O well...now what adress might this be, and why is KDM calling out. I am sitting behind two Firewalls, so there is really no reason :-( Anyone else seen this ? Regards Dan -- buddha 2.6.4-54.5-default 9:05am an 19:31, 1 Benutzer,
O well...now what adress might this be, and why is KDM calling out. I am sitting behind two Firewalls, so there is really no reason :-(
ogley@jogley:~> whois 4.0.1.64 OrgName: Level 3 Communications, Inc. OrgID: LVLT Address: 1025 Eldorado Blvd. City: Broomfield StateProv: CO PostalCode: 80021 Country: US NetRange: 4.0.0.0 - 4.255.255.255 CIDR: 4.0.0.0/8 NetName: LVLT-ORG-4-8 NetHandle: NET-4-0-0-0-1 Parent: NetType: Direct Allocation NameServer: NS1.LEVEL3.NET NameServer: NS2.LEVEL3.NET Comment: RegDate: Updated: 2004-06-04 -- James Ogley, Webmaster, usr local bin & Planet SuSE james@rubberturnip.org.uk www.rubberturnip.org.uk Updated GNOME packages for SUSE LINUX: www.usr-local-bin.org Latest SUSE News and Blogs: www.planetsuse.org
On Thursday 02 September 2004 05:44, James Ogley wrote:
O well...now what adress might this be, and why is KDM calling out. I am sitting behind two Firewalls, so there is really no reason :-(
ogley@jogley:~> whois 4.0.1.64
OrgName: Level 3 Communications, Inc. OrgID: LVLT Address: 1025 Eldorado Blvd. City: Broomfield StateProv: CO PostalCode: 80021 Country: US
NetRange: 4.0.0.0 - 4.255.255.255 CIDR: 4.0.0.0/8 NetName: LVLT-ORG-4-8 NetHandle: NET-4-0-0-0-1 Parent: NetType: Direct Allocation NameServer: NS1.LEVEL3.NET NameServer: NS2.LEVEL3.NET Comment: RegDate: Updated: 2004-06-04 -- James Ogley, Webmaster, usr local bin & Planet SuSE james@rubberturnip.org.uk www.rubberturnip.org.uk Updated GNOME packages for SUSE LINUX: www.usr-local-bin.org Latest SUSE News and Blogs: www.planetsuse.org
I tracerout'ed this address, but the result confuses me, since the traceroute appears to terminate at an entirely different IP: (I've obliterated my own IP): % traceroute 4.0.1.64 traceroute to 4.0.1.64 (4.0.1.64), 30 hops max, 40 byte packets 1 me.sonic.net (me.me.me.me) 27.655 ms 28.940 ms 27.073 ms 2 fast1-0-0.border.sr.sonic.net (208.201.224.194) 29.281 ms 27.715 ms 25.312 ms 3 fast4-1-0.border2.sr.sonic.net (64.142.0.26) 35.095 ms 33.200 ms 31.102 ms 4 GigabitEthernet1-0.GW1.SJC7.ALTER.NET (157.130.214.177) 32.586 ms 30.642 ms 29.782 ms 5 POS1-0.XR2.SJC7.ALTER.NET (152.63.53.194) 28.262 ms 29.337 ms 25.263 ms 6 0.so-4-3-0.XL2.SCL2.ALTER.NET (152.63.52.141) 22.739 ms 28.665 ms 22.325 ms 7 0.so-5-1-0.BR1.SCL2.ALTER.NET (152.63.48.9) 24.420 ms 23.998 ms 25.223 ms 8 204.255.173.42 24.951 ms 25.411 ms 24.888 ms 9 so-1-2-0.bbr1.SanJose1.Level3.net (209.244.3.137) 24.619 ms 25.583 ms so-1-2-0.bbr2.SanJose1.Level3.net (209.244.3.141) 27.270 ms 10 ge-5-2.core1.SanJose1.Level3.net (64.159.2.165)(H!) 28.487 ms ge-4-1.core1.SanJose1.Level3.net (64.159.2.69)(H!) 29.180 ms * Randall Schulz
On Thu, 2004-09-02 at 14:29 +0100, Dan Am wrote:
Hi all,
since the latest update(9.1) on startup KDM has a rather droll message in the log: <snip> Sep 2 13:41:36 buddha kdm[3406]: Cannot convert Internet address 4.0.1.64 to host name
As far as I can see, the only time KDM prints that string is when it receives an incoming xdmcp connection attempt. So I'd check what's going on on your LAN if I were you
Hi all, Am Thursday 02 September 2004 13:50 schrieb Anders Johansson:
As far as I can see, the only time KDM prints that string is when it receives an incoming xdmcp connection attempt. So I'd check what's going on on your LAN if I were you Incoming xdmcp alright... I am using that protocol. From the above I seem to see that you are able to duplicate this ? Regards -- buddha 2.6.4-54.5-default 9:05am an 19:31, 1 Benutzer,
On Fri, 2004-09-03 at 09:10 +0100, Dan Am wrote:
Hi all, Am Thursday 02 September 2004 13:50 schrieb Anders Johansson:
As far as I can see, the only time KDM prints that string is when it receives an incoming xdmcp connection attempt. So I'd check what's going on on your LAN if I were you Incoming xdmcp alright... I am using that protocol. From the above I seem to see that you are able to duplicate this ?
Yes, I can duplicate it by trying to connect to xdmcp with a machine with an IP address that doesn't have a reverse mapping to a name. I haven't seen it with the IP you mentioned, or any other IP except the one I tested with since I'm blocking external connections to port 177. I checked the source to see under what circumstances KDM would log something like that, and it will only happen on an incoming xdmcp connection, never else.
On Thu, 2004-09-02 at 09:29, Dan Am wrote:
Hi all,
since the latest update(9.1) on startup KDM has a rather droll message in the log: <snip> Sep 2 13:41:36 buddha kdm[3406]: Cannot convert Internet address 4.0.1.64 to host name </snip> So I checked: host 4.0.1.64: Host 64.1.0.4.in-addr.arpa not found: 3(NXDOMAIN) O well...now what adress might this be, and why is KDM calling out. I am sitting behind two Firewalls, so there is really no reason :-( Anyone else seen this ? Regards
Dan -- buddha 2.6.4-54.5-default 9:05am an 19:31, 1 Benutzer,
You might want to report this to Level3 abuse@level3.com Someone from one of their IP's tried to break into one of my servers recently, I reported it and they seem to want to catch the hackers. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2) * PLEASE only reply to the list *
participants (5)
-
Anders Johansson -
Dan Am -
James Ogley -
Ken Schneider -
Randall R Schulz