On 2018-07-13, Kent West wrote:
>
> It was on the network manager's end of things. I don't know the details,
> but he fixed it.
So it was indeed the *network manager* and not the *NetworkManager*. The
disambiguation tombe à pic.
It was on the network manager's end of things. I don't know the details,
but he fixed it.
--
Kent
On Fri, Jul 13, 2018 at 2:05 PM, Kent West wrote:
>
>
> On Fri, Jul 13, 2018 at 1:46 PM, Greg Wooledge
> wrote:
>
>> On Fri, Jul 13, 2018 at 01:33:41PM -0500, Kent West wrote:
>> > I renamed /e
On Fri, Jul 13, 2018 at 1:46 PM, Greg Wooledge wrote:
> On Fri, Jul 13, 2018 at 01:33:41PM -0500, Kent West wrote:
> > I renamed /etc/network/interfaces.
>
> Put it back!!
>
> It contains the configuration for loopback (lo) which is really important.
>
> Your interface was NOT listed in /e/n/i so
On Fri, Jul 13, 2018 at 01:33:41PM -0500, Kent West wrote:
> I renamed /etc/network/interfaces.
Put it back!!
It contains the configuration for loopback (lo) which is really important.
Your interface was NOT listed in /e/n/i so Network Manager grabbed it and
took over.
You can see this by the w
On Fri, Jul 13, 2018 at 12:31 PM, john doe wrote:
> On 7/13/2018 7:04 PM, Kent West wrote:
>
>> On Fri, Jul 13, 2018 at 12:00 PM, john doe wrote:
>>
>> On 7/13/2018 6:50 PM, Kent West wrote:
>>>
>>> On Fri, Jul 13, 2018 at 11:36 AM, Greg Wooledge
wrote:
On Fri, Jul 13, 2018 at 11
On 7/13/2018 7:04 PM, Kent West wrote:
On Fri, Jul 13, 2018 at 12:00 PM, john doe wrote:
On 7/13/2018 6:50 PM, Kent West wrote:
On Fri, Jul 13, 2018 at 11:36 AM, Greg Wooledge
wrote:
On Fri, Jul 13, 2018 at 11:29:42AM -0500, Kent West wrote:
westk@westkent:~$ cat /etc/network/interfaces
On Fri, Jul 13, 2018 at 12:00 PM, john doe wrote:
> On 7/13/2018 6:50 PM, Kent West wrote:
>
>> On Fri, Jul 13, 2018 at 11:36 AM, Greg Wooledge
>> wrote:
>>
>> On Fri, Jul 13, 2018 at 11:29:42AM -0500, Kent West wrote:
>>>
westk@westkent:~$ cat /etc/network/interfaces
> # This file
On 7/13/2018 6:50 PM, Kent West wrote:
On Fri, Jul 13, 2018 at 11:36 AM, Greg Wooledge wrote:
On Fri, Jul 13, 2018 at 11:29:42AM -0500, Kent West wrote:
westk@westkent:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate t
On Fri, Jul 13, 2018 at 11:50:22AM -0500, Kent West wrote:
> westk@westkent:~$ ps as | grep NetworkManager
> 1000 11085
> 00018000 S+ pts/0 0:00 grep NetworkManager
> westk@westkent:~$ ps as | grep systemd-networkd
> 1000 11088 000
On 2018-07-13, Greg Wooledge wrote:
> On Fri, Jul 13, 2018 at 11:29:42AM -0500, Kent West wrote:
>> westk@westkent:~$ cat /etc/network/interfaces
>> > # This file describes the network interfaces available on your system
>> > # and how to activate them. For more information, see interfaces(5).
>>
On Fri, Jul 13, 2018 at 11:36 AM, Greg Wooledge wrote:
> On Fri, Jul 13, 2018 at 11:29:42AM -0500, Kent West wrote:
> > westk@westkent:~$ cat /etc/network/interfaces
> > > # This file describes the network interfaces available on your system
> > > # and how to activate them. For more information,
On Fri, Jul 13, 2018 at 11:29:42AM -0500, Kent West wrote:
> westk@westkent:~$ cat /etc/network/interfaces
> > # This file describes the network interfaces available on your system
> > # and how to activate them. For more information, see interfaces(5).
> > source /etc/network/interfaces.d/*
> > #
In my org, a DNS server was recently retired, but my /etc/resolv.conf is
still being populated with the old DNS entry (which slows my networking
considerably; I can delete that line manually, but that's just a temporary
fix).
My network admin tells me that I have a "dhcp-static" address, and "it
s
13 matches
Mail list logo
