You are not logged in.

#1 2013-01-01 00:42:21

chai
Member
Registered: 2011-05-31
Posts: 3

Can't connect to network

I'm having trouble connecting to network from the live installation media. (using usb)
I'll run through the steps I take:

boot to usb, hit tab on the 64bit arch option. I disable ipv6 at boot like this

 ipv6.disable=1

right away I check ifconfig eth0, and it seems like dhcpcd worked automatically. here's the output (top 3 lines):

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1492
inet 192.168.2.3 netmask 255.255.255.0 broadcast 192.168.2.255
ether f0:de:f1:72:12:bc txqueuelen 1000 (Ethernet)
...

seconds later, I check again and the output is:

eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1492
ether f0:de:f1:72:12:bc txqueuelen 1000 (Ethernet)
...

it lost the IP address! this will continue, seemingly at random. same thing with "ip a" sometimes the eth0 device isn't even listed, only lo.
I can't even ping the router (at 192.168.2.1)

connect: network is unreachable

What could I be doing wrong?? (I checked the cables, there isn't a monkey back there unplugging things)

edit: added the error received after pinging

Last edited by chai (2013-01-01 00:56:21)

Offline

#2 2013-01-02 00:06:44

chai
Member
Registered: 2011-05-31
Posts: 3

Re: Can't connect to network

Somehow it works now, with manual ip address configuration. dhcpcd was messing up and constantly retrying (thus bringing my interface up and down?). I killed it with

#dhcpcd -k

I used ip to add an ip address manually.

#ip addr add 192.168.2.3/24 dev eth0

because that's what my router was giving me. also had to manually add the route (had to do this multiple times until no error was received)

#ip route add default via 192.168.2.1

then I could ping other devices on my network, however I could never ping the router. I set up /etc/resolv.conf with google's dns servers then I could even ping out to the internet and continue installation.

Offline

Board footer

Powered by FluxBB