[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How to configure e-net port again -- SOLVED (sort of)

On Fri, Jan 31, 2020 at 02:57:13PM -0600, Dennis Wicks wrote:

Michael Stone wrote on 1/31/20 2:00 PM:
Do you remember which one you used? Both can be used, but if you try to use both at the same time you'll have problems. I'd suggest uninstalling one of them, or at the very least make sure that they aren't both trying to control the same interface. Neither will modify /etc/network/interfaces, so just ignore that.
Michael, thanks for that tip. I got rid of both network managers and setup the port in /etc/network/interfaces and that works -- sometimes.
In future if you do want to use /etc/network/interfaces then be aware that NetworkManager will ignore anything that's configured there. If you never want to use it, though, it doesn't matter if you remove it.
If I try to use IP address reservation in my dhcp server ifup will not work. I get this: 
- - - - -

root@ichiban:~# ifup enp3s0
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/enp3s0/10:7b:44:50:39:8b
Sending on   LPF/enp3s0/10:7b:44:50:39:8b
Sending on   Socket/fallback
DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 7
DHCPOFFER of 192.168.1.2 from 192.168.254.254
DHCPREQUEST for 192.168.1.2 on enp3s0 to 255.255.255.255 port 67
DHCPNAK from 192.168.254.254
DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 6
DHCPOFFER of 192.168.1.2 from 192.168.254.254
DHCPREQUEST for 192.168.1.2 on enp3s0 to 255.255.255.255 port 67
DHCPNAK from 192.168.254.254

- - - - - <repeat ad infinitum>
If I remove IP address reservation ifup works and I get the following:
- - - - -

root@ichiban:~# ifup enp3s0
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/enp3s0/10:7b:44:50:39:8b
Sending on   LPF/enp3s0/10:7b:44:50:39:8b
Sending on   Socket/fallback
DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 7
DHCPOFFER of 192.168.34.220 from 192.168.254.254
DHCPREQUEST for 192.168.34.220 on enp3s0 to 255.255.255.255 port 67
DHCPACK of 192.168.34.220 from 192.168.254.254
bound to 192.168.34.220 -- renewal in 6833 seconds.
root@ichiban:~#

- - - - -
This machine is running Buster 10 64 bit, I have a machine that is running Buster 10 32 bit that works fine with Network Manager Applet 1.8.22. This machine (64 bit) had 1.8.20 and it did not work. Just looped continuously until I deleted the address reservation from the dhcp server. When I run ifup it does the same thing so the problem must be buried deeper somewhere.
Check the logs on the dhcp server. DHCPNAK means that the server is telling the client that the client can't have that IP, that's why it's looping. (Because it first offers that IP.) Some possibilities are that you have multiple dhcp clients running, the dhcp server thinks the IP isn't in the proper subnet (I notice that you're using 192.16.254, 192.168.1, and 192.168.34--is your netmask consistently 255.255.0.0 or /16 everywhere?), you're trying to assign the same IPs both statically and dynamically, you've got multiple hosts using the same IP for some other reason, or you've got multiple DHCP servers fighting with each other.
Reply to: