Network doesn't work but has ip

Lonsas · 2008-12-23 10:07:28

Okay, I'm really tired of this now and I guess it's actually just a simple small problem (probably something I've screwed up not knowing)

The problem is:
I'm able to get an ip from the router (192.168.1.1) and dhcp gives me 192.168.1.7. If I check in the router it says that the computer is connected and everything seems fine.
But nothing works! ping returns

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. From 192.168.1.7 icmp_seq=2 Destination Host Unreachable

Currently I've set so that nothing is automatic so that I can try to find the error; I load the module, bring up eth0 and dhcp for an ip and all that works.

It works perfectly on the livecd and I've even tried copying some of the config files from the livecd just to make sure that there are no small bugs.

As I said before I've commented out the network stuff from rc.conf.
Allthrough I think it looked something like this before:

eth0="dhcp"
lo="lo 127.0.0.1"
INTERFACES=(lo eth0)
gateway="default gw 192.168.1.1"
ROUTES=(!gateway)

The route table looks something like this:

192.168.1.0    *            255.255.255.0    U    0    0    0    eth0
default        192.168.1.1    0.0.0.0        UG    0    0    0    eth0

I'm pretty new to arch and I would really want some help on this, it's really bugging me.

Last edited by Lonsas (2008-12-23 13:12:02)

zenlord · 2008-12-23 14:19:48

If you didn't install a firewall, you should definitely check out netcfg and set up a simple ethernet-profile to connect.

With the network-daemon, I think you can remove everything related to lo (IIRC it is automatically brought up by the initscripts-package) and you can comment out the gateway and route-sections in your rc.conf.

Zl.
PS: what is the version of dhcpd? If it is v4 and older than 4.0.7, that also might be the problem (which is ought to be fixed in 4.0.7)

Lonsas · 2008-12-23 15:10:27

netcfg doesn't exist...
It's dhcpcd version 4.0.2

So I guess I'll just reinstall, it's just a clean install on a computer that I've not used for a while.

Thanks for the help anyway zenlord

zenlord · 2008-12-23 15:33:19

You don't need to reinstall:
http://bugs.archlinux.org/task/11770?st … &closedto=

I guess you cannot update your system as long as you don't have a network connection.

Netcfg is the command, but IIRC the package is called 'netcfg2' - also read the wiki on 'net-profiles'. According to me, it is really straightforward and it lets you specify to use dhclient instead of dhcpd. This change brought my connection back. When I have the time, I'll revert back to dhcpd.

Zl.

Zariel · 2008-12-23 16:10:51

hm dhcpcd works fine for me on .27 and .28

Lonsas · 2008-12-23 17:04:56

Ok
dhcp isn't the problem; same result with static adress.

I reinstalled arch and the problem still resides. I have had the connection working before in arch and other distros.

The module that is used is tlan (ThunderLAN 10mbps... horay! )
It seems to load fine, but i wonder... should lsmod say that the modules is used by something? because it says that it isn't used by anything 0, nada.

And in what way should netcfg help really?

The real problem is - I get connected to the router but that's it.
I guess it has something to do with routes or something like that but I have really no idea, I don't know much at all.

Last edited by Lonsas (2008-12-23 17:09:52)

Zariel · 2008-12-23 17:18:19

sudo modprobe tlan, does that say anything?

nvm mine says the same on my server, whats the output of ifconfig eth0?

Last edited by Zariel (2008-12-23 17:22:35)

Lonsas · 2008-12-23 17:20:10

Zariel wrote:

sudo modprobe tlan, does that say anything?

No it doesn't... I said that it seemed to load fine.

Zariel · 2008-12-23 17:52:37

can you ping yourself? ie, ping 192.168.1.7

Lonsas · 2008-12-23 18:01:00

Zariel wrote:

can you ping yourself? ie, ping 192.168.1.7

Yes

Lonsas · 2008-12-25 10:26:22

This is getting really annoying now.
It's for sure not dhcp (tested dhclient).
The thing that is really bugging me is that it works perfectly fine on the arch livecd.
The tlan module works perfectly fine and it establish the link for eth0.

Does anyone have a clue about what the problem really is?

Mr Green · 2008-12-25 11:00:54

What you got in resolv.conf hosts etc? it may be nothing but worth checking

Lonsas · 2008-12-25 12:36:15

Mr Green wrote:

What you got in resolv.conf hosts etc? it may be nothing but worth checking

I have currently only the defaults since I tried reinstalling

resolv.conf:

nameserver 192.168.1.1

hosts:

127.0.0.1 localhost.localdomain localhost

New update: Noticed now that there is collisions

collisions:37

That tells me that something ain't allright ey?

Last edited by Lonsas (2008-12-25 12:44:36)

R00KIE · 2008-12-25 14:59:10

My rc.conf only has

eth0="dhcp"
INTERFACES=(eth0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

and everything works well.
Also if you have changed your hostname to something else besides localhost you should add that to the hosts file I believe.

The collisions thing .... either you have another pc using the same ip or you are using a hub and some other pc is monopolizing your network (I'm not an expert on networking though, I might be wrong).

Lonsas · 2008-12-25 17:55:53

A small update.

The collisions happen everytime you try to do something (dhcp and ping). It doesn't collide with any of the other computers so the problem is 100% on the computer or between it and the router.
Edit: only at the computer, router is working fine with the computer since it works when you try with the livecd.

The computer can't seem to reconnect after the router been down too (the router recognises a network connection but it isn't in the list of attached devices).

I should try with an older kernel later since it works on the livecd and has been working before.

I'm not entirely sure the tlan module gives what it should, anyone one knows if this output seems ok?

TLAN: eth0: Starting autonegotiation.
TLAN: Giving autonegotiation more time.
TLAN: Please check that your adapter has
TLAN: been properly connected to a HUB or Switch.
TLAN: Trying to establish link in background...
TLAN: eth0: Autonegotiation complete.
TLAN Starting internal PHY with HALF-DUPLEX
TLAN: eth0: Link active

The tlan module is pretty weird but what I remeber - the output looked like that when I had it working too.

Last edited by Lonsas (2008-12-25 17:57:31)

Arch Linux

#1 2008-12-23 10:07:28

Network doesn't work but has ip

#2 2008-12-23 14:19:48

Re: Network doesn't work but has ip

#3 2008-12-23 15:10:27

Re: Network doesn't work but has ip

#4 2008-12-23 15:33:19

Re: Network doesn't work but has ip

#5 2008-12-23 16:10:51

Re: Network doesn't work but has ip

#6 2008-12-23 17:04:56

Re: Network doesn't work but has ip

#7 2008-12-23 17:18:19

Re: Network doesn't work but has ip

#8 2008-12-23 17:20:10

Re: Network doesn't work but has ip

#9 2008-12-23 17:52:37

Re: Network doesn't work but has ip

#10 2008-12-23 18:01:00

Re: Network doesn't work but has ip

#11 2008-12-25 10:26:22

Re: Network doesn't work but has ip

#12 2008-12-25 11:00:54

Re: Network doesn't work but has ip

#13 2008-12-25 12:36:15

Re: Network doesn't work but has ip

#14 2008-12-25 14:59:10

Re: Network doesn't work but has ip

#15 2008-12-25 17:55:53

Re: Network doesn't work but has ip

Board footer