similar to: Centos 7 and MAC address munging

Odd situation: I've mentioned before that I have several users for whom I have to spoof the MAC address, due to a software license. Now, I've got net.ifnames=0 biosdevname=0 on the grub2 command line, and I've got the spoofed MAC address in /etc/sysconfig/network-sctipts/ifcfg-eth0. But he had a serious problem - X froze, and he thought to reboot, rather than call me. It came up with

Got a problem: a user's workstation froze. He wound up rebooting, without calling me in first, so I dunno. But, and this is a show-stopper, when it came up, it came up with the firmware MAC, not the spoofed one. In /etc/sysconfig/network-scripts/ifcg-eth0, I've got the spoofed MAC address, and a UUID. In the grub.conf, I've got net.ifnames=0 biosdevname=0. But when I logged onto his

On 30 June 2017 at 18:58, <m.roth at 5-cent.us> wrote: > Got a problem: a user's workstation froze. He wound up rebooting, without > calling me in first, so I dunno. But, and this is a show-stopper, when it > came up, it came up with the firmware MAC, not the spoofed one. In > /etc/sysconfig/network-scripts/ifcg-eth0, I've got the spoofed MAC > address, and a UUID. In

On Mon, 18 May 2015, James Hogarth wrote: > On 18 May 2015 at 20:10, <m.roth at 5-cent.us> wrote: >> Someone else got the 7 pxe install going, and one thing that's annoying is >> that NetworkMangler appears to be regularly trying to fire up the wifi. >> >> On a workstation, in a wired environment. I just want to tell NM to knock >> it off....It's

On 5/19/2015 10:24 AM, James Hogarth wrote: > On 19 May 2015 11:40, <me at tdiehl.org> wrote: >> >> >> Or if you want a bigger hammer: >> >> systemctl disable NetworkManager.service >> systemctl enable network.service >> systemctl stop NetworkManager.service >> systemctl start network.service >> >> The above will disable

On 16 February 2017 at 12:02, James Hogarth <james.hogarth at gmail.com> wrote: > On 16 February 2017 at 11:46, James Hogarth <james.hogarth at gmail.com> wrote: >> On 16 February 2017 at 11:35, Alice Wonder <alice at domblogger.net> wrote: >>> On 02/16/2017 03:28 AM, James Hogarth wrote: >>>> >>>> On 16 February 2017 at 10:42, Alice

James Hogarth wrote: > On 10 December 2015 at 15:00, <m.roth at 5-cent.us> wrote: > >> We've started having a problem with a CentOS 7 server. It looses its >> IPv6 address, if I understand this issue correctly. We can get in, >> if we do ssh -4, though. >> >> In the logs, I'm seeing this about twice an hour: >> <warn> (pid 98466)

On 13 February 2017 at 15:35, <m.roth at 5-cent.us> wrote: > My manager tells me a system in the datacenter is down. I go down there, > and plug in a monitor-on-a-stick and keyboard. It's up, but no network. I > try systemctl restart NetworkManager several times, and ip a shows *no* > change. > > Finally, I do an ifdown, followed by an ifup, and everything's

On 02/16/2017 04:20 AM, James Hogarth wrote: > On 16 February 2017 at 12:02, James Hogarth <james.hogarth at gmail.com> wrote: >> On 16 February 2017 at 11:46, James Hogarth <james.hogarth at gmail.com> wrote: >>> On 16 February 2017 at 11:35, Alice Wonder <alice at domblogger.net> wrote: >>>> On 02/16/2017 03:28 AM, James Hogarth wrote:

Someone else got the 7 pxe install going, and one thing that's annoying is that NetworkMangler appears to be regularly trying to fire up the wifi. On a workstation, in a wired environment. I just want to tell NM to knock it off....It's Monday, and my searching isn't going too well. Clues for the poor? mark

On 16 February 2017 at 11:35, Alice Wonder <alice at domblogger.net> wrote: > On 02/16/2017 03:28 AM, James Hogarth wrote: >> >> On 16 February 2017 at 10:42, Alice Wonder <alice at domblogger.net> wrote: >>> >>> On 02/16/2017 02:32 AM, James Hogarth wrote: >>>> >>>> >>>> On 16 February 2017 at 10:17, Alice Wonder

On 16 February 2017 at 11:46, James Hogarth <james.hogarth at gmail.com> wrote: > On 16 February 2017 at 11:35, Alice Wonder <alice at domblogger.net> wrote: >> On 02/16/2017 03:28 AM, James Hogarth wrote: >>> >>> On 16 February 2017 at 10:42, Alice Wonder <alice at domblogger.net> wrote: >>>> >>>> On 02/16/2017 02:32 AM, James

On 16 February 2017 at 10:42, Alice Wonder <alice at domblogger.net> wrote: > On 02/16/2017 02:32 AM, James Hogarth wrote: >> >> On 16 February 2017 at 10:17, Alice Wonder <alice at domblogger.net> wrote: >>> >>> On 02/16/2017 02:03 AM, James Hogarth wrote: >>>> >>>> >>>> On 16 February 2017 at 09:09, Alice Wonder

----- Oorspronkelijk bericht ----- Van: "James Hogarth" <james.hogarth at gmail.com> Aan: "CentOS mailing list" <centos at centos.org> Verzonden: Donderdag 11 juni 2015 19:59:39 Onderwerp: Re: [CentOS] NetworkManager / wireless on latest Centos7 installs On 11 Jun 2015 13:28, <johan.vermeulen7 at telenet.be> wrote: > > > > ----- Oorspronkelijk

On 02/16/2017 03:28 AM, James Hogarth wrote: > On 16 February 2017 at 10:42, Alice Wonder <alice at domblogger.net> wrote: >> On 02/16/2017 02:32 AM, James Hogarth wrote: >>> >>> On 16 February 2017 at 10:17, Alice Wonder <alice at domblogger.net> wrote: >>>> >>>> On 02/16/2017 02:03 AM, James Hogarth wrote: >>>>>

On Thursday, 7 April 2016, James Hogarth <james.hogarth at gmail.com> wrote: > On 6 April 2016 at 19:21, Subscriber <ml-lists at agoris.net.ua > <javascript:;>> wrote: > > > Hello James, > > > > Wednesday, April 6, 2016, 5:34:26 PM, you wrote: > > > > > Note that this is pretty much the last use case you cannot use > > >

On 02/16/2017 02:32 AM, James Hogarth wrote: > On 16 February 2017 at 10:17, Alice Wonder <alice at domblogger.net> wrote: >> On 02/16/2017 02:03 AM, James Hogarth wrote: >>> >>> On 16 February 2017 at 09:09, Alice Wonder <alice at domblogger.net> wrote: >>>> >>>> On 02/16/2017 12:54 AM, Tony Mountifield wrote: >>>>>

On 11/6/2015 3:58 PM, James Hogarth wrote: > I have a couple of relevant articles you may be interested in ... > > On assigning the zone via NM: > https://www.hogarthuk.com/?q=node/8 > > Look down to the "Specifying a particular firewall zone" bit ... > remember that if you edit the files rather than using nmcli you must > reload NM (or do nmcli reload) for that

On 02/01/2016 07:00 AM, Leroy Tennison wrote: > The issue here may be systemd ... > Web documentation at freedesktop.org says net.ifnames needs to be set to zero, I found just the opposite but if it doesn't work for you try both before giving up. Just to clarify: net.ifnames=0 disables the systemd/udev interface renaming feature. biosdevname=0 disables the biosdevname interface

On 18 May 2015 at 20:10, <m.roth at 5-cent.us> wrote: > Someone else got the 7 pxe install going, and one thing that's annoying is > that NetworkMangler appears to be regularly trying to fire up the wifi. > > On a workstation, in a wired environment. I just want to tell NM to knock > it off....It's Monday, and my searching isn't going too well. Clues for > the