SBC and Linux

Soichiro · Sep 13, 2006

Well, I finally managed to get SBC to work on my (Windows) laptop and parents' computer (through my Linksys router), but my Linux computer cannot receive an internet connection through SBC (even though it worked fine with Comcast through the router set up the same way). The comp is set to DHCP and the router's status page shows that the computer is actually connected to the router, so... does anyone have an idea to get this working? SBC support basically told me to f*ck off because they hate Linux

(it's Gentoo btw, in case that matters)

klingens · Sep 13, 2006

We need a lot more technical info
Since you use a router, is the router actually connected to the internet? What model/name? Does it have a built in DSL modem? Are there any other PCs on the network you can reach?

Can you ping IPs? what is the output or "route" (mainly the default gateway gw)

Gnufsh · Sep 13, 2006

ifconfig outpit?

petteyg359 · Sep 13, 2006

I suggest doing the following:

Code:

rm /etc/resolv.conf
route add default gw 192.168.1.1

and then trying your connection again. Replace 192.168.1.1 with whatever your router's IP address is.

klingens · Sep 13, 2006

What will deleting resolv.conf help except making sure there is no way to resolve any addresses anymore ensuring he doesn't have net access.

Same with setting the gateway: How do you know it's 192.168.1.1 with his (unknown so far) router?

Soichiro · Sep 13, 2006

Netgear WRT54G router, yes the IP for it is 192.168.1.1. Ping basically gives no response, I can't post the full ifconfig output now since I'm at school, but it gives an IP of 192.168.1.107 (all I can remember...). Will post more when I get home in an hour and a half

ookabooka · Sep 14, 2006

ping an external address, like 72.14.203.104 (google) and if that works, its a DNS issue and you have to check your /etc/resolv.conf file. can you ping 192.168.1.1 (your router)? if you cant do that then there is something really funky going on. . .what distro is it? dhcpcd eth0 (or whatever your ehternet addy is) should restart the interface and look up an address, that way you dont have to reboot.

Soichiro · Sep 14, 2006

Code:

suikii ~ # ifconfig
eth0      Link encap: Ethernet   HWaddr 04:48:80:80:80:03
          inet addr:192.168.1.107  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:47144 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42454 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3247928 (3.0 Mb)  TX bytes:18656510 (17.7 Mb)
          Interrupt:16 Base address:0x2000


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:324 errors:0 dropped:0 overruns:0 frame:0
          TX packets:324 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:16200 (15.8 Kb)  TX bytes:16200 (15.8 Kb)

Code:

suikii ~ # ping -c 3 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=2.88 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.716 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.723 ms

--- 192.168.1.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2009ms
rtt min/avg/max/mdev = 0.716/1.440/2.882/1.019 ms

Code:

suikii ~ # ping -c 3 google.com
ping: unknown host google.com

And it's on Gentoo...

JerMe · Sep 15, 2006

ookabooka is suggesting that something might be up with your /etc/resolv.conf file. Could you post the contents of it? (cat /etc/resolv.conf)

Like he said before, ping a google IP (66.102.7.104, 66.102.7.147, 66.102.7.99) and see if you get a response. Obviously you're connected to the router. If you ping an IP directly, the output would give us more information.

It's possible that your router is set to block your linux box from accessing the net. Possible, but unlikely.

Soichiro · Sep 15, 2006

I fixed this last night by deleting the /etc/resolv.conf file (which was still listing nameservers from my old ISP) and running "dhcpcd eth0". Thank you to everyone who helped (except Klingens

for telling me deleting the /etc/resolv.conf would break the connection even more

That was quite confusing....)

Gnufsh · Sep 15, 2006

It would have broken the connection if dhcpcd didn't re-create it.

petteyg359 · Dec 30, 2006

klingens said:
What will deleting resolv.conf help except making sure there is no way to resolve any addresses anymore ensuring he doesn't have net access.

Same with setting the gateway: How do you know it's 192.168.1.1 with his (unknown so far) router?

Because setting the gateway adds the gateway back in to resolv.conf. That what route add default gw whateveriphere does. And you'll notice in my post that I said to replace 192.168.1.1 with whatever the router's IP was.

SBC and Linux

Soichiro

Member

klingens

Member

Gnufsh

Senior Member

petteyg359

Likes Popcorn

klingens

Member

Soichiro

Member

ookabooka

Member

Soichiro

Member

JerMe

Member

Soichiro

Member

Gnufsh

Senior Member

petteyg359

Likes Popcorn

Similar threads