search for: ens3f0

...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) unhandled DHCP event for interface ens3f0 >> >> Now, in googling, I get very few hits putting quotes around "unhanded >> dhcp >> exception" - in fact, the only one I found that seemed to talk about it >> was from someone's slackware box, where there was some sort of >> configuration, perhap...

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) unhandled DHCP event for interface ens3f0 Now, in googling, I get very few hits putting quotes around "unhanded dhcp exception" - in fact, the only one I found that seemed to talk about it was from someone's slackware box, where there was some sort of configuration, perhaps similar to ifcfg-<if>, and they were telling...

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

...at least five or six manufacturers, of varying > ages, from the 10+ yr old Altix 3000 from SGI, to the current one from > SGI, to my 5 yr old Dell workstation, to some old Penguins and several > Suns (soon to set, the sooner the better...). How do you deal with > everything from em1 to ens3f0, which comes up *only* after you start to > install.... In what conceivable way is this better than having your > scripts know that eth0 (or even em1) is always going to be how to talk to > the world? > <snip> > > mark "they sound like ham call letters" &g...

...protocols: db files services: db files ethers: db files rpc: db files netgroup: nis My /etc/resolv.conf: search nsa.int domain nsa.int nameserver 192.168.42.253 My /etc/network/interfaces: auto lo iface lo inet loopback # 10 Gigabit Port 1 allow-hotplug ens3f0 auto ens3f0 iface ens3f0 inet manual address 192.168.84.71 netmask 255.255.255.0 mtu 9014 # 10 Gigabit Port 2 allow-hotplug ens3f1 auto ens3f1 iface ens3f1 inet manual address 192.168.84.72 netmask 255.255.255.0 mtu 9014 # 10 Gigabit Port 3 allo...

...nd the new > naming... it's*so* much easier to deal with... yeah, right, I'll run the > install, and wait till it hangs, so I can see that the NIC is named, what > was it, on that HP last month, oh, yeah, I need to use ip -f inet link, > far simpler than ifconfig, yes, it's ens3f0.... > > mark "why would I*possibly* prefer a same-on-every-box eth0?"* > > * For the satire-impaired, this is satire. LOL !!! After a bit more experimenting, looks like I've found a clean solution for this. Simply create the /etc/udev/rules.d/70-persistent-net...

...m...<thinking> at least five or six manufacturers, of varying ages, from the 10+ yr old Altix 3000 from SGI, to the current one from SGI, to my 5 yr old Dell workstation, to some old Penguins and several Suns (soon to set, the sooner the better...). How do you deal with everything from em1 to ens3f0, which comes up *only* after you start to install.... In what conceivable way is this better than having your scripts know that eth0 (or even em1) is always going to be how to talk to the world? <snip> mark "they sound like ham call letters"

...at least five or six manufacturers, of varying > ages, from the 10+ yr old Altix 3000 from SGI, to the current one from > SGI, to my 5 yr old Dell workstation, to some old Penguins and several > Suns (soon to set, the sooner the better...). How do you deal with > everything from em1 to ens3f0, which comes up *only* after you start to > install.... In what conceivable way is this better than having your > scripts know that eth0 (or even em1) is always going to be how to talk to > the world? > <snip> > > mark "they sound like ham call letters" &gt...

...9;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) unhandled DHCP event for interface ens3f0 > > Now, in googling, I get very few hits putting quotes around "unhanded dhcp > exception" - in fact, the only one I found that seemed to talk about it > was from someone's slackware box, where there was some sort of > configuration, perhaps similar to ifcfg-<if>...

...9;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) unhandled DHCP event for interface ens3f0 > > Now, in googling, I get very few hits putting quotes around "unhanded dhcp > exception" - in fact, the only one I found that seemed to talk about it > was from someone's slackware box, where there was some sort of > configuration, perhaps similar to ifcfg-<if>...

...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) unhandled DHCP event for interface ens3f0 >> >> Now, in googling, I get very few hits putting quotes around "unhanded >> dhcp exception" - in fact, the only one I found that seemed to talk >> about it was from someone's slackware box, where there was some sort of >> configuration, perhaps similar...