Brian,Looks like the answer is "yes" it will work ok with the new names. Thank you.
Mathew,I followed a number of on-line helps. The problem I ran into was that if the core is updated, as soon as you re-boot it goes back to the newer naming convention and no interfaces are working anymore.
Thanks to both, Nigel. On 10/7/2015 6:11 PM, Brian Burch wrote:
On 08/10/15 00:44, Mathew Crane wrote:Hi Nigel, The new udev device naming schema is a bit daunting at first. I recommend at least looking over Red Hat's own documentation in regards to this: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/ch-Consistent_Network_Device_Naming.html If you want to revert to the old-style naming: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Disabling_Consistent_Network_Device_Naming.html Most modern distros are headed down the systemd-udevd path. I recommend using the CentOS 7 defaults and renaming via /etc/udev/rules.d/70-persistent-net.rules instead of disabling the feature altogether. Here's an example for yours. Replace ATTR{address}== with the MAC addresses of your interfaces. Easiest way to get these to take effect is to reboot. /etc/udev/rules.d/70-persistent-net.rules: SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{dev_id}=="0x0", ATTR{address}=="00:0e:b7:34:10:38", ATTR{type}=="1", KERNEL=="enp*", NAME="eth0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{dev_id}=="0x0", ATTR{address}=="00:0e:b7:34:10:39", ATTR{type}=="1", KERNEL=="enp*", NAME="eth1" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{dev_id}=="0x0", ATTR{address}=="00:0e:b7:34:10:3a", ATTR{type}=="1", KERNEL=="enp*", NAME="eth2" You can get creative with the naming. For mine, I use 'wan0', 'lan0', 'wifi0', etc. Hope this helps! mateo On Wed, Oct 7, 2015 at 7:03 PM, Nigel Aves <ni...@twin-peaks-video.com <mailto:ni...@twin-peaks-video.com>> wrote: Quick question on interface names. I'm building a Centos 7 server and the interface names are no longer eth* but (on this machine) are:- enp2s0 - Outside world enp8s0 - Internal network enp7s0 - Internal network I've tried checking the documentation but can not find a definitive answer. Will Shorewall - Interfaces be OK with these new names, or should I try and revert back to the eth* naming schema.One of my ubuntu servers has its interfaces automatically names as p33p1 and p34p1. I simply changed the old eth0/eth1 names to the new ones in these shorewall files and it has been working fine for a couple of years: * interfaces (obviously!) * hosts (because I have multiple subnets on both interfaces) * masq * tcinterfaces Why not just "grep -lir eth /etc/shorewall/ and edit the files? HTH Brian(and it's a bit of a hit and miss getting those names back, but dead easy to loose all your networking! :) ) Nigel. ------------------------------------------------------------------------------ Full-scale, agent-less Infrastructure Monitoring from a single dashboard Integrate with 40+ ManageEngine ITSM Solutions for complete visibility Physical-Virtual-Cloud Infrastructure monitoring from one console Real user monitoring with APM Insights and performance trend reports Learn More http://pubads.g.doubleclick.net/gampad/clk?id=247754911&iu=/4140 _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net <mailto:Shorewall-users@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/shorewall-users ------------------------------------------------------------------------------ Full-scale, agent-less Infrastructure Monitoring from a single dashboard Integrate with 40+ ManageEngine ITSM Solutions for complete visibility Physical-Virtual-Cloud Infrastructure monitoring from one console Real user monitoring with APM Insights and performance trend reports Learn More http://pubads.g.doubleclick.net/gampad/clk?id=247754911&iu=/4140 _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users------------------------------------------------------------------------------ _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
-- from the desk of Nigel http://soft-focus-imagining.com http://twin-peaks-video.com
<<attachment: nigel.vcf>>
------------------------------------------------------------------------------
_______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
