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.

Similar Messages

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)

Nexus 5000 - Odd Ethernet interface behavior (link down inactive)

Hi Guys,
This would sound really trivial but it is very odd behavior.
- We have a server connected to a 2, Nexus 5000s (for resiliancy)
- When there is no config on the ethernet interfaces whatsoever, the ethernet interface is UP / UP, there is minimal amount of traffic on the link etc. E.g.
Ethernet1/16 is up
Hardware: 1000/10000 Ethernet, address: 000d.ece7.85d7 (bia 000d.ece7.85d7)
Description: shipley-p1.its RK14/A13
MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is access
full-duplex, 10 Gb/s, media type is 1/10g
Beacon is turned off
Input flow-control is off, output flow-control is off
Rate mode is dedicated
Switchport monitor is off
Last link flapped 00:00:07
Last clearing of "show interface" counters 05:42:32
30 seconds input rate 0 bits/sec, 0 packets/sec
30 seconds output rate 96 bits/sec, 0 packets/sec
Load-Interval #2: 5 minute (300 seconds)
    input rate 0 bps, 0 pps; output rate 8 bps, 0 pps
RX
    0 unicast packets 0 multicast packets 0 broadcast packets
    0 input packets 0 bytes
    0 jumbo packets 0 storm suppression packets
    0 runts 0 giants 0 CRC 0 no buffer
    0 input error 0 short frame 0 overrun   0 underrun 0 ignored
    0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop
    0 input with dribble 0 input discard
    0 Rx pause
TX
    0 unicast packets 163 multicast packets 0 broadcast packets
    163 output packets 15883 bytes
    0 jumbo packets
    0 output errors 0 collision 0 deferred 0 late collision
    0 lost carrier 0 no carrier 0 babble
    0 Tx pause
1 interface resets
- As soon as I configure the link to be an access port, the link goes down, flagging "inactivity" E.g.
sh int e1/16
Ethernet1/16 is down (inactive)
Hardware: 1000/10000 Ethernet, address: 000d.ece7.85d7 (bia 000d.ece7.85d7)
Description: shipley-p1.its RK14/A13
MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is access
auto-duplex, 10 Gb/s, media type is 1/10g
Beacon is turned off
Input flow-control is off, output flow-control is off
Rate mode is dedicated
Switchport monitor is off
Last link flapped 05:38:03
Last clearing of "show interface" counters 05:41:33
30 seconds input rate 0 bits/sec, 0 packets/sec
30 seconds output rate 0 bits/sec, 0 packets/sec
Load-Interval #2: 5 minute (300 seconds)
    input rate 0 bps, 0 pps; output rate 0 bps, 0 pps
RX
    0 unicast packets 0 multicast packets 0 broadcast packets
    0 input packets 0 bytes
    0 jumbo packets 0 storm suppression packets
    0 runts 0 giants 0 CRC 0 no buffer
    0 input error 0 short frame 0 overrun   0 underrun 0 ignored
    0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop
    0 input with dribble 0 input discard
    0 Rx pause
TX
    0 unicast packets 146 multicast packets 0 broadcast packets
    146 output packets 13083 bytes
    0 jumbo packets
    0 output errors 0 collision 0 deferred 0 late collision
    0 lost carrier 0 no carrier 0 babble
    0 Tx pause
0 interface resets
- This behavior is seen on both 5Ks
- I've tried using a different set of ports, changed SFPs, and fibre cabling to no avail
- I can't seem to understand this behavior?! In that, why would configuring the port cause the link to go down?
- If anyone has experience this before, or could shed some light on this behavior, it would be appreciated.
sh ver
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2010, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
Software
BIOS:      version 1.2.0
loader:    version N/A
kickstart: version 4.2(1)N1(1)
system:    version 4.2(1)N1(1)
power-seq: version v1.2
BIOS compile time:       06/19/08
kickstart image file is: bootflash:/n5000-uk9-kickstart.4.2.1.N1.1.bin
kickstart compile time: 4/29/2010 19:00:00 [04/30/2010 02:38:04]
system image file is:    bootflash:/n5000-uk9.4.2.1.N1.1.bin
system compile time:     4/29/2010 19:00:00 [04/30/2010 03:51:47]
thanks
Sheldon

I had identical issue
Two interfaces on two different FEXes were INACTIVE. I have two Nexus 5596 in vPC and A/A FEXes.
I also use config-sync feature.
Very same configuration was applied to other ports on other FEXes and they were working with no problems.
interface Ethernet119/1/1
inherit port-profile PP-Exchange2003
I checked VLAN status associated with this profile and it was active (of course it was, other ports were ok).
I solved it by removing port profile from this port and re-applied it... voila, port changed state to up!
Very very strange.

Ethernet interface disappears after waking up from sleep

Hi guys,
I've been trying to debug a networking problem without any luck and I think it's about time I ask the forum for help.
My ethernet interface no longer works after I wake up my computer from sleep. I have no idea why.
Before sleep:
# ls /sys/class/net
lo wlp2s0 enp3s0f2
After waking up from sleep,
ls /sys/class/net
lo wlp2s0
Here are the list of services I have running.
UNIT LOAD ACTIVE SUB DESCRIPTION
dbus.service loaded active running D-Bus System Message Bus
[email protected] loaded failed failed dhcpcd on enp3s0f2
[email protected] loaded active running Getty on tty1
[email protected] loaded active running Daemon which acts upon network cable inse
kmod-static-nodes.service loaded active exited Create list of required static device nod
[email protected]\x2dSecure.service loaded active exited Networking for netctl profile wlp2s0-Wolf
polkit.service loaded active running Authorization Manager
systemd-backlight@acpi_video0.service loaded active exited Load/Save Screen Backlight Brightness of
systemd-fsck@...\x2d38bc68d942fc.service loaded active exited File System Check on /dev/disk/by-uuid/1c
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-random-seed.service loaded active exited Load/Save Random Seed
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-tmpfiles-setup-dev.service loaded active exited Create static device nodes in /dev
systemd-tmpfiles-setup.service loaded active exited Recreate Volatile Files and Directories
systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-update-utmp.service loaded active exited Update UTMP about System Reboot/Shutdown
systemd-user-sessions.service loaded active exited Permit User Sessions
systemd-vconsole-setup.service loaded active exited Setup Virtual Console
upower.service loaded active running Daemon for power management
[email protected] loaded active running User Manager for 1000
Furthermore, plugging in the ethernet cord after the computer has started doesn't connect to the internet, even when I have the ifplugd service running. I am forced to run:
sudo ip link set enp3s0f2 up
sudo dhcpcd enp3s0f2
However, I can't run these commands after the laptop wakes up from sleep since it no longer sees the ethernet interface.
I am thoroughly confused. Please help me.

It seems to be fixed after the kernel update. On an related note, I've switched from using dhcpcd to netctl. I've enabled netctl to automatically connect to the network using:
# systemctl enable [email protected]
# systemctl enable [email protected]
So when I check for the status of the ethernet profile, I get told that's it's inactive.
#netctl status ethernet-dhcp
netctl@ethernet\x2ddhcp.service - Networking for netctl profile ethernet-dhcp
Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
Active: inactive (dead)
Docs: man:netctl.profile(5)
But I turned off the wireless, so I must be connected to the ethernet, So how do I know which profile I'm connected to?

How to set/change ip-address on ethernet interface

I have an IP address set on my wireless interface (with Internet access - no problem here), but I want to use my Ethernet interface to connect to a NAS device, on a "private/hidden" network - different network (10.0.1.xx)
What is the best way to do this?

Look in the printer's user manual for instructions on using TCP/IP (Ethernet.) The printer will have to connect to your network via an Ethernet port. If I remember correctly those old printers only have an AppleTalk serial port, so you will need an adaptor. They were called PhoneNet adaptors. I have no idea where you might find one today. They have a serial port connection on one end and an Ethernet connection on the other.
Unfortunately, I don't know that the printer will work unless you can turn on AppleTalk, and SL no longer supports it. If that's the case then you need a different type of adaptor - one that actively converts from AppleTalk to Ethernet. They were once made by Asante and Farallon, and they sold for around $100. But they are no longer made.

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

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û...

Ipv6 and ethernet interface

I started using a router that supports IPv6. The Mac automatically recognizes this and assigns an IPV6 address. The problem is, that once this happens there seems to be no way to disable the ethernet interface. (I wanted to switch to wireless only) I have turned IPV4 'OFF' but there is no "OFF" for the IPV6 configuration. I had to reboot and connect only to IPV4 in order to clear this condition..
Mac OS 10.10.2

You can try disabling IPv6 on the Ethernet interface by using Terminal.app the command would be something like
networksetup -setv6off Ethernet
If you have a different type of Ethernet interface to the built-in one you may need to use a slightly different name, you can check the name by doing
networksetup -listallnetworkservices
Another different approach would be to simply completely disable the Ethernet interface, the equivalent of turning it off. This is done in System Preferences -> Network and then after selecting the Ethernet interface go to the the bottom left corner Cog Wheel (Gear) and select Make Service Inactive. You may need to unlock the padlock first.

[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)?

X86 diskless client's Ethernet interfaces not plumbed/configured

Hi,
My client's extra (non-primary) Ethernet interfaces aren't being configured even though I put entries for them in the client's sysidcfg file. Could someone please tell me if this indicates a problem in the sysidcfg file or something more insidious?
Thanks,
Dave

Hi,
It turns out that my sysidcfg file isn't being used by the client at all. That explains some things I'm seeing, but I'm not sure how to get the file to be used by the client. An entry is in both the bootparams file and the SsysidCF DHCP macro. I tried a sys-unconfig on the diskless client, but it turns out that it can't be used on a diskless client.
Something more fundamental is amiss...
Thanks,
Dave

Network Interface problems on Mountain Lion Server

My Mac mini server has been migrated from 10.6.8 Server to 10.8.3 with Server 2.2.1.
I am seeing quite a bit of problems now that I have been running for a day. The most important one is that CRAM MD5 Challenge-Response authentication became very flaky after a day. What I found out is that the password server was completely overwhelmed by 'network transitions':
Apr 6 2013 17:51:22 844743us    A network transition was received.
Apr 6 2013 17:51:32 847278us    Initializing TCP ...
Apr 6 2013 17:51:32 847395us    Updating interface list due to a network transition.
Apr 6 2013 17:51:51 516341us    A network transition was received.
Apr 6 2013 17:51:56 426628us    A network transition was received.
Apr 6 2013 17:51:57 959249us    A network transition was received.
Apr 6 2013 17:52:07 961503us    Initializing TCP ...
Apr 6 2013 17:52:07 961583us    Updating interface list due to a network transition.
Apr 6 2013 17:52:09 265791us    A network transition was received.
Apr 6 2013 17:52:10 820056us    A network transition was received.
Apr 6 2013 17:52:16 789386us    Initializing TCP ...
Apr 6 2013 17:52:16 789623us    Updating interface list due to a network transition.
Apr 6 2013 17:52:17 455413us    A network transition was received.
Apr 6 2013 17:52:20 914352us    A network transition was received.
Apr 6 2013 17:52:26 653641us    Initializing TCP ...
Apr 6 2013 17:52:26 653702us    Updating interface list due to a network transition.
Apr 6 2013 17:52:27 581163us    A network transition was received.
Apr 6 2013 17:52:37 583599us    Initializing TCP ...
Apr 6 2013 17:52:37 583713us    Updating interface list due to a network transition.
Apr 6 2013 17:52:43 296938us    A network transition was received.
Apr 6 2013 17:52:53 299257us    Initializing TCP ...
Apr 6 2013 17:52:53 299338us    Updating interface list due to a network transition.
Apr 6 2013 17:52:55 963244us    A network transition was received.
Apr 6 2013 17:52:59 480000us    A network transition was received.
Apr 6 2013 17:53:09 482429us    Initializing TCP ...
Apr 6 2013 17:53:09 482536us    Updating interface list due to a network transition.
Apr 6 2013 17:53:11 415949us    A network transition was received.
Apr 6 2013 17:53:13 9951us    A network transition was received.
Apr 6 2013 17:53:23 12241us    Initializing TCP ...
Apr 6 2013 17:53:23 12348us    Updating interface list due to a network transition.
Apr 6 2013 17:54:55 364487us    A network transition was received.
Apr 6 2013 17:55:05 372730us    Initializing TCP ...
Apr 6 2013 17:55:05 372869us    Updating interface list due to a network transition.
I could see this too when in System Preferences, Network, that it was constantly renewing the lease of DHCP on the Ethernet interface. (The server gets its IP via DHCP from the router). This has worked well for years. I was even unable to edit a manual setting, until I disconnected the ethernet cable, because trying to edit the manual ip address was interrupted by the system changing. I have now set up a manual entry and the system is a lot more workable. The router has never given these problems and it even does not now give these problems on the client machines. Somehow, I suspect the server itself to be the culprit in that it tries to renew the lease constantly itself (lease time is 1440 minutes).
After some researching, I may have found the cuplrit. My Network settings have a Wifi device which is unconnected to a network. That was no problem previously. but I see a lot of configd entries i nthe logs:
4/6/13 5:11:55.204 PM configd[24]:
com.apple.message.domain: com.apple.wifi.timeout.xpc
com.apple.message.signature: Success
com.apple.message.signature2: SC_CHANGED_EVENT
com.apple.message.result: pass
com.apple.message.value: 456.000000
com.apple.message.summarize: YES
4/6/13 5:12:01.391 PM configd[24]:
com.apple.message.domain: com.apple.wifi.timeout.xpc
com.apple.message.signature: Success
com.apple.message.signature2: SC_CHANGED_EVENT
com.apple.message.result: pass
com.apple.message.value: 4.000000
com.apple.message.summarize: YES
4/6/13 5:14:10.560 PM configd[24]:
com.apple.message.domain: com.apple.wifi.timeout.xpc
com.apple.message.signature: Success
com.apple.message.signature2: SC_CHANGED_EVENT
com.apple.message.result: pass
com.apple.message.value: 51.000000
com.apple.message.summarize: YES
4/6/13 5:15:08.251 PM configd[24]:
com.apple.message.domain: com.apple.wifi.timeout.xpc
com.apple.message.signature: Success
com.apple.message.signature2: SC_CHANGED_EVENT
com.apple.message.result: pass
com.apple.message.value: 57.000000
com.apple.message.summarize: YES
4/6/13 5:15:35.634 PM configd[24]:
com.apple.message.domain: com.apple.wifi.timeout.xpc
com.apple.message.signature: Success
com.apple.message.signature2: SC_CHANGED_EVENT
com.apple.message.result: pass
com.apple.message.value: 1.000000
com.apple.message.summarize: YES
I have set the network setting to manual, this seems to stabilize matters. I'm now going to test what happens if I go back to DHCP, but without the unconfigured devices

Back to DHCP for 20 minutes now. No more transitions and the system is stable. DHCP was not so much the problem, its seems, but the unconfigured WiFi interface was.
Hmm, if OS X Server tries to be smart about signals like a network change (I can understand that Apple sees that as a good thing), I'd better have a stable network setup. So, apart from deleting all the unused interfaces, I'm sticking to a manual IP for my server. One source less of instability problems.

Xantrex PS ethernet interface and VXI-11 compliance

I am trying to find if once can use VISA (or better just use NI's LV GPIB PnP driver and change the interface to ethernet from GPIB) to talk to the XFR over ethernet. I am trying to buy their instrument with their Ethernet Interface Option but I am not sure about how well their VX-11 protocol is. The communication is going to be pretty simple and I wanted to know if anyone has ever communicated with a Xantrex PS over ethernet using VISA. They have an option of plugging an ethernet or GPIB interface to their instruments and I have attached the ethernet interface information.
Instrument,
http://www.xantrex.com/web/id/102/docserve.asp
NI PnP LV GPIB driver,
http://sine.ni.com/apps/we/niid_web_display.download_page?p_id_guid=E3B19B3E93D0659CE034080020E74861
Attachments:
Xantrex ethernet brochure.pdf ‏513 KB

The ethernet interface that Xantrex has for it's instruments is not VX-11 compliant. But I am able to test it using a VISA TCP/IP resource "TCPIP::10.15.117.167::771:OCKET" but not communicate.
I know that the Xantrex PS is VISA compliant for GPIB and Serial. Xantrex gets it's ethernet interfaces from , bb-elec, http://www.bb-elec.com/Subcategory.asp?Subcategoryid=668, Digi One Family Single-Port Serial to Ethernet Connectivity I believe. What the Digi s/w does is that it creates a virtual/fake COM/serial port that points to the ethernet connection. The problem is it probably does some translation between COM to Ethernet port. I need to know what it does so I can do the same in VISA maybe, to make it work.
I need your help because we are using the RT platform; on windows referencing this virtual COM port works fine but I am not sure what settings their s/w does to make it work under windows. I need to do the same on RT.
Has anybody come across this before. I appreciate your help.

Ethernet interface input queue 81/80 (size/max)

Hello,
Does anyone had the problem that the Gigabit interface of a C1140-K9W7 (or C1135)
sometimes "hangs" due to queue problems (from what I understood it was queue problems)?
I've got this AP, C1140-K9W7 with IOS 12.4(21a)JA1 and noticed it was not processing
any input packets at the Gigabit interface, the drop count was 0 but strangely the input queue
information was that it had size 81 and max 80... looks to me that the queue processing
code hanged somewhere...
The interface output is OK however (the AP is sending arp requests..) .
I've done some search but was not able to find any information about it, also followed the
steps in [1] to try troubleshoot what was causing that, no success. The IP traffic listing
shows that the interface is receiving packets but they aren't being processed and "aren't"
droped also (at least the drop count is 0).
If I reboot the AP it does work OK yes... I can still access the console (via serial) and it
still is at that state in case there's any suggestion of procedure.
Thanks for your time.
Jean Mousinho
[1] http://www.cisco.com/en/US/products/hw/routers/ps133/products_tech_note09186a0080094791.shtml

It looks like this could be related:
CSCtf27580 Ethernet interface input queue wedge from broadcast/uniGRE traffic
Is there any GRE traffic going through this AP?
The workarounds are:
Reboot APs to bring APs back up for time being.
OR
go back to 6.0.188.0 code on WLC.
OR
Route GRE traffic away from AP's.
It appears that it definitely exists in your code:
12.4(21a)JHA 12.4(21a)JA01 006.000(196.000)

MacBook Ethernet Connectivity Problem

Hi everyone:
Just until two weeks ago I was able to plug the ethernet cable into my MacBook in a conference room where I work. Since then it has not worked; the MacBook does not recognise that the cable is plugged in.
An IBM ThinkPad has no problems connecting to the same ethernet cable.-
When I take the cable and plug it directly into the Linksys 48 Port Gigabit Switch that is two floors below the conference room I have no problem. It seems that somehow the distance from the switch makes a difference to the MacBook, even though there was no problem just two weeks ago.
Does anyone know how to resolve this issue? Is it related to a recent update?
Thank you very much for your help.

system updates and installation of software as admin can do bad things to network configurations at time.
Try deleting all the ethernet interfaces specified in System Preferences/Network/ left panel and creating a new one (be sure to make a note of the correct ethernet configuration).
Also, delete Network "Locations" you are not using (again in System Preferences/Network).
Also, you can run this from the command line to get an idea of what configuration is active and network state you have:
ifconfig
Luc P. Beaudoin

`netctl` "randomly" started failing with ethernet interface.

I use netctl with the netctl-ifpluged service to start put up the ethernet. It stopped working, so I turned off `ifpluged` and tried manually starting the netctl profile. Doesn't work.
I get this output from `s systemctl status [email protected]`
● [email protected] - Networking for netctl profile wired
Loaded: loaded (/usr/lib/systemd/system/[email protected]; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2015-01-18 00:46:45 CST; 6min ago
Docs: man:netctl.profile(5)
Process: 7383 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
Main PID: 7383 (code=exited, status=1/FAILURE)
Jan 18 00:46:45 folio network[7383]: Starting network profile 'wired'...
Jan 18 00:46:45 folio network[7383]: The interface of network profile 'wired' is already up
Jan 18 00:46:45 folio systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE
Jan 18 00:46:45 folio systemd[1]: Failed to start Networking for netctl profile wired.
Jan 18 00:46:45 folio systemd[1]: Unit [email protected] entered failed state.
Jan 18 00:46:45 folio systemd[1]: [email protected] failed.
I don't have a clue what it means, except that my stuff failed. netctl does work with with my wireless interface, and dhcpcd works on the ethernet interface. It's just the combination of ethernet and netctl
here is a copy of my "wired" profile:
Description='A basic dhcp ethernet connection'
Interface=eno1
Connection=ethernet
IP=dhcp
On a presumably unrelated note, udev "randomly" changed the name of my *wireless* interface on a kernel upgrade a few days before this problem first occurred. The ethernet interface seems to have the same name. Probably not related, but I don't know the deep magic, and I thought that was also weird and network-related, so I figured I'd mention it.

ninjaaron wrote:Jan 18 00:46:45 folio network[7383]: The interface of network profile 'wired' is already up
Try running this first:
# ip l set <ethernet interface name> down
And then start the profile again.
https://wiki.archlinux.org/index.php/Ne … ice_failed
Have you tried just using dhcpcd.service to bring the ethernet connection up?
This works for me -- genuine "plug & play"

Ethernet interface problems...

Similar Messages

Maybe you are looking for