2
I have two ethernet interfaces, p10p1
(motherboard) and eth1
(card), and the only interface that is loading on boot is loopback; neither of the Ethernet interfaces are loading. This has started occurring after [unsuccessfully] trying to create a pppoe
connection and then completely removing pppoeconf
in an attempt to remove any trace of its effect on the system.
The /etc/network/interfaces
file is as follows:
auto lo
iface lo inet loopback
auto p10p1
iface p10p1 inet dhcp
auto eth1
iface eth1 inet static
address 192.168.5.1
netmask 255.255.255.0
broadcast 192.168.5.255
gateway 192.168.0.1
When booting, I get the message “Waiting for network configuration” then ”Waiting an additional 60 seconds for network configuration.”
I can bring up the interfaces manually using sudo ifconfig p10p1 up
(same for eth1
), but that doesn’t seem to accomplish anything.
The current configuration is that this server sits behind a router that provides DHCP to the whole network (there are no devices behind the server at this point). p10p1
interface is the “external/primary” interface and eth1
is the “internal” interface.
The end goal is to get a pppoe
connection going to I can turn the unfortunate router my ISP gave me for our fiber internet into bridge mode and make the server the primary gateway/firewall/router again; that’s how it was when we had cable Internet.
For now, though, I just need to get this box communicating with the interwebs again so I can install rp-pppoe
and try that.
I’m wondering if my uninstall of pppoeconf
wiped something out, or if in the process of configuring pppoeconf, something was done that might render /etc/network/interfaces
inoperable. Is that possible?
Any thoughts on why my interfaces are not coming up on boot?
Well, both interfaces are configured as DHCP clients. Do you have a DHCP server that would listen to DHCP requests? – nKn – 2015-09-07T18:55:45.943
Yes, eth1 should be static as the isc-dhcp-server is running on that interface, but at the moment I'm less concerned about it as I am about p10p1. The current router is providing DHCP without any issue for the rest of the network. It was working prior to my attempt at the pppoe connection (not with this interfaces configuration, but of course I didn't save the old one before messing with it). – Patrick – 2015-09-07T19:06:05.640
Mind if I ask what is the make/model of the PoS router/modem you have on your network? – JakeGould – 2015-09-07T23:15:31.457
Sorry. It is not a PoS router. It is a piece of crap. Well, that's what I've been told anyways. I have edited the post to clarify that. It is a ZyXEL FR1000Z. – Patrick – 2015-09-07T23:33:41.073
'ifconfig interface up' only enables the interface, it doesn't configure it. Try 'ifup p10p1' and 'ifup eth1' (and maybe check that gateway for eth1) – Brandon Xavier – 2015-09-08T00:49:56.917
thanks for the tip on
ifup
. The gateway for eth1 is set to the ZyXEL router, otherwise traffic on the server never leaves the server in this situation or something. When it is set to192.168.5.1
, and you ping Google or something, the host is unreachable. Perhaps there is another workaround, but this is working for the time being. When the server becomes the primary gateway for the network, it will switch to192.168.5.1
– Patrick – 2015-09-08T02:00:52.263