Honeypots mailing list archives
Re: ODP: No reverse routing map for 10.0.0.100
From: wan fat wu <thizthiz () yahoo com hk>
Date: Mon, 12 Apr 2004 14:03:20 +0800 (CST)
HI Mariusz Burdach, I have read the following email and also tried the suggestion from you. Now I can ping the router. However, I can't ping virtual machines under network 10.0.1.0/24. I have set the personality of IP 10.0.1.100 to window. When I ping it, it is out of respond. Could you tell me what's wrong? One more question what is the meaning of 10.0.0.100/32? Thanks a lot! Best, Fred new config: route entry 10.0.0.100 route 10.0.0.100 link 10.0.0.100/32 route 10.0.0.100 link 10.0.1.0/24 route 10.0.0.100 add net 10.1.0.0/24 10.0.1.1 route 10.0.1.1 link 10.1.0.0/24 Mariusz Burdach <M_Burdach () compfort pl> wrote: Hello, Try to add the following entry to your configuration file: ++route 10.0.0.100 link 10.0.0.100/32 and add route entry in the route table to new network by using the route command. Best regards, Mariusz Burdach -----Wiadomo?? oryginalna----- Od: chunsheng fu [mailto:chunsheng.fu () nutechsolutions com] Wys?ano: Pn 2004-04-05 17:21 Do: Niels Provos; Our-team DW: honeypots () securityfocus com Temat: No reverse routing map for 10.0.0.100 Hi, I used the following Honeyd configure file(Config1.conf) and tried to ping 10.0.0.100 from a Windows machine. The ping command returns "Request timed out". It is okay to ping other IPs such as 10.0.1.1. Since I started Honeyd without daemonizing it, then I went back to the Honeyd screen and saw the "No reverse routing map for 10.0.0.100". If I try "tracert 10.1.0.1", then it can return the right topology. The funny thing about this is when I changed to "Config2.conf" following Niels's paper"Honeyd: A Virtual Honeypot Daemon", then both ping and tracert will not work. ping command did not work for any IPs. I attached Honeyd's onscreen message to Config2.conf. It seems ICMP reply messages are normal. Can any one of you give me a clue? 1 * * * Request timed out. 2 20 ms 60 ms 10 ms 10.0.1.1 3 30 ms 80 ms 80 ms 10.1.0.1 Config1.conf: route entry 10.0.0.100 route 10.0.0.100 link 10.0.1.0/24 route 10.0.0.100 add net 10.1.0.0/24 10.0.1.1 route 10.0.1.1 link 10.1.0.0/24 Config2.conf: route entry 10.0.0.100 route 10.0.0.100 link 10.0.0.0/24 route 10.0.0.100 add net 10.1.0.0/16 10.1.0.1 route 10.0.0.100 add net 10.2.0.0/16 10.2.0.1 route 10.1.0.1 link 10.1.0.0/24 route 10.2.0.1 link 10.2.0.0/24 honeyd[1815]: Sending ICMP Echo Reply: 10.0.0.100 -> 10.0.0.42 honeyd[1815]: Sending ICMP Echo Reply: 10.0.0.100 -> 10.0.0.42 honeyd[1815]: Sending ICMP Echo Reply: 10.0.0.100 -> 10.0.0.42 honeyd[1815]: Sending ICMP Echo Reply: 10.0.0.100 -> 10.0.0.42 honeyd[1815]: Connection to closed port: udp (10.0.0.42:137 - 10.1.0.1:137) honeyd[1815]: Connection to closed port: udp (10.0.0.42:137 - 10.1.0.1:137) honeyd[1815]: Connection to closed port: udp (10.0.0.42:137 - 10.1.0.1:137) honeyd[1815]: TTL exceeded for dst 10.1.0.1 at gw 10.0.0.100 honeyd[1815]: TTL exceeded for dst 10.1.0.1 at gw 10.0.0.100 honeyd[1815]: TTL exceeded for dst 10.1.0.1 at gw 10.0.0.100 honeyd[1815]: Sending ICMP Echo Reply: 10.1.0.1 -> 10.0.0.42 honeyd[1815]: Sending ICMP Echo Reply: 10.1.0.1 -> 10.0.0.42 Thanks a lot. -CF 必殺技、飲歌、小星星... 浪漫鈴聲 情心連繫 http://ringtone.yahoo.com.hk/
Current thread:
- ODP: No reverse routing map for 10.0.0.100 Mariusz Burdach (Apr 05)
- Re: ODP: No reverse routing map for 10.0.0.100 wan fat wu (Apr 13)
- <Possible follow-ups>
- Re: ODP: No reverse routing map for 10.0.0.100 Mariusz Burdach (Apr 14)