[NBLUG/talk] Changed Network

[Walter Hansen]

After fishing with it I don't think it's a problem, but I could be wrong.
192.168.100.100 is the second router from the host. All it seems to mean
is that packets went out to that router.

router1 192.168.33.100
router2 192.168.100.100


>
>> while googling I found someone asking about this. does this shed some
>> light to anyone? Why am I seeing 192.168.100 network someplaces? This
>> computer was never on the 192.168.100 network, but there is one one
>> router away.
>>
>> [root at amanda root]# route -C -n
>> Kernel IP routing cache
>> Source          Destination     Gateway         Flags Metric Ref
>> Use Iface 192.168.33.1    192.168.33.255  192.168.33.255  ibl   0
>> 0
>>    0 lo 192.168.33.1    192.168.33.211  192.168.33.211  il    0      0
>> 147 lo 192.168.33.251  192.168.33.255  192.168.33.255  ibl   0
>> 0
>>        0 lo 192.168.100.100 192.168.33.211  192.168.33.211  l     0
>> 0     1040 lo 192.168.33.3    192.168.33.255  192.168.33.255  ibl   0
>>   0       32 lo 192.168.33.250  192.168.33.255  192.168.33.255  ibl
>> 0
>>     0      218 lo 192.168.33.5    192.168.33.255  192.168.33.255  ibl
>> 0      0        1 lo 192.168.33.211  208.201.224.11  192.168.33.100
>>   0      0      144 eth0 192.168.33.211  208.201.224.33
>> 192.168.33.100
>>       0      5      142 eth0 192.168.33.211  192.168.33.1
>> 192.168.33.1          0      1        0 eth0 192.168.33.211
>> 208.201.224.11  192.168.33.100        0      7      144 eth0
>> 192.168.33.211  208.201.224.33  192.168.33.100        0      0
>> 142 eth0 192.168.33.211  192.168.100.100 192.168.33.100        0
>> 0 1040 eth0
>
> Honestly, this looks like it MAY be a typo somewhere... you've got
> "192.168.33.100" -- I suspect a data-entry error, filling the 3rd
> octet with a "100" (which is a valid 4th-octet value), then saying
> "whups, missed the 4th octet" & filling that in with the (correct) value
> (also 100).  I've seen people do that _exact_ thing (dup'ing octets), &
> have also done it myself.
>
> OTOH, it's also possible, since you're 1 hop away from 192.168.100.0/24,
> that something screwy's going on there... DOES that host
> (192.168.100.100) actually exist on that network?
>
>
> - Steve S.
>
>
>
>
> _______________________________________________
> talk mailing list
> talk at nblug.org
> http://nblug.org/cgi-bin/mailman/listinfo/talk