Re: How to configure e-net port again -- SOLVED (sort of)
On 1/31/2020 9:57 PM, Dennis Wicks wrote:
> Michael Stone wrote on 1/31/20 2:00 PM:
>> On Fri, Jan 31, 2020 at 11:27:06AM -0600, Dennis Wicks wrote:
>>> john doe wrote on 1/31/20 1:00 AM:
>>>> On 1/31/2020 2:48 AM, Dennis Wicks wrote:
>>>>> I am running Debian Buster 10, upgrade within the past week.
>>>>>
>>>>> I tried to change my e-net to use dhcp, which I thought it was but it
>>>>
>>>> How did you try to change your e-net to use dhcp?
>>>>
>>>>> wasn't picking up all the info from the DHCP server, specifically
>>>>> the IP
>>>>> addr. Now it doesn't work at all. How can I run through the setup/init
>>>>> process that it went through at install to get back at least a working
>>>>> communications port.
>>>>>
>>>>
>>>> I would say, revert the change(s)that you have done.
>>>>
>>>> --
>>>> John Doe
>>>>
>>>>
>>>>
>>> I have tried that to no avail. There are two possibilities:
>>>
>>> (1) I don't remember exactly what was there before
>>> (2) One of the two network management programs that are running
>>> changed something that I don't know about.
>>>
>>> In my Notification Area there are two programs that seem to be
>>> controlling the interfaces, and perhaps causing my problems. They are
>>> Network Manager Applet and WICD Network Manager.
>>
>> 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.
>
> 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.
>
> Thanks for all the help and suggestions!
> Dennis
>
One thing, let the network manager to enable/disable the interface if
you want the CLI use CLI for the network manager that you use.
That would be 'nmcli' for NetworkManager.
--
John Doe
Reply to: