Good morning Jay,
If you want to control and have persistent names for NIC's on Linux, the
preferred method these days is udev (man udev).
On an SLES system, we have entries like:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:e0:ed:08:72:04", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth1"
for each NIC in the file /etc/udev/rules.d/70-persistent-net.rules. You
just have to match the MAC address with the name.
The network configuration interface should create these lines for you,
so you can simply edit the file and change the NAME. Do this from the
console and reboot right after the edit, and do not use the network
configuration interface afterwards, as it will overwrite your changes.
The files may not be in the same place in Ubuntu but there is some
information available if you google "ubuntu udev".
Patrick
Jay Ridgley wrote:
> On 03/17/2011 10:00 PM, Tom Eastep wrote:
>
>> On 3/17/11 7:36 PM, Jay Ridgley wrote:
>>
>>
>>> All other connections are wired and within the range 192.168.139.0/28
>>>
>>> subnet 192.168.139.0 netmask 255.255.255.240 {
>>> option routers 192.168.139.2;
>>> option subnet-mask 255.255.255.240;
>>> option domain-name-servers 24.93.41.127, 24.93.41.128;
>>> option ip-forwarding off;
>>> }
>>>
>> ARP
>>
>> ? (192.168.139.4) at 00:a0:cc:26:cb:bd [ether] on eth3
>> ? (192.168.139.3) at 00:1a:a0:99:d0:90 [ether] on eth3
>> ? (192.168.139.5) at 00:90:a9:6e:27:24 [ether] on eth3
>> ? (70.112.128.1) at 00:1d:a2:e8:41:d9 [ether] on eth0
>> ? (192.168.100.1) at 00:02:8a:de:ad:02 [ether] on eth0 <------------- this
>> is reflected in the dump? eth0 is my firewall and to my
>> ? (192.168.139.37) at 00:1a:70:84:51:40 [ether] on eth4<===
>> knowledge the address contained is NOT part of my network.
>>
>> The only host known to the firewall on eth4 is .37. <------------- that
>> would be correct
>>
>> -Tom
>>
>
> Tom,
>
> Your prior message asked about the difference between eth1 and eth2 vs eth3 &
> eth4. Yes, all of the config files that required changes have been fixed to
> reflect that change.
>
> This was brought about from moving NICs from the old system to the new
> system. I
> was having to do it so many times I purchased a pair of new NICs and when I
> installed them they showed up as eth3 and eth4. I have found no way to change
> them to eth1 and eth2. Do you have any ideas? I don't feel like that should
> be a
> worry, however.
>
> I am very concerned about the 168.192.100.1 entry above. Is there a lot of
> traffic to/from it?
>
> I did an arp from my firewall and 192.168.100.1 points to my main system
> (192.168.139.5). I am going to try to see where that came from.
>
> Thanks,
> Jay
>
--
Patrick McNeil Université de Montréal - DGTIC
Pav. Roger-Gaudry, X-205 Téléphone: (514) 343-6111, poste 5247
Courriel: [email protected]
Télécopie/FAX: (514) 343-2155
[email protected]
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
