Network interface configuration on Debian 6 (No DHCPOFFERS received)
up vote
2
down vote
favorite
I am trying to configure an interface to allow internet connection on a home server which runs Debian 6 x86.
The server is behind a router which has DHCP enabled. The router IP is 192.168.1.1 with netmask 255.255.255.0.
I have so far tried configuring the connection via /etc/network/interfaces using the official Debian docs.
My current /etc/network/interfaces configuration looks like this:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
Once I saved this configuration, I ran /etc/init.d/networking restart, however, it seems like dhclient is unable to connect. The output given is:
DHCPRELEASE on eth0 to 192.168.1.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done.
The output of route -n is empty. (not sure if that is relevant)
I also tried troubleshooting the connection by ensuring that the cable is connected to the server, as well as that the router isn't malfunctioning (no issues with the other devices connected to it). Any help would be greatly appreciated.
networking debian dhcp
asked Nov 22 '14 at 15:33
arnaudoff
11113
migrated from serverfault.com Nov 22 '14 at 15:38
This question came from our site for system and network administrators.
add a comment |
up vote
2
down vote
favorite
I am trying to configure an interface to allow internet connection on a home server which runs Debian 6 x86.
The server is behind a router which has DHCP enabled. The router IP is 192.168.1.1 with netmask 255.255.255.0.
I have so far tried configuring the connection via /etc/network/interfaces using the official Debian docs.
My current /etc/network/interfaces configuration looks like this:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
Once I saved this configuration, I ran /etc/init.d/networking restart, however, it seems like dhclient is unable to connect. The output given is:
DHCPRELEASE on eth0 to 192.168.1.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done.
The output of route -n is empty. (not sure if that is relevant)
I also tried troubleshooting the connection by ensuring that the cable is connected to the server, as well as that the router isn't malfunctioning (no issues with the other devices connected to it). Any help would be greatly appreciated.
networking debian dhcp
asked Nov 22 '14 at 15:33
arnaudoff
11113
migrated from serverfault.com Nov 22 '14 at 15:38
This question came from our site for system and network administrators.
Assuming a completely bone-stock Debian 6 install with no firewall apps configured or IPTables rule changes, your router is probably busted or your cable is bad.
– Magellan
Nov 22 '14 at 15:44
@Magellan, the install isn't new, but I don't have firewall packages or any iptables rules. Regarding the hardware, I've tested both the cable and the router - they seem to work with other devices. All I remember is changing the router address from 10.0.0.0 to 192.168.0.0, but I don't think this could be the issue as other devices worked fine after that.
– arnaudoff
Nov 22 '14 at 16:19
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I am trying to configure an interface to allow internet connection on a home server which runs Debian 6 x86.
The server is behind a router which has DHCP enabled. The router IP is 192.168.1.1 with netmask 255.255.255.0.
I have so far tried configuring the connection via /etc/network/interfaces using the official Debian docs.
My current /etc/network/interfaces configuration looks like this:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
Once I saved this configuration, I ran /etc/init.d/networking restart, however, it seems like dhclient is unable to connect. The output given is:
DHCPRELEASE on eth0 to 192.168.1.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done.
The output of route -n is empty. (not sure if that is relevant)
I also tried troubleshooting the connection by ensuring that the cable is connected to the server, as well as that the router isn't malfunctioning (no issues with the other devices connected to it). Any help would be greatly appreciated.
networking debian dhcp
asked Nov 22 '14 at 15:33
arnaudoff
11113
I am trying to configure an interface to allow internet connection on a home server which runs Debian 6 x86.
The server is behind a router which has DHCP enabled. The router IP is 192.168.1.1 with netmask 255.255.255.0.
I have so far tried configuring the connection via /etc/network/interfaces using the official Debian docs.
My current /etc/network/interfaces configuration looks like this:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
Once I saved this configuration, I ran /etc/init.d/networking restart, however, it seems like dhclient is unable to connect. The output given is:
DHCPRELEASE on eth0 to 192.168.1.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done.
The output of route -n is empty. (not sure if that is relevant)
I also tried troubleshooting the connection by ensuring that the cable is connected to the server, as well as that the router isn't malfunctioning (no issues with the other devices connected to it). Any help would be greatly appreciated.
networking debian dhcp
networking debian dhcp
asked Nov 22 '14 at 15:33
arnaudoff
11113
asked Nov 22 '14 at 15:33
arnaudoff
11113
asked Nov 22 '14 at 15:33
arnaudoff
11113
asked Nov 22 '14 at 15:33
arnaudoff
11113
asked Nov 22 '14 at 15:33
arnaudoff
11113
11113
migrated from serverfault.com Nov 22 '14 at 15:38
This question came from our site for system and network administrators.
migrated from serverfault.com Nov 22 '14 at 15:38
This question came from our site for system and network administrators.
Assuming a completely bone-stock Debian 6 install with no firewall apps configured or IPTables rule changes, your router is probably busted or your cable is bad.
– Magellan
Nov 22 '14 at 15:44
@Magellan, the install isn't new, but I don't have firewall packages or any iptables rules. Regarding the hardware, I've tested both the cable and the router - they seem to work with other devices. All I remember is changing the router address from 10.0.0.0 to 192.168.0.0, but I don't think this could be the issue as other devices worked fine after that.
– arnaudoff
Nov 22 '14 at 16:19
add a comment |
Assuming a completely bone-stock Debian 6 install with no firewall apps configured or IPTables rule changes, your router is probably busted or your cable is bad.
– Magellan
Nov 22 '14 at 15:44
@Magellan, the install isn't new, but I don't have firewall packages or any iptables rules. Regarding the hardware, I've tested both the cable and the router - they seem to work with other devices. All I remember is changing the router address from 10.0.0.0 to 192.168.0.0, but I don't think this could be the issue as other devices worked fine after that.
– arnaudoff
Nov 22 '14 at 16:19
Assuming a completely bone-stock Debian 6 install with no firewall apps configured or IPTables rule changes, your router is probably busted or your cable is bad.
– Magellan
Nov 22 '14 at 15:44
Assuming a completely bone-stock Debian 6 install with no firewall apps configured or IPTables rule changes, your router is probably busted or your cable is bad.
– Magellan
Nov 22 '14 at 15:44
@Magellan, the install isn't new, but I don't have firewall packages or any iptables rules. Regarding the hardware, I've tested both the cable and the router - they seem to work with other devices. All I remember is changing the router address from 10.0.0.0 to 192.168.0.0, but I don't think this could be the issue as other devices worked fine after that.
– arnaudoff
Nov 22 '14 at 16:19
@Magellan, the install isn't new, but I don't have firewall packages or any iptables rules. Regarding the hardware, I've tested both the cable and the router - they seem to work with other devices. All I remember is changing the router address from 10.0.0.0 to 192.168.0.0, but I don't think this could be the issue as other devices worked fine after that.
– arnaudoff
Nov 22 '14 at 16:19
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Try this.
instead of
auto eth0
try
auto eth0
allow-hotplug eth0
allow-hotplug starts the interface when the kernel detects a hotplug event from the interface while auto starts the interface on the system start.
I'm sure but I think a DHCP release is a hotplug event.
Hope this was helpful.
answered Nov 22 '14 at 17:27
Eamonn Travers
49646
I tried that, no success. I also did a bit more troubleshooting: to make sure the NIC is fine, I tried to connect without dhcp and set my address, gateway, netmask etc. to the ones given to me by my ISP (the address is static) - it worked like a charm. It seems that the issue is exactly with the interface and/or DHCP configuration.
– arnaudoff
Nov 22 '14 at 17:42
Hi. If I was you (& assuming that you haven't already tried it) I would firstly reboot the router & secondly make sure that it's not using fixed leases. Sorry I couldn't be of more help.
– Eamonn Travers
Nov 22 '14 at 17:44
P.S Notable is "send_packet: Network is unreachable" it usually a sign that the NIC is not doing it's thing.
– Eamonn Travers
Nov 22 '14 at 17:46
Well, I already tried rebooting and releasing. Also, I'm not getting the send_packet error anymore - it just appeared at the time I was posting, it is no longer present, though.
– arnaudoff
Nov 22 '14 at 18:20
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Try this.
instead of
auto eth0
try
auto eth0
allow-hotplug eth0
allow-hotplug starts the interface when the kernel detects a hotplug event from the interface while auto starts the interface on the system start.
I'm sure but I think a DHCP release is a hotplug event.
Hope this was helpful.
answered Nov 22 '14 at 17:27
Eamonn Travers
49646
I tried that, no success. I also did a bit more troubleshooting: to make sure the NIC is fine, I tried to connect without dhcp and set my address, gateway, netmask etc. to the ones given to me by my ISP (the address is static) - it worked like a charm. It seems that the issue is exactly with the interface and/or DHCP configuration.
– arnaudoff
Nov 22 '14 at 17:42
Hi. If I was you (& assuming that you haven't already tried it) I would firstly reboot the router & secondly make sure that it's not using fixed leases. Sorry I couldn't be of more help.
– Eamonn Travers
Nov 22 '14 at 17:44
P.S Notable is "send_packet: Network is unreachable" it usually a sign that the NIC is not doing it's thing.
– Eamonn Travers
Nov 22 '14 at 17:46
Well, I already tried rebooting and releasing. Also, I'm not getting the send_packet error anymore - it just appeared at the time I was posting, it is no longer present, though.
– arnaudoff
Nov 22 '14 at 18:20
add a comment |
up vote
0
down vote
Try this.
instead of
auto eth0
try
auto eth0
allow-hotplug eth0
allow-hotplug starts the interface when the kernel detects a hotplug event from the interface while auto starts the interface on the system start.
I'm sure but I think a DHCP release is a hotplug event.
Hope this was helpful.
answered Nov 22 '14 at 17:27
Eamonn Travers
49646
I tried that, no success. I also did a bit more troubleshooting: to make sure the NIC is fine, I tried to connect without dhcp and set my address, gateway, netmask etc. to the ones given to me by my ISP (the address is static) - it worked like a charm. It seems that the issue is exactly with the interface and/or DHCP configuration.
– arnaudoff
Nov 22 '14 at 17:42
Hi. If I was you (& assuming that you haven't already tried it) I would firstly reboot the router & secondly make sure that it's not using fixed leases. Sorry I couldn't be of more help.
– Eamonn Travers
Nov 22 '14 at 17:44
P.S Notable is "send_packet: Network is unreachable" it usually a sign that the NIC is not doing it's thing.
– Eamonn Travers
Nov 22 '14 at 17:46
Well, I already tried rebooting and releasing. Also, I'm not getting the send_packet error anymore - it just appeared at the time I was posting, it is no longer present, though.
– arnaudoff
Nov 22 '14 at 18:20
add a comment |
up vote
0
down vote
up vote
0
down vote
Try this.
instead of
auto eth0
try
auto eth0
allow-hotplug eth0
allow-hotplug starts the interface when the kernel detects a hotplug event from the interface while auto starts the interface on the system start.
I'm sure but I think a DHCP release is a hotplug event.
Hope this was helpful.
answered Nov 22 '14 at 17:27
Eamonn Travers
49646
Try this.
instead of
auto eth0
try
auto eth0
allow-hotplug eth0
allow-hotplug starts the interface when the kernel detects a hotplug event from the interface while auto starts the interface on the system start.
I'm sure but I think a DHCP release is a hotplug event.
Hope this was helpful.
answered Nov 22 '14 at 17:27
Eamonn Travers
49646
edited Nov 22 '14 at 20:57
answered Nov 22 '14 at 17:27
Eamonn Travers
49646
answered Nov 22 '14 at 17:27
Eamonn Travers
49646
answered Nov 22 '14 at 17:27
Eamonn Travers
49646
49646
I tried that, no success. I also did a bit more troubleshooting: to make sure the NIC is fine, I tried to connect without dhcp and set my address, gateway, netmask etc. to the ones given to me by my ISP (the address is static) - it worked like a charm. It seems that the issue is exactly with the interface and/or DHCP configuration.
– arnaudoff
Nov 22 '14 at 17:42
Hi. If I was you (& assuming that you haven't already tried it) I would firstly reboot the router & secondly make sure that it's not using fixed leases. Sorry I couldn't be of more help.
– Eamonn Travers
Nov 22 '14 at 17:44
P.S Notable is "send_packet: Network is unreachable" it usually a sign that the NIC is not doing it's thing.
– Eamonn Travers
Nov 22 '14 at 17:46
Well, I already tried rebooting and releasing. Also, I'm not getting the send_packet error anymore - it just appeared at the time I was posting, it is no longer present, though.
– arnaudoff
Nov 22 '14 at 18:20
add a comment |
I tried that, no success. I also did a bit more troubleshooting: to make sure the NIC is fine, I tried to connect without dhcp and set my address, gateway, netmask etc. to the ones given to me by my ISP (the address is static) - it worked like a charm. It seems that the issue is exactly with the interface and/or DHCP configuration.
– arnaudoff
Nov 22 '14 at 17:42
Hi. If I was you (& assuming that you haven't already tried it) I would firstly reboot the router & secondly make sure that it's not using fixed leases. Sorry I couldn't be of more help.
– Eamonn Travers
Nov 22 '14 at 17:44
P.S Notable is "send_packet: Network is unreachable" it usually a sign that the NIC is not doing it's thing.
– Eamonn Travers
Nov 22 '14 at 17:46
Well, I already tried rebooting and releasing. Also, I'm not getting the send_packet error anymore - it just appeared at the time I was posting, it is no longer present, though.
– arnaudoff
Nov 22 '14 at 18:20
I tried that, no success. I also did a bit more troubleshooting: to make sure the NIC is fine, I tried to connect without dhcp and set my address, gateway, netmask etc. to the ones given to me by my ISP (the address is static) - it worked like a charm. It seems that the issue is exactly with the interface and/or DHCP configuration.
– arnaudoff
Nov 22 '14 at 17:42
I tried that, no success. I also did a bit more troubleshooting: to make sure the NIC is fine, I tried to connect without dhcp and set my address, gateway, netmask etc. to the ones given to me by my ISP (the address is static) - it worked like a charm. It seems that the issue is exactly with the interface and/or DHCP configuration.
– arnaudoff
Nov 22 '14 at 17:42
Hi. If I was you (& assuming that you haven't already tried it) I would firstly reboot the router & secondly make sure that it's not using fixed leases. Sorry I couldn't be of more help.
– Eamonn Travers
Nov 22 '14 at 17:44
Hi. If I was you (& assuming that you haven't already tried it) I would firstly reboot the router & secondly make sure that it's not using fixed leases. Sorry I couldn't be of more help.
– Eamonn Travers
Nov 22 '14 at 17:44
P.S Notable is "send_packet: Network is unreachable" it usually a sign that the NIC is not doing it's thing.
– Eamonn Travers
Nov 22 '14 at 17:46
P.S Notable is "send_packet: Network is unreachable" it usually a sign that the NIC is not doing it's thing.
– Eamonn Travers
Nov 22 '14 at 17:46
Well, I already tried rebooting and releasing. Also, I'm not getting the send_packet error anymore - it just appeared at the time I was posting, it is no longer present, though.
– arnaudoff
Nov 22 '14 at 18:20
Well, I already tried rebooting and releasing. Also, I'm not getting the send_packet error anymore - it just appeared at the time I was posting, it is no longer present, though.
– arnaudoff
Nov 22 '14 at 18:20
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f843652%2fnetwork-interface-configuration-on-debian-6-no-dhcpoffers-received%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Assuming a completely bone-stock Debian 6 install with no firewall apps configured or IPTables rule changes, your router is probably busted or your cable is bad.
– Magellan
Nov 22 '14 at 15:44
@Magellan, the install isn't new, but I don't have firewall packages or any iptables rules. Regarding the hardware, I've tested both the cable and the router - they seem to work with other devices. All I remember is changing the router address from 10.0.0.0 to 192.168.0.0, but I don't think this could be the issue as other devices worked fine after that.
– arnaudoff
Nov 22 '14 at 16:19