Eth0 became eth1

Client has a ZCM11sp1 on SLES11sp? server setup (single primary server, external DB server). Initially they said they could not see the server.
I took a quick look and even though there is only one NIC in the VM setup there are 2 seen in yast. So I moved the IP to eth1 to see if that was the NIC setup to talk on the LAN. NOw I can ping it but nothing else works.
Next I edited the 70-persistant_name_net.rules file in /etc/udev/rules.d/, followed a cool solution to a point (was written for sles10),
Cool Solutions: Renaming a NIC
but the "rename netiface" was not available. I could not find a similar file.
After a reboot I can get into the web interface and users can login, thought I might be home......
My guess is there is a config somewhere that is set wrong. Any help appreciated.
Basically looking for Linux help not Zen - Does anyone know the sles11 command for "rename netiface" that was in the sles10 cool solution?
Any other ideas to try quite welcome!
WO

On 26.10.2012 15:26, whiteowl76 wrote:
>
>> In SLES11, it's much easier. Use Yast. ;) You can rename network cards
>> right there.
>
> Think you missed what I said. I have already gotten the interface to
> reply as eth0, BUT it looks like somewhere else there is a reference to
> eth1.
Quite seriously, I've read and re-read what you posted, but that's
totally not what you said. Can you try again? ;)
To answer a related question, there's most certainly nothing per se tied
to the interface name on a plain SLES and ZCM Server.
Except, of course, if you're running the firewall.
CU,
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de

Similar Messages

How to find on which line - eth0 or eth1 packets are received

hi,
i've two lines - eth0 and eth1 on my board and using tcp sockets. I've used INADDR_ANY in bind(). I get packets on
both eth0 and eth1. How to find to which line(eth0 or eth1) a packet received belongs to ?
Thanks & Regards,
liuxgate

Normal TCP/IP Sockets in Java (ie java.net.Socket) do not offer any exposure to packets and how/when they are received. But why do you care?
Check that. There is a DatagramPacket class, which means you must be able to send around "packets" in some way. I've never seen or used this before, so I can't say. But maybe someone else will know.
Edited by: tjacobs01 on Jan 11, 2012 5:39 AM

Ethernet card: eth0 or eth1?

Hi,
my ArchLinux has a strange behavior regarding the interface to use to connect to the net (ethernet card, dhcp):
sometimes the right interface is eth0, sometimes it's eth1. I "solved" the problem adding both interfaces to my rc.conf:
INTERFACES=(lo eth0 eth1)
this way one of the two interface (the "choice" seems to be "taken" randomly) fails at startup, of course.
I could live with that, but it seems a somewhat ugly solution to me. I'm wondering if I configured something wrong or if that's a bug?
Here's some info about my system:
Kernel 2.6.22-suspend2
Acer Aspire 1500 laptop
Network card : Broadcom Corporation NetXtreme BCM5788
There's a FireWire - it uses an eth interface too, right?
thanks in advance
Simon

I wondered whether someone will run into this funny problem:D
Compiling drivers for both cards into kernel may fix your problem.
Alternatively you may try adding modules for these cards in MODULES in /etc/rc.conf. It may also require adding them to MOD_BLACKLIST.

ETH0 and ETH1 on SOM Dev Board (sbRIO-9651)

I am getting about 33M bytes per second over ETH0 (dev board label) and 36M bytes per second ETH1 (dev board label) using TCP/IP UDP data size of 65,500 bytes which gives the best performance.
Is this the performance limit of the SOM or is there a more preferred method to get something like 80M bytes/sec (800M bit/second) which is what I would like to get.
The one core is running at 70% utilization and the other like 20%.
I have jumbo frame enabled at 9K.
What can I try?
Thanks.

Hello User5551212,
After doing some additional research, it seems that our benchmarking tests for this device put the typical Ethernet communication at around the same rate that you have been getting. There is a limitation associated with the architecture behind the communication that probably will not allow you to get 80 MB/s speeds. The only way around this would be to create your own Ethernet controller in the FPGA, which would take up a lot of the FPGA fabric but could greatly increase the ceiling on communication speeds.
From what you told me, it seems like you have already taken care of most optimizations that we suggest in software (ie, using jumbo frames, increasing packet size, utilizing the Nagle algorithm). The only other suggestion I could make would be using parallel TCP streams. However, I found a couple of resources that might be helpful for the underlying configuration of TCP or UDP. Please keep in mind that changes to the Linux RT kernel will likely not be supported!
- http://www.embedded.com/design/operating-systems/4403058/Accelerating-network-packet-processing-in-L...
- http://www.techrepublic.com/article/take-advantage-of-tcp-ip-options-to-optimize-data-transmission/
- http://datatag.web.cern.ch/datatag/howto/tcp.html
Siana A.
Application Engineering
National Instruments

Eth0 and eth1 are improperly configured [Solved]

*Interfaces solved by reassigning Mac addresses for both interfaces and reflecting those changes in rc.conf
DHCP is no longer working for me and my HP Mini-1125nr netbook is no longer able to get online via ifplugd. This adds to my ongoing battle with Broadcom-wl (I installed it from the AUR) and Arch wireless in general. It seems my interfaces are not setup correctly. I'm using the wiki and google, but not winning the war. At boot network fails and declares
wlan0: unknown interface: no such device
current rc.conf chunks (see my previous config which had working eth0 dhcp)
MOD_AUTOLOAD="no"
MODULES=(lib80211_crypt_tkip wl !b43 !ssb snd-hda-intel atl1)
eth0="dhcp"
wlan0="dhcp"
INTERFACES=(wlan0 eth0)
My NETWORKS is still default (main) as I have not setup a network manager beyond ifplugd
DAEMONS=(syslog-ng hal network netfs @crond @alsa @ifplugd)
ifconfig -a note: wlan missing and eth0 has no inet addr or mask
eth0 Link encap:Ethernet HWaddr 0C:60:76:2D:E9:B6
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:16 Base address:0xc000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
iwconfig
lo no wireless extensions
eth0 IEEE 802.11 Nickname:""""
Access Point: Not-Associated
Link Quality:5 Signal level:0 Noise level:0
Rx invalid nwid:0 invalid:crypt invalid misc:0
lsmod | grep wl
wl 1944061 0
lib80211 3158 2 wl, lib80211_crypt_tkip
lspci -vnn | grep 14e4
01:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01)
lspci -v (written by hand so I'm just putting in the important bits)
Broadcom BCM4312
Kernel Driver in use: wl
Kernel modules: wl, ssb
Atheros AR8132 / L1c Gigabit Etheret Adapter (rev c0)
Kernel modules: atl1c
Last edited by medianmajik (2011-01-23 19:35:02)

You can name the interfaces whatever you like:
https://wiki.archlinux.org/index.php/Co … es_varying
Last edited by schuay (2010-11-11 06:52:10)

[half-SOLVED] eth0 and eth1 getting swapped every time

Hi,
The title says it all, but I don't know what else to do.
I've tried putting the modules in order in the MODULES array in /etc/rc.conf, but it doesn't work. Apparently, the modules in MODULES aren't guaranteed to load in the order they are anymore.
I've tried following this wiki page, about Udev, but it didn't work, too.
I also tried closing my eyes and pretending it doesn't happen, but it didn't work too.
TIA
Last edited by andre.ramaciotti (2009-09-11 15:06:06)

brenix wrote:
Mr.Elendig wrote:http://wiki.archlinux.org/index.php/Ude … _Each_Boot
This is what I did, to me its the easiest solution...
Yeah, except it doesn't work here.
hw-tph wrote:Read the manpage for iftab: man 5 iftab
Quickest and cleanest way, IMHO.
It's half working. I've edited /etc/iftab and I've put 'ifrename' in /etc/rc.local . My wired connection does get renamed, but my wireless doesn't. It gives me an error saying that eth1 is busy, which doesn't make sense as I load wicd only after ifrename.
I think now I have a predictable behaviour: wired is always 'wired' and wireless is always 'eth1', so I'll keep it. It wasn't exactly what I wanted, but it's better than completely random.
As hw-tph's solution is the one that suckless™, I'll stay with it. Thanks to all of you that tried to help.
Last edited by andre.ramaciotti (2009-09-11 15:05:43)

BroadCom Wireless Help

Hey,
I have a broadcom 4328 card, as identified by lspci | grep bcm43
I can't get it to work (in short).
I followed the directions here:
http://wiki.archlinux.org/index.php/Broadcom_BCM4312
But to no avail, eth0 (ethernet) works 100% fine. Wireless isn't listed at all under "ifconfig" nor "iwconfig"
I've tried probing the drivers wl and lib80211_crypt_tkip many times, and removed the b43 module as told. Modprobing them doesn't give errors.
I saw the bottom of that article, but my ethernet is Marvell Yukon card (Macbook Pro), though that is the type of error it is giving me, it just sees nothing.
I've added it to my module array in rc.conf, and restarted many times, but to no avail.
I realize this isn't a lot of information to go on so if you need additional information please ask.
Thanks for your time.

Yeah is a problem with the driver that eth0 became eth1.
But I solve the problem, re-compiling the driver and with a "rmmod wl.ko" and reinstall the package.
See if you can use it this is my rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="local"
USEDIRECTISA="no"
TIMEZONE="America/El_Salvador"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(acpi-cpufreq cpufreq_powersave !snd-pcsp)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="hercolubus"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
eth0="dhcp"
eth1="dhcp"
lo="lo 127.0.0.1"
INTERFACES=(eth0 eth1 lo)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.1.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng hal @cpufreq !network !netfs @crond @alsa @wicd @sshd)

[solved] stable network card name eth0 eth1

Hello, I'm new to Arch Linux. I have two Ethernet interface adapters, let's distinguish them by their MAC addresses MAC0 and MAC1. Relationship between MAC addresses and 'eth' unit numbers may change after reboot. Sometimes
MAC0~eth0
MAC1~eth1
sometimes
MAC0~eth1
MAC1~eth0
When they swap, I should change 'rc.conf' settings (IP addresses and such) or keep rebooting until they swap back. I want to name devices in 'rc.conf' by their MAC addresses, is it possible?
Last edited by beroal (2009-06-14 01:47:57)

Had this issue recently. The best solution is to create a rule in udev which handles the naming task. See http://wiki.archlinux.org/index.php/Udev. The general solution didn't solve my problem. The udev rule has been effective so far. I renamed to lan0 and lan1. If you do rename remember to change your configs that refer to the network cards.
*edit: just a little late, typing with 1 hand...*
Last edited by stryder (2009-06-07 17:34:59)

Eth0 connectivity depends on eth1 being plugged in?

The problem is that if I pull the plug out on eth1 (PCI) then eth0 (onboard) connectivity stops.
If I pull eth0 then eth1 continues to respond, while eth0 does not.
I have seen this now on two different machines, so it seems to me to be a 'feature' of Arch.
I am a bit unhappy about it as it somewhat defeats the intention with redundancy.
Any take on that?
I am on Arch64
I just follow the beginners guide and install arch with two ethernet cards, one builtin and one PCI.
I edit rc.conf:
eth0 = "dhcp"
eth1 = "eth1 10.10.11.242 broadcast 10.10.11.255 netmask 255.255.254.0"
INTERFACES=(eth0 eth1)
gateway="default gw 10.10.10.1"
ROUTES=(gateway)
eth0 get its IP:
eth0 Link encap:Ethernet HWaddr 00:23:54:40:48:BB
inet addr:10.10.10.69 Bcast:10.10.11.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1258618 errors:0 dropped:0 overruns:0 frame:0
TX packets:846 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:99922868 (95.2 Mb) TX bytes:62041 (60.5 Kb)
Interrupt:29 Base address:0xe000
eth1 Link encap:Ethernet HWaddr 00:50:FC:22:F7:D4
inet addr:10.10.11.242 Bcast:10.10.11.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:426 errors:0 dropped:0 overruns:0 frame:0
TX packets:94 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:44279 (43.2 Kb) TX bytes:11986 (11.7 Kb)
Interrupt:17 Base address:0xc000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:799 errors:0 dropped:0 overruns:0 frame:0
TX packets:799 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:48572 (47.4 Kb) TX bytes:48572 (47.4 Kb)
Last edited by slot (2010-02-15 15:45:03)

jac wrote:I think the title is a typo.
You´re welcome to suggest something better
How do you unplug it? Do you just mean taking the ethernet cord out?
Yes, but the same happens when it boots with one cable plugged only
Did you set up static device naming, or do they get assigned whatever name is available?
No I didn't, but I think they'r fairly stable, and I don't care which one gets the IP's
Unfortunately I don't know too much about networking, but maybe it has to do with the fact that eth1 is static and eth0 is dhcp?
Edit: For testing the last suggestion, can you try switching their configs? See if eth0 is done statically if it will work with the (then, dhcp configured) eth1 unplugged.
Yes - I will.

Eth0 changes to eth1

with the new kernel 2.6.19 my eth0 card sometimes changes to eth1, anyone know if this is a bug or something?
my computer specs:
MSI k8n SLI-FI
AMD Athlone 64 3200+
512 mb ram
i do only have one network card so i think its wired that it changes from eth0 to eth1 sometimes..

Snowman wrote:this might help:
http://wiki.archlinux.org/index.php/Ude … _Each_Boot
I think that wiki is a little outdated as far as the actual file to modify. On my system its /etc/udev/rules.d/70-persistent-net.rules. If you find that file and modifying works let us know and I (or you can) update the wiki.

Arch server - swaps eth0/eth1 randomly on reboot ? Can you force

Hi.
I have a server (quite good spec), has 2 eth ports
eth0 = e1000e
eth1 = tg3
After reboot they randomly swap over - screwing my network config up...
Is there a way to force eth0/eth1 to use a particular driver ?
Any help would be good.
Thanks

Hi - I tried removing /etc/udev/rules.d/75-persistent-net-generator.rules.optional and rebooting
Still occurs...
Its a really weird bug! Seems that every reboot they swap (it could just be random though)
Is there any other way of forcing each eth to use a specific driver ?
Cheers

Cisco Clean Access Server eth0 port inactive on install

I am trying to learn how the Cisco NAC appliances work. I have created a small self-contained test network with a Server 2003 domain controller, a fake domain setup and some workstations joined to the domain.
I have two NAC appliances, one is the Server and one is the Manager.
When I follow the instructions from the manual to install the server from the CD everything seems to go fine. I plan to use it as a bridge in the network so I applied the same IP address to both the eth0 and eth1 interface (the eth1 interface is not connected to the network during install as per instructions)
Here is the issue I am having: After configuration is finished and the CCA server re-boots, I cannot ping the server when it is connected by eth0. If I swap the network cable over to eth1, however I can ping the device.
Is this normal?

I have the same issue. But it gets even stranger; I had the CAM/CAS working in a test LAN enviroment, got the AD SSO to work by appllying VLANs based on AD group membership of the user logging on. Client was pleased.
Move the two NAC devices to their location and reloaded clean both CAM & CAS from CD, did the same configuration and now eth0 (Trusted) can't see the AD domain controller but can see the CAM. I ran nslookup on the CAS to test the network settings and the result is no server found - the DNS server is the AD domain controller.

NIC changed from eth0 to eth2

Just did a pacman -Syu to get the kde updates and such ... and when I rebooted, my NIC was changed from eth0 to eth2 ... I saw that ipw2200 was among the updates... could that cause this?

Well ... now I think that my NIC gets eth0, and my wlan NIC gets eth1 every time, but sometimes none of them gets set up at all.
I boot, and when I do en ifconfig, the only thing that shows up is 'lo'. If I try 'ifconfig eth0 up' and 'dhcpcd eth0', eth0 does not get set up correctly. I then try a reboot, and usually the NICs work after the reboot.
I added an 10-network.rules in the /etc/udev/rules.d/ folder which contains the following lines:
<code>SUBSYSTEM=="net", SYSFS{address}=="00:0b:5d:77:b3:aa", NAME="eth0"
SUBSYSTEM=="net", SYSFS{address}=="00:0e:35:da:97:36", NAME="eth1"</code>
In /etc/rc.conf I have:
<code>lo="lo 127.0.0.1"
eth0="dhcp"
eth1="dhcp"
INTERFACES=(lo eth0 !eth1)</code>
Anyone who can help me out here?

VIPCA showing only eth0 interface

Hi all,
I'm installing Oracle 10g R2 2 node RAC on RHEL4 U4 for R&D purpose. And i'm following the steps given in http://www.oracle.com/technology/pub/articles/hunter_rac10gr2.html article.
While installing clusterware software asked me to run orainstRoot.sh and root.sh script on both nodes. On node1 both the scripts ran succesfully and on node2 root.sh script gave the following error..
The given interface(s), "eth0" is not public. Public interfaces should be used to configure virtual IPs.
It is given in the doc that, the above error can be resolved by running the VIPCA GUI utility on the node where this error is occurred.. when i ran VIPCA utility on Node2..in Network Interfaces section, it is showing only eth0 (public) and it is not showing eth1. But in the above given link, it is mentioned that we need to select both eth0 and eth1.
Can anybody tell me what might be the problem?
Thanks,
Praveen

Hi,
Please upload/review your ifconfig -a output on both nodes. you should see 3 IPs on each node, one for the interconnect, one for the public and one for the virtual. These should be persistent after a reboot, and match. eth0 on one node should be eth0 on the second, etc.
If this is done, you should not have an issue with VIPCA.
Thanks,
Idan.

Help me with eth1 and dhcp !

Hey there, i think i am close on this one. i have searched from pillar to post on forums everywhere. so here goes..
i connect to the internet via cablemodem to eth0
i want to serve out dhcp to another computer via eth1
(yep, using crossover cable)
it worked with assigning a static ip but i cant get it to do dhcp.
firestarter fails when i try to set it up like that.
i have dnsmasq and all the stuff i think i need.
anyone have some advice ?

maybe this will help
from rc.conf
# Networking
HOSTNAME="Arch"
# Module to load at boot-up (in this order)
# (prefix a module with a ! to disable it)
MODULES=(!usbserial !ide-scsi 8139too natsemi sis lp parport_pc sd-mod ohci-hcd snd-pcm-oss snd-ens1371 )
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# (prefix an interface in INTERFACES with a ! to disable it)
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
lo="lo 127.0.0.1"
eth0="dhcp"
eth1="eth1 192.168.1.1 netmask 255.255.255.0 broadcast 192.168.1.255"
INTERFACES=(lo eth0 eth1)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# (prefix a route in ROUTES with a ! to disable it)
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Daemons to start at boot-up (in this order)
# (prefix a daemon with a ! to disable it)
DAEMONS=(syslogd klogd !pcmcia iptables network netfs alsamixer crond hotplug httpd dnsmasq cups gdm)
# End of file
From Iptables.rules
# Generated by iptables-save v1.2.11 on Tue Dec 14 15:03:28 2004
*nat
:PREROUTING ACCEPT [163:9508]
:POSTROUTING ACCEPT [12:628]
:OUTPUT ACCEPT [0:0]
-A POSTROUTING -o eth0 -j MASQUERADE
COMMIT
# Completed on Tue Dec 14 15:03:28 2004
# Generated by iptables-save v1.2.11 on Tue Dec 14 15:03:28 2004
*filter
:INPUT ACCEPT [1455:1486827]
:FORWARD ACCEPT [6279:4965423]
:OUTPUT ACCEPT [1318:140982]
COMMIT
# Completed on Tue Dec 14 15:03:28 2004
from /etc/dhcp.conf
# DHCP configuration generated by Firestarter
ddns-update-style interim;
ignore client-updates;
subnet 192.168.1.0 netmask 255.255.255.0 {
option routers 192.168.1.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 24.116.0.157;
option ip-forwarding on;
range dynamic-bootp 192.168.1.2 192.168.1.100;
default-lease-time 21600;
max-lease-time 43200;
bogus-priv
dhcp-range=192.168.0.50,192.168.0.150,12h
cache-size=150
log-queries
ok, lemme know where i may be screwed up here.
thanks

Eth0 became eth1

Similar Messages

Maybe you are looking for