Network Problem Solved but.....
Peter
plp-ysDPMY98cNQDDBjDh4tngg at public.gmane.org
Sat Nov 19 19:03:01 UTC 2005
On Thu, 17 Nov 2005, Imran . wrote:
> Okay. Problem is solved. I looked at router's routing table and i am
> wondering why it was like this?
> First let me tell u my network settings:
> IP address of Router : 192.168.2.1
> IP address of Laptop: 192.168.2.101
> IP address of 2nd PC : 192.168.2.100 (Problematic)
>
> Now, look at the router's routing table below. 192.168.2.0 network is
> directly connected. However, for 192.168.2.100 it got a gateway address
> through ICMP redirect 84.63.0.1. So in order to reach this sytem it was
> trying the gateway 84.53.0.1. Now i am wondering how this ICMP redirect
> happened? does it have to do something with security?
>
> here is a part of routing table:
> ------------------------------------------------------------
> Flags Network Address Netmask Gateway
> Interface
> I 192.168.2.100 255.255.255.255 84.63.0.1
> 9xÜ9X!Ü9L
> C 192.168.2.0 255.255.255.0 directly
> LAN
> I 192.168.2.2 255.255.255.255 81.202.40.1
> 9xÜ9X!Ü9L
>
> Flags : C - directly connected, S - static, R - RIP, I - ICMP Redirect
> ---------------------------------------------------------------------
> So i just reset router settings and now it doesn't have 84.63.0.1 as gateway
> for 192.168.2.100. So now both linux and windows are working fine. however, i
> should have saved router's log but i forgot. i have firewalled disabled on
> router. should i turn it on?
I don't know if it matters but your email contains several unicode
characters where only ASCII schould be used. Maybe this is causing your
problems. Make sure you use an ASCII editor when editing the config
files and use all ASCII host names. In the file above the hosts
192.168.2.100 and 192.168.2.2 (aka 81.202.40.1) had 'problem' names.
Peter
More information about the Legacy
mailing list