Poly-poly man wrote:
> Poly-poly man wrote:
>> Poly-poly man wrote:
>>> I've probably asked this before, but what I remember is not working.
>>> I have an internet connection on a windows ME box that is running ICS
>>> to an adapter which has a crossover cable directly to my linux box.
>>> The mini-network is set up properly (I can ping 192.168.0.1(my ME
>>> box) and it can ping 192.168.0.2(my linux box)). How do I set up my
>>> linux box (running openSuSE 10.1 in NetworkManager mode) for the ICS
>>> (set up correctly).
>>>
>>> Desperate and close to succeeding,
>>> poly-p man
>>
>> I've changed a few things, but still nothing. Here's exactly how I'm
>> set up right now:
>>
>> WME has three network "cards"- the pppoe (acts like a dial-up), the
>> wireless (used to get at the pppoe) and the ethernet (x-over to
>> Linux). The e-net is set to 192.168.3.1/255.255.255.0, the pppoe is
>> working fine. ICS is set up between the "dial-up" thingamajig and the
>> ethernet. It has a firewall which allows all ICS traffic.
>>
>> Lin has one network card, set to static (192.168.3.2/255.255.255.0),
>> with 192.168.3.1 as the default gateway. It has DNS set up exactly as
>> ynotssor said (boy, you know more about my connection than I did
).
>> It has no firewall (yet).
>>
>> Let's say I ping google.com (or it's IP). I see on WME that the pppoe
>> connection gets data passed through it. I get no reply on my linux
>> box, though. The same thing happens when I disable the firewall.
>>
>> Please, help!!!
>>
>> poly-p man
>>
>> The reason I'm using 192.168.3.x is to avoid conflicts with my other
>> routers.
>>
> Oh, and one more thing: My Linux Box can ping the nameservers.
>
> poly-p man
Sorry it's in pieces like this, but I have great news:
Tracing route to google.com [64.233.167.99]
over a maximum of 30 hops:
1 55 ms 55 ms * 10.5.28.1
2 * 83 ms 41 ms
so-0-1-2-0.CORE-RTR1.NWRK.verizon-gni.net [130.81.4.9]
3 69 ms 110 ms 41 ms so-7-2-0-0.BB-RTR1.NWRK.verizon-gni.net
[130.81.20.160]
4 41 ms 55 ms 69 ms
so-6-0-0-0.PEER-RTR1.NWK80.verizon-gni.net [130.81.17.157]
5 41 ms 41 ms 42 ms POS5-0.GW1.EWR17.ALTER.NET [152.63.21.117]
6 27 ms 55 ms 55 ms 0.so-1-1-0.XL2.EWR6.ALTER.NET
[152.63.28.89]
7 55 ms 68 ms 28 ms 0.so-6-1-0.XL4.NYC4.ALTER.NET
[152.63.16.198]
8 * 82 ms 69 ms 0.ge-5-1-0.BR2.NYC4.ALTER.NET
[152.63.3.122]
9 69 ms 28 ms 41 ms if-7-2.core1.NTO-NewYork.teleglobe.net
[216.6.82.9]
10 55 ms 96 ms 179 ms
if-4-0-0.core2.NTO-NewYork.teleglobe.net [216.6.82.66]
11 55 ms 110 ms 82 ms 216.6.97.6
12 124 ms 96 ms 96 ms if-8-0.core2.CQW-Chicago.teleglobe.net
[216.6.16.9]
13 55 ms 69 ms 68 ms if-0-3.core1.CT8-Chicago.teleglobe.net
[66.110.27.21]
14 123 ms 110 ms 96 ms ix-8-0.core1.CT8-Chicago.teleglobe.net
[66.110.27.46]
15 96 ms 82 ms * 216.239.46.1
16 * 83 ms 96 ms 66.249.94.133
17 * 151 ms 164 ms 72.14.232.74
18 96 ms 110 ms * 64.233.167.99
19 110 ms 96 ms 83 ms 64.233.167.99
It's the output of a windows tracert command (to google). When I ping
all of the addresses on my Linux box, I get all the way to 72.14.232.74,
but 64.233.167.99 (google) fails.
poly-p man