[Dallas]

I have Win2000 connected to Verizon through a Netgear router and DSL-Modem which came from Verizon.

I cannot seem to get the Linux computer to connect through tkpppoe (came from rp-pppoe). ifconfig shows that the eth0 is up IP 192.168.0.4 DHCP is enabled so it shouldn't use the IP numbers. I get a timed out from tkppoe when I try and start the connection.

I ping yahoo.com and get "Unknown host"

I can ping the Router and the win2k box. .8ms and .3ms respectively, interestingly, the router takes more time than going through it to w2k.

I ping yahoo.com with the w2k and it's fine.
4 packets sent none lost etc...

/etc/resolv.conf

nameserver 151.203.214.84
nameserver 151.203.214.85

it's the same IP as the ipconfig on the connected w2000 box. My router install CD says that I need to connect with DHCP and allow the Verizon server to fill in everything except the user name and password.

I think the the resolve.conf came in automatically from Verizon at some point but I still can't connect.

My router defaults to 192.168.0.1
The w2k ethnet card is set to 192.168.0.2 with DHCP Enabled.

from ipconfig on the w2k box:
Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139(A) PCI Fast Ethern
Adapter
Physical Address. . . . . . . . . : 00-20-ED-44-F2-9C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Wednesday, 30 April, 2003 16:48:46
Lease Expires . . . . . . . . . . : Monday, 18 January, 2038 22:14:07

I switched ethernet cables just to make sure. Both are ok with w2k

What else am I forgetting to tell you?
Thanks,

[lynch]

I'm going to wrestle with a dsl/cable router tonight after having to pester Comcast support last night trying to get my new cable modem activated We both decided to give up after 2 hours with me re-checking all the physical stuff on my end and tech guy promising to keep hacking at it on his end.When I tried the connection this morning it was working,so it must have been somthing on thier end.
From that experience,the thing that jumps out at me from the ipconfig output is your default gateway(router) is using a local IP.
That just doesnt seem right to me.I could be wrong.
I dont know Verizon's policy on connection sharing(it'sdont ask,dont tell @Comcast)but if it's cool with them I'd call thier support guy.
HTH
lynch

[Squashman]

I would like to know if your Netgear router is setup correctly. Is it getting an IP address from the DSL Modem. Did you set up your Netgear router for PPOE.

[codejockey]

One thing to check is your default route. As root, issue the command "route" (without the quotes) at the command line and review the defautl entry. If you have no defautl entry, that's likely a problem, and you will need to add one. The default entry should point to the local IP of the modem. For example, on my system (slackware) the route command gives the output:

ROOT: 2 /root-> route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
172.16.0.0 * 255.255.0.0 U 0 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
default portal 0.0.0.0 UG 1 0 0 eth0

where "portal" is my 2-wire Home Portal modem connected to my router (a NetGear RT-314). The script that adds this default route during bootup is /etc/rc.d/rc.inet1 (on my system); your script should replace the default value with the local IP address of your modem (which should be an address on your local network, i.e., 192.168.0.X).

Hope this helps.