If I use a completely vanilla freshly installed VM (on VirtualBox)...
LXDE, but otherwise standard options:
Even a simple "ifdown " with no configuration changes gives
inconsistent results. Three different results so far:
1) Sometimes it SEEMS like it releases the DHCP address, and
On Saturday 25 August 2018 06:02:20 Gene Heskett wrote:
> On Saturday 25 August 2018 04:20:51 to...@tuxteam.de wrote:
> > On Sat, Aug 25, 2018 at 03:54:32AM -0400, Gene Heskett wrote:
> >
> > [...]
> >
> > > I've experienced that on a armbian install on a rock64, it takes
> > > sometimes 2 or 3
On Saturday 25 August 2018 04:20:51 to...@tuxteam.de wrote:
> On Sat, Aug 25, 2018 at 03:54:32AM -0400, Gene Heskett wrote:
>
> [...]
>
> > I've experienced that on a armbian install on a rock64, it takes
> > sometimes 2 or 3 powerdown recycles to make a change in e-n-i.d/name
> > of interface to
On Saturday 25 August 2018 04:20:51 to...@tuxteam.de wrote:
> On Sat, Aug 25, 2018 at 03:54:32AM -0400, Gene Heskett wrote:
>
> [...]
>
> > I've experienced that on a armbian install on a rock64, it takes
> > sometimes 2 or 3 powerdown recycles to make a change in e-n-i.d/name
> > of interface to
On Sat, Aug 25, 2018 at 03:54:32AM -0400, Gene Heskett wrote:
[...]
> I've experienced that on a armbian install on a rock64, it takes
> sometimes 2 or 3 powerdown recycles to make a change in e-n-i.d/name of
> interface to stick [...]
That sounds a bit like Voodoo. But then, there's Clarke's
On Friday 24 August 2018 23:33:49 Mark Pavlichuk wrote:
> ifdown doesn't seem to work. It seems to complete successfully with
> messages about a released DHCP address, but ifconfig shows the
> interface is still up, a ping will be returned etc... Though if I try
> another ifdown it will say the
ifdown doesn't seem to work. It seems to complete successfully with
messages about a released DHCP address, but ifconfig shows the interface
is still up, a ping will be returned etc... Though if I try another
ifdown it will say the interface is not configured.
If I then make configuration
I spoke too soon...
I'm getting inconsistent results each time I try... with things usually
not working. I usually brute-force problems by just exploring every
combination of configuration and commands, but something very weird is
going on here.
Now I'm getting :
Job for
Ahh, the problem was the "allow-hotplug" that my interface acquired...
though it's weird that even stopping dhclient and the network daemon
didn't stop the interface from bouncing back up (with a DHCP address).
Is there some other daemon I'm unaware of? (I was experimenting with a
fresh
I can't seem to change the configuration of a nic from DHCP to static in
Stretch (without rebooting) - I do this a lot so I don't want to have to
reboot every time. I'm using the old "killall dhclient;ifdown eth0;ifup
eth0" method which also still seems to be in the documentation... at
least
10 matches
Mail list logo
