You are not logged in.
Pages: 1
Did a fresh install and wired connection does not work. It gets to obtaining ip address and hangs there.
Tried this but no luck. https://dev1galaxy.org/viewtopic.php?id=682
Did I forget to install something?
Last edited by Spaceman Spiff (2019-05-25 17:40:15)
Offline
What exactly did you install?
Offline
PS. the connection is good.
Offline
defaut desktop
print server and dhcp? It was three things that were chosen by defualt, and I just went with it.
Last edited by Spaceman Spiff (2019-05-24 17:22:54)
Offline
What is the content of /etc/network/interfaces?
Does dhclient return any error messages if you run it from the command line?
Can you assign static addresses with the ip command?
The full output of ip link would also be relevant.
Brianna Ghey — Rest In Power
Offline
I have had wicd do this on past installs when the wireless address in preferences was set to wlan0 instead of the wlxblahblahblah address
which showed up with ip link command. fwiw
my mistake-you said "wired" sorry for noise.
Last edited by catprints (2019-05-24 18:52:24)
"The obstacle is the path."
Offline
I randomly have this problem after installing the net install from ethernet. When installing from ethernet, /etc/network/interfaces will contain:
# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
This control causes a delay during boot and at some point, this code should be removed, and let the network manager (wicd, networkmanger, etc) control network. But at times I have removed this code from /etc/network/interfaces and I didnt have ethernet as well. In my case the problem worked itself out with removal of this code and the network manager managing ethernet.
If no ethernet, what happens if you:
dhclient -r eth0
ifconfig eth0 down
ifconfig eth0 up
dhclient -v eth0
Offline
dhclient did not return any errors. One thing of note that I suddenly realized is that I have two ethernet controllers on my computer. one on the motherboard and a card. during installation it selected eth1, but in previous systems it has always been eth0.
The installation said that eth1 was good and eth0 was not. this might have some bearing on the problem.
I will post the interfaces and iplink shortly if I get a chance.
Offline
Solved it! wicd was pointing towards eth0 instead of eth1. I'm glad it was a simple fix. Thanks for the help guys.
Offline
Pages: 1