Got a dlink604 router today to share a DSL connection. I dual boot this machine; windows/slackware. I haven't booted to windows personally in like 4 mos now, but I did to set the net up for my wife real quick before getting started with setting up linux. I was able to access the web interface from windows by typing http://192.168.0.1. I set it up for dhcp and quickly accessed the net. Then, I booted to linux to get it working.

I tried to ping 192.168.0.1 just to check, and I get "network unreachable". I typed the address in firebird and I get "connection was refused". Went through netconfig, set it up for dhcp and rebooted the machine and restarted the router. Nothing.

Why am I unable to ping the router? I think I could work out setting up dhcp, but it acts as if the router doesnt even exist.

As root run 'ifconfig' and post the results.

Here is just after boot while hooked up to the router: (I get a timed out waiting for dhcp during boot)

bash-2.05b# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Here is what I get after I connect directly to my modem (if this helps):

bash-2.05b# ifconfig
eth1 Link encap:Ethernet HWaddr 00:04:5A:7F2:61
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:569 errors:0 dropped:0 overruns:0 frame:0
TX packets:657 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:230520 (225.1 Kb) TX bytes:95894 (93.6 Kb)
Interrupt:12 Base address:0x9000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

ppp0 Link encap:Point-to-Point Protocol
inet addr:151.198.160.239 P-t-P:10.5.63.1 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:558 errors:0 dropped:0 overruns:0 frame:0
TX packets:645 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:217515 (212.4 Kb) TX bytes:81280 (79.3 Kb)

Well an immediate fix would be to statically assign an IP address to your machine. This is probably the best approach on a local network as it address won't change which is of benefit when other machines on your network need to talk to it. You will have to put in a DNS server when you run 'netconfig'. You can get the DNS server info from the router.

I believe most of your network setting are set in /etc/rc.d/rc.inet1 so you may wish to take a look in there if you are set on the DHCP thing. Also 'dmesg' may give you some good info.

Ok. I'll give that a try. I tried it once, but skipped the DNS info because I wasn't sure where to find it.

Did it. Still get the same error messages. I did netconfig, static, assigned my comp 192.168.0.3 and set up the gateway for 192.168.0.1 (router) and the same thing happens.

I got the mac address from dmesg for the router config, but not much else helpful there.

So having a static IP of 192.168.0.3 you still could not ping the router?

I am not sure that this is the issue but try changing the network mask to 255.255.255.0 with your static IP. Does the 'ifconfig' info show eth0 properly when you have a static IP? Really just a shot in the dark here.

I have never messed with PPP before so I am wondering if this is somewhat an issue.

Also if you configure with DHCP what does 'dmesg' say? It should give you some error information if it can't get an IP.

Be sure you are using a straight through cat 5 cable to your router, such as the one to your PC. Likely, the cable between your router and the modem is a cross-over cable. On MultiTech routers, you can just use the router IP for the DNS, and it will proxy for you.

It is a straight through cat5. Also remember, it works fine from Windows.

I am going to reinstall both os's when I get home tonight, much as I hate to. I think I have been hacked. I've been getting all kinds of bogus emails from M$ lately. I haven't used any m$ products in like 4 mos, and NEVER subscibed to anything from them. They contain attachments for security patches and what not. Of course, I never opened them but... I am also getting a bunch of "mail undeliverable" in my inbox that were sent to addresses that likely don't even exist as if someone is able to use my mail client to send emails. The wife says windows is acting stupid also. Both were just reinstalled on a new hard drive like a week ago. It had to have been a hack through linux since thats all I use and its connected around 22/7. I was working on hardening Slack, but I suppose it wasn't fast enough. The router/firewall should help that.

I also think my networking probs might be caused by something I had to do to set up PPPoE, so I'll be starting from scratch. I'll post back if it still doesnt work.

Thanks

Still no dice. I have no idea what could be causing this. I reinstalled Slack. First thing, I did netconfig. Entered hostname and domain name; chose dhcp; nothing. Then, I tried static. Entered 192.168.0.3 for local (i set the router to specifically accept this whilst in windows), 192.168.0.1 for the gateway and nothing. Can't ping, can't access web config. At least I have a clean install to work with now. That should narrow down the possibilities.

Can you even ping localhost (127.0.0.1) and/or the IP of the NIC itself?

This is starting to sound like a hardware problem. I know I have been burned a few times by this.

Try switching to another port on the router just to eliminate this as the problem.

Also see if you can ping it from your machine from another machine on the network.

Ok. I can ping localhost. Matter o fact, I am on the net from linux now. Via PPPoE hooked directly into the modem. I tried a different port on the router, no dice. This is the only machine on the network at this time, but I have no trouble accessing the router (ping or otherwise) from windows. The other machine will take some work to get cabled, and I didn't see a point in going through the hassle until they will be able to use the net. As long as I can't use the router with linux, the router ain't getting used

Are you sure you are not having a conflict with another IP address on the network?

Dont see how. When I set it to static, I used 192.168.0.3. I know the router uses .1, because I use its IP to access it from a browser. This is the only machine connected to it. I have been wondering if this is a d-link/linux problem, but I bought this router based on it only needing HTTP to configure, and no drivers whatsoever, so I don't see how that could be it. Though I also wonder why the hell it works in windows and not linux... Not like TCP/IP is some exotic protocol....