Ethernet interface eth0 missing

Hi!
Since a few days, on my laptop (Thinkpad X200) there is no ethernet interface anymore.
The output of ifconfig:
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.101 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::221:6aff:fe11:a710 prefixlen 64 scopeid 0x20<link>
ether 00:21:6a:11:a7:10 txqueuelen 1000 (Ethernet)
RX packets 45280 bytes 47188889 (45.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 37841 bytes 5350719 (5.1 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
I tried to reconfigure the device according to the wiki page, but the Ethernet section of lspci -v does not tell the kernel module:
00:19.0 Ethernet controller: Intel Corporation Device baad (rev 03)
Subsystem: Lenovo Device 20ee
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at f2600000 (32-bit, non-prefetchable) [size=128K]
Memory at f2625000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 1840 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [e0] PCI Advanced Features
I am pretty helpless now and I would be glad if someone could give me a hint!

ewaller wrote:
Welcome to Arch. Two things in addition to Graysky's link (TL;DR version of the link: It is probably not called eth0:)
1. ifconfig is depreciated. The preferred command now is a sub command of ip. The command is: ip link
2. ifconfig only displays the interfaces that have an address. To see all the interfaces, use ifconfig -a or, of course, ip link
It might actually be called 'eth0', since his wireless is 'wlan0', but otherwise, you are right, he should be checking for all interfaces and not just those that have an address.

Similar Messages

Using TCP on the second ethernet interface

Hello,
I'm using a PXI 8109 running Pharlap.
I'm trying to use the second ethernet interface of my PXI to send UDP and TCP packets. The primary interface is used to manage Veristand Channels.
Here is the configuration of my two ethernet interfaces:
- eth0 (primary):
IP : 10.0.0.3
subnet mask : 255.0.0.0
- eth1 :
IP : 192.168.10.9
subnet mask : 255.255.255.0
For UDP, I have no problems, packets are sent to the second interface as I want. I think it work because there is a "network address" input on the "UDP Open" VI so the system can choose the right interface.
For TCP, I use the "TCP Open a connection" VI but there is no this kind of input. And it is not working : I assume the system is trying to use the primary interface but it can't route packets...
For information, my two networks are physically independant.
Can you help me finding out what's going on ? Is it possible to use TCP on the second ethernet interface ?
Many thanks,
Regards,
Laurent
Solved!
Go to Solution.

Sorry but i don't understand your Input problem!!!
Could you give me more details?
The link below can maybe be help you:
http://digital.ni.com/public.nsf/allkb/67F94BB93BCE32CF86257367006B3659?OpenDocument
Best regards
Aurélien Corbin
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Cahiers de vacances de NI
Présentations en ligne : 12 fondamentaux à réviser, du 9 juillet au 29 aoû...

[solved] dhcpStart:interface eth0 is not Ethernet ...

Trying to setup the network of my laptop, I've edited rc.conf and put eth0="dhcp, commented the statip ip line and added the driver module of the card in the MODULE section.
Configuration files are just like the desktop except of the different drivers.
When running "/etc/rc.d/network start" or "dhcpcd eth0" I get the following error in /var/log/errors.log one finds,
dhcpStart: interface eth0 is not Ethernet or 802.2 Token Ring
Loading or unloading the driver module doesn't differ, I get the same error.
ifconfig -a shows a down network interface named eth0

The card is Marvell Yukon 88E8036 PCI-E Fast Ethernet Controller and it's driver is supposed to be sk98lin available in arch's 0.7 kernel (2.6.10).
Beside of trying to do things using arch's configuration files, I'm trying the generic way. I'm also trying static IP instead of dhcp.
My IP should be 192.168.1.101
and the gateway IP is 192.168.1.1
modprobe sk98lin
ifconfig eth0 192.168.1.101 up
route add default gw 192.168.1.1
The output of dmeg is as follows:
http://www.macamania.com/dmesg_newcomer/
The output of route -n is as follows:
http://www.macamania.com/route_newcomer/

Netctl: Using same ethernet interface for PPPoE and LAN

Configuration overview
One ethernet interface connected to a switch which has both the LAN and my ADSL router (running in bridge mode).
My Arch PC should connect via PPPoE (possibly multiple connections) to the ISP and be able to access the LAN simultaniously. (Connection sharing is another goal, but that is not yet relevant...)
The main reason for not changing the setup is that some other people on the LAN use their own ISP accounts over the same line.
I currently have two netctl profiles, adsl (PPPoE) and ethernet (LAN).
I also want the ability to run two PPPoE sessions simultaniously (with routing to determine which data uses which connection). (This is not currently relevant, but have been in the past and might be again in the future...)
The problem:
I'm unable to connect to both the ethernet and ADSL profiles simultaniosly.
I tried to switch to Network manager, but it has a known bug preventing the same interface from being used for both plain LAN and PPPoE.
The workaround that currently seem to work, is to use ifconfig to manually add an IPv4 address to the ethernet interface after connecting the PPPoE session.
The systax for a PPP profile also have the unusual feature that its "Interface" value refers to the underlying interface, rather than the created PPP interface.
I currently have it working on my Ubuntu HDD and previusly had it working on Gentoo.
(Under a standard Windows XP / 7, it works with a single connection, but multiple simultanious PPPoE connections require soem non-standard tools...)
The Ubuntu setup
eth0 is set up by NetworkManager (I didn't have the option to avoid that one...) and I have the PPPoE connections configured in my /etc/interfaces: (ppp0 is not currently in use, was previously)
auto lo
iface lo inet loopback
iface ppp0 inet ppp
pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf
provider dsl-provider-local
auto ppp1
iface ppp1 inet ppp
pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf
provider dsl-provider-intl
I then have these files under /etc/ppp/peers: (with the name mathing the "provider" line) An example below. (passwords are in the /etc/ppp/*-secrets files)
unit 0 # This specifies that the created connection uses ppp0, differs in others.
noipdefault
hide-password
noauth
persist
plugin rp-pppoe.so eth0
user "myuser@radius-domain"
Arch setup:
ADSL profile:
Description='ISPName'
Interface=enp4s0
Connection=pppoe
User='username@radius-server'
Password='mysecret'
ConnectionMode='persist'
#UsePeerDNS=true
# Override default LCP parameters from /etc/ppp/options
LCPEchoInterval=15
LCPEchoFailure=10
Ethernet profile:
Description='A basic static ethernet connection'
Interface=enp4s0
Connection=ethernet
IP=static
Address=('192.168.0.8/24')
Solutions / Workarounds
1. Manually configuring a IP after connecting PPPoE
2. Not using netctl for pppoe, rather using the pppoe-setup tool
3, Figuring out the correct netctl setup for this scenario - which is what I need your help for...
Possibly related links
https://bbs.archlinux.org/viewtopic.php?id=163956
https://wiki.archlinux.org/index.php/Sh … Connection - Insists that an extra interface is needed for sharing connections - which is not a fundemental Linux requirement

I used to use ubuntu & if you reboot into it (if you can) & run:
$ ifconfig
you will see eth0 & ppp1
ppp1 will be set as the default gateway.
Your issue in Arch is that you currently want the PPPoE interface to be the same as your LAN, this will not work at best you will need to bridge the 2 BUT I think what you should do is use the networkmanager profile as a guide & have netctl create an adsl interface called ppp1 & set that as the default gateway
thus:
Description='ISPName'
Interface=ppp1
Connection=pppoe
User='username@radius-server'
Password='mysecret'
ConnectionMode='persist'
#UsePeerDNS=true
# Override default LCP parameters from /etc/ppp/options
LCPEchoInterval=15
LCPEchoFailure=10
I think this will work, try it & good luck
PS:
I do not use netctl as I use dhcp but you might even be able to configure netctl to set ppp1 as default gateway as a "post-up" command OR just create a systemd service to do it after the relevant netctl services are up
Last edited by t0m5k1 (2013-06-18 17:56:02)

Leave plugged in Ethernet interface disabled (down) [solved]

Is it possible to keep a plugged in Ethernet interface down by default at boot? I have a USB Ethernet adapter I'd like to keep down until needed. Despite not having an IP, it is automatically activated and up at boot up (it is a spanned port).
The ipv6 stack is in the kernel but not used for interfaces, udev renames the device, and nothing is configured for it in NetworkManager (although have tried to manage it this way to avail). dhcp shouldn't be a problem, unless I'm missing something that is pre-configured by default?
The only solution I can think of is to blacklist the module, which would allow me to probe it when needed to bring it up (there is also the physical side of doing this as well). The only drawback is these aren't the most efficient ways to manage an interface.
Any suggestions are appreciated.
Last edited by jskier (2014-03-27 19:49:44)

Standard NICs are kept down unless configured (eg. with netctl, etc). My net2 is plugged into a switch:
$ ip a s
3: net2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:00:5a:73:94:a2 brd ff:ff:ff:ff:ff:ff

Ethernet interface problems...

I'm having some problems with a Solaris 8 on x86 server not seeing its ethernet interface between reboots without reconfiguring every time.
About two weeks ago, a backup script on my main file sever spontaneously appeared to crash NIS, and the box was rebooted. When it came back up, it appeared to have forgotten about its ethernet interface, an Intel GigE card at e1000g0. The error message at boot is:
"Protocol wrong type for socket"
... followed by the attempt to move the IP from e1000g0 to any other active interface, which of course failed, since it's the only interface in the box.
I've found that the only way to get the interface up is to boot -rs so it forces a reconfiguration and then drops into single-user mode. Then I can plumb the interface and number it by hand. I can then init 3 and everything is fine. If I don't boot into single user mode, it tries to start NIS, fails, and the box hangs.
If I reboot at this point, the box fails detect the interface again and I have to go through the whole process once more.
I've tried at least one other Intel GigE card, as well as moving them between PCI slots to no avail. I've removed the driver and added it back in, same thing.
Does anyone have any idea what might be the problem? I'm completely stumped.
I'm not sure if it's pertinent, but the when I run my backup script and it crashes NIS, I get the following errors in /var/adm messages.
Aug 10 15:27:10 myserver smbd[23184]: [ID 105279 user.error] nis_cast: t_open: /dev/udp:No such device or address
Aug 10 15:27:10 myserver smbd[23176]: [ID 566193 user.error] n2a get_local_info: ioctl (get interface flags): No such device or address
This is what happened to cause the reboot in the first place, after which the interface failed to show up. I'm not sure if it's important, but I figured I'd include it anyway.
Thanks for any help!
Franklin

I'll check that in just a bit. On the other hand I noticed that by PXE OPROM in the mobo settings the Intel boot agent started from the beginning and not just when rebooting, however, it didn't solve the issue. My new guess is that the issue is not IBA related.
I'm not completely sure if it is an eth0 vs eth1 issue, as loading Xubuntu (which automatically connects to the networks) doesn't solve it. If I reboot it automatically connects to the wired network, if turning on for the first time it shows a "no wired network available" ,and instead offers to connect to the available wireless networks.
I used to have the first firmware (probably dating back to february or march) but updated to a more recent one and yesterday got the most recent firmware available through Asus, but the issue persisted.

Eth0 missing, Xorg won't start, and removable media problems

When I got back from vacation last night, I turned on my computer and several problems arose. I tried starting X with startx like I usually do but it wouldn't come up. I tried opening elinks to google the problem only to find that the internet wouldn't work. A quick ifconfig showed that eth0 was missing.
I googled the problem with my netbook and found this thread. It sounds like the OP couldn't see eth0 right after he installed Arch Linux, but eth0 worked fine for me about 10 days ago. Also, my motherboard is an Asus M2A-VM rather than a P8P67. Nonetheless, I copied the driver he linked to to a flash drive. But when I plugged the flash drive into my desktop, it didn't show up in /dev/. In fact only two of the thee hard drives I have installed showed up. The two that show up are SATA and the one that doesn't is an IDE. Not to mention the flash drive that didn't show up.
For further testing I booted an old Ubuntu Jaunty live CD I found laying around. In Ubuntu eth0 does show up. As for the hard drives, it looks the same as it does in Arch Linux.
I think I may possibly have a bad motherboard due to devices not showing up in /dev/, but I want to be completely sure. I want to get a new computer either way but for now I want to focus on at least getting eth0 and X working again. Any ideas on how I can get that driver over to my desktop or how I can get X started?

No, I didn't follow the beginners install guide. I just installed Arch Linux then installed the packages that I wanted.
Here is my /etc/rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# Note: Using "localtime" is discouraged.
# 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
# VERBOSE: Verbose level (from 1 to 8). man 3 syslog for level info
LOCALE="en_US.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="America/Denver"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
VERBOSE="3"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
MOD_AUTOLOAD="yes"
MODULES=(fuse usblp)
# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30
# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"
# Scan for BTRFS volumes at startup
USEBTRFS="no"
# 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="rockstar"
# 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
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
#eth0="dhcp"
#INTERFACES=(eth0)
eth0="eth0 192.168.1.103 netmask 255.255.255.0 broadcast 192.168.1.255"
INTERFACES=(eth0)
# 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.0.1"
#ROUTES=(!gateway)
ROUTES=(gateway)
gateway="default gw 192.168.1.1"
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
# 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
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
DAEMONS=(hwclock syslog-ng network netfs crond dbus mpd sshd cups avahi-daemon)
And the sound works so I guess I don't need a sound module? Well, it did before I left for vacation.
Last edited by resuni (2011-08-08 04:04:05)

Bringing up interface eth0: e1000 device eth0 does not seem to be present, delaying initialization.

I performed a software reboot on the MSE3310. After the reboot the MSE was no longer visible on the network. I went and consoled into the device and it was operational. I ran the msed stop and msed start commands. I got this message when it tried to load eth0
Bringing up interface eth0: e1000 device eth0 does not seem to be present, delaying initialization.
[FAILED]
Earlier in the day I had updgraded the firmware from 6.0 to 7.0.230.0.
Can I recover the eth0? Is this related to the firmware upgrade?
Thanks.
Jason

Tarik,
This procedure worked great! After adding the HWADDR parameter to the eth0 config file and rebooting the server, we are now able to access the server on the network again. Thank you very much for the quick reply!
Here is the procedure if others need this.
ifconfig -a showed the eth0 interface was renamed to _tmp462132856
[root@MSE-CPW-01 ~]# ifconfig -a
__tmp462132856 Link encap:Ethernet HWaddr 00:15:17:F1:4D:C7
          BROADCAST 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:169 Memory:e8180000-e81a0000
eth1      Link encap:Ethernet HWaddr 00:15:17:F1:4D:C8
          BROADCAST 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)
Then issued
vi /etc/sysconfig/network-scripts/ifcfg-eth0
to edit the file and add the HWADDR=xx:xx:xx:xx:xx:xx
Then issued a 'shutdown -r now' to reboot the server
After a reboot, network connectivity was restored!
Thanks!
Brian

[SOLVED] Bring up ethernet interface without connection

I have two ethernet interfaces in my computer. eth0 connects to the router for the internet, I'm not concerned about that. eth1 I use sometimes to plug a laptop into, and sometimes a MS Windows games PC. Most of the time I don't use it, and there's nothing plugged into it.
I have
NETWORKS=(eth0 eth1)
in rc.conf, and this in /etc/network.d/eth1:
CONNECTION='ethernet'
DESCRIPTION='Internal network'
INTERFACE='eth1'
IP='static'
ADDR='192.168.1.1'
At first boot, there's usually nothing plugged in to eth1, so the 'eth1' profile fails to start:
> sudo netcfg eth1
:: eth1 up [BUSY] > No connection
[FAIL]
> ip addr show eth1
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 00:1b:ee:00:fe:d6 brd ff:ff:ff:ff:ff:ff
Why won't it start up eth1? I want it to give eth1 the IP of 192.168.1.1, even though there's no cable in it. This causes a problem when, after starting the main PC, I plug in a cable to eth1 and start a device (eg. laptop). I have to plug it in, start up the device (which is set to get a DHCP IP from my computer), manually start up eth1 on the PC, then rerun the connect command from the device.
Last edited by Smarthound (2012-04-26 22:34:54)

When I start ifplugd:
Apr 26 22:38:23 localhost ifplugd(eth1)[1268]: ifplugd 0.28 initializing.
Apr 26 22:38:23 localhost ifplugd(eth1)[1268]: Using interface eth1/00:1B:EE:00:FE:D6 with driver <r8169> (version: 2.3LK-NAPI)
Apr 26 22:38:23 localhost ifplugd(eth1)[1268]: Using detection mode: SIOCETHTOOL
Apr 26 22:38:23 localhost ifplugd(eth1)[1268]: Initialization complete, link beat not detected.
So far, so good, but when I plug a cable into eth1, the link is detected, waits a few seconds, then fails:
Apr 26 22:43:17 localhost ifplugd(eth1)[4946]: Link beat detected.
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: Executing '/etc/ifplugd/ifplugd.action eth1 up'.
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: Warning: Your network settings are deprecated.
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: Please refer to /etc/rc.conf on how to define a single wired
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: connection, or use a utility such as netcfg.
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: up: error fetching interface information: Device not found
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 metric 1
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: inet 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: ether 00:1b:4d:4e:c3:d7 txqueuelen 1000 (Ethernet)
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: RX packets 2942 bytes 1534429 (1.4 MiB)
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: RX errors 0 dropped 0 overruns 0 frame 0
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: TX packets 2870 bytes 600353 (586.2 KiB)
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: device interrupt 44 base 0xc000
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 metric 1
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: ether 00:1b:ee:00:fe:d6 txqueuelen 1000 (Ethernet)
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: RX packets 2 bytes 736 (736.0 B)
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: RX errors 0 dropped 0 overruns 0 frame 0
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: TX packets 0 bytes 0 (0.0 B)
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: device interrupt 19 base 0xe000
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436 metric 1
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: inet 127.0.0.1 netmask 255.0.0.0
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: loop txqueuelen 0 (Local Loopback)
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: RX packets 2497 bytes 1134472 (1.0 MiB)
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: RX errors 0 dropped 0 overruns 0 frame 0
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: TX packets 2497 bytes 1134472 (1.0 MiB)
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: Usage: inet_route [-vF] del {-host|-net} Target[/prefix] [gw Gw] [metric M] [[dev] If]
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: inet_route [-vF] add {-host|-net} Target[/prefix] [gw Gw] [metric M]
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: [netmask N] [mss Mss] [window W] [irtt I]
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: [mod] [dyn] [reinstate] [[dev] If]
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: inet_route [-vF] add {-host|-net} Target[/prefix] [metric M] reject
Apr 26 22:43:18 localhost ifplugd(eth1)[4946]: client: inet_route [-FC] flush NOT supported
Apr 26 22:43:27 localhost ifplugd(eth1)[4946]: Program execution failed, return value is 1.
Do you think it's failing because it's issuing a bad route command? Is my /etc/network.d/eth1 correct (see initial post)?

Ipv4 from dhcp, ipv6 static on single interface eth0

Hi,
pls help me understand or solve my problem with my network setup.
I had ipv4 ip address assigned dynamically and ipv6 set statically, both via netcfg and everything worked without problem.
This is my netcfg config:
CONNECTION='ethernet'
DESCRIPTION='A basic dhcp ethernet connection using iproute'
INTERFACE='eth0'
IP='dhcp'
PRE_UP='ethtool -s eth0 wol g'
PRE_DOWN='ethtool -s eth0 wol g'
## for IPv6 autoconfiguration
#IP6='stateless'
## for DHCPv6
IP6='static'
ADDR6=(2002:54f2:xxxx:1::2/64)
GATEWAY6=2002:54f2:xxxx:1::1
But someday I received error when booting up and also when I try to start profile manualy:
/etc/rc.d/net-profiles start
:: eth0 up
RTNETLINK answers: File exists
Adding gateway 2002:54f2:xxxx:1::1 failed
No profile started.
I found that I can't have two gateways on one interface, but until now there's no problem.
When I disabled GATEWAY6 line from config, eth0 profile can be started but ipv6 connectivity didn't works.
I tried set ipv6 to stateless that works, but after some time not more that 5min network connection resets and after recovery in couple of seconds only ipv4 works.
Where's a problem? What can I do to achieve same setup I had before some update last week?
Thanks

houmles wrote:I found that I can't have two gateways on one interface, but until now there's no problem.
I suspect it's a problem with that; I've noticed this problem as well.
When trying to add multiple default gateways with iproute2 (ie, `ip r a default via xxx:xxx:xxx::xxxx`) it errors with the error you've mentioned. I'm not sure if this is a kernel bug, iproute2 bug, or not a bug at all.
Having multiple default IPv4 gateways works fine.
I believe netcfg doesn't check for an existing gateway and delete it first (or use `ip r r` instead or `ip r a`) before adding the one; but I haven't checked the code so I could be wrong.
EDIT:
OK, I couldn't resist looking at the code, and it indeed does a 'dumb' addition of the gateway:
112 if [[ -n "$GATEWAY" ]]; then
113 report_debug ethernet_iproute_up ip route add default via "$GATEWAY" dev "$INTERFACE"
114 if ! ip route add default via "$GATEWAY" dev "$INTERFACE"; then
115 report_iproute "Adding gateway $GATEWAY failed"
116 fi
117 fi
I'm looking at making a patch now. Patch and bug report: https://bugs.archlinux.org/task/29480
Last edited by fukawi2 (2012-04-16 01:00:09)

Why the "hme0" interface is missing?

Hallo! I'm working on a Sun Blade 150 (Solaris 8 4/01). I did a "ifconfig -a" and only see the "lo0" loppback interface and the "eri0" interface.
Why the "hme0" interface is missing?
Edited by: Wolfgang073 on Jan 17, 2010 9:11 AM

Wolfgang073 wrote:
Hallo! I'm working on a Sun Blade 150 (Solaris 8 4/01). I did a "ifconfig -a" and only see the "lo0" loppback interface and the "eri0" interface.
Why the "hme0" interface is missing?
Edited by: Wolfgang073 on Jan 17, 2010 9:11 AM... because for Solaris-ethernet-on-SPARC, the interface name is specific to the chipset that is used for the function.
Your SB150 uses an "ethernet RIO interface" (ERI) on a discrete chipset and does not use hardware for what has often been named "highspeed-media-ethernet" (HME).
The hardware is different, thus the acronym is different.
Others may choose to offer a better description.

Dolby Advanced Audio Interface software missing HP Pavilion Ultrabook 14-b003sa

I updated my HP Pavilion Ultrabook 14-boo3sa to windows 8.1 a couple months ago and since then the dolby advanced audio interface software is missing. The speakers are working and sound fine but I just want the option of the equaliser again. I have looked at the drivers available online and the most upto date driver for audio for this laptop is an IDT audio driver from 2012 for windows 8. Is there a more upto date driver that has the interface software? or is it just a case that the software has been removed on the update due to compatability issues? It sounds like dolby advanced audio is still active there is just no interface available as before I updated to windows 8.1. Please help. Thank you.

Hi Lhawley91,
I understand you are having issues with the Dolby Advanced Audio Interface software missing HP Pavilion Ultrabook 14-b003sa. This package contains the driver that enables the IDT High-Definition (HD) Audio for Windows 8.1.
http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-112631-1&cc=us&dlc=en&lc=en...
Hope this helps.
Thanks.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

Status LIS9 of the User interface MP000200 missing

Hi All,
While creating leaving action. System is giving error (Status LIS9 of the User interface MP000200 missing.
Mentions below are my configuration.
Infogroup
COP 0001 Org assignment
LIS9 0002 Personal Data
LIS9 0006 address
LIS9 0105 Communication
And Personnel Action type are:- 0 0 0 MSN20 (Tick) (Tick) (Not tick)
Let me know how to resolve it.
Regard
Ashish

Hi,
make sure that LIS9 should not be used to the Infotypes which are having Time Constraint 1
Check V_T582A for time constratints and also check V_T588D to remove the operation LIS9 forLeaving/ termination action.
for your information
Infotype 0002 should NEVER be delimited as part of the Leaving Action.
The help text for the Operations field of the Info Group states the following:
In the Leaving action, use the "delimit" (LIS9) operation to delimit records.
Please remove the infotype 0002 from the info group, then run the leaving action, you will not find an error message
The reason why you get the error is because the status LIS9 does not exist on MP000200 .
You can see this via the menu painter via SE41.
regards,
mohammed
Edited by: 0mohammed1 on Oct 14, 2011 1:51 PM

Setup more than one ethernet interface

Hi,
On a 10.5.2 server, I have 4 ethernet ports, 2 on Lan and 2 on Wan with public IP.
What I am suposed to do first :
1- Setup 1 lan interface, DNS, others interfaces an d thne services
2- Setup 4 interfces, Dns, Services
3- Other
Services planned on that Xserve : DNS, OD, Ical, VPN, MAil, Web.
Thank's four your help
Eric Sudan

Thank's for your response servantofserver,
I'll have an internal DSN, so I'am not sure of one thing :
What ethernet interface is suposed to be the "primary" ?
One of the lan, or one of the wan ?
Can it be changed later, changing the order by drag and drop ?, need to use changeip ?
Thank's
Eric

How do I set up an ethernet interface on MacBook Air - no ethernet option showing in network pane

I need to connect to internet via ethernet as no WiFi in my location. I have tried to add ethernet interface from network settings but no option for ethernet appears when in the network pane.
I have a MacBook Air running OSX 10.7.5
Any advice on how I can do this? Thanks

Have you plugged a USB to Ethernet adaptor in and connected it with an Ethernet lead to a router? After doing this you should see:

Ethernet interface eth0 missing

Similar Messages

Maybe you are looking for