Ethernet interface won't go up?

Hello!
I've been using my Arch-box as a router (among other things) for a while now.
It has 2 Ethernet interfaces (wan_eth0, lan_eth0) and 1 Wireless interface (lan_wifi0); One of the Ethernet interfaces connects to the internet, while the other can't seem to connect to anything at all.
The Wifi is excellent, but works as a bottleneck. I'm not super-experienced with Arch/Linux but I've used it (somewhat passively) for several years, but I haven't been able to figure out what's wrong with the interface despite several attempts. A recent update forced me to reconfigure the network settings (adding a bridge interface, lan_br0), which prompted me to try again, but I haven't gotten anywhere.
I use udev to change the interfaces' names, netctl to create the bridge interface, hostapd to host the Wifi AP, iptables is properly configured for NAT, dhcpd listens to the server's LAN IP (assigned to the bridge interface), and dhcpcd runs on the external interface.
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: lan_eth0: <NO-CARRIER,BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc pfifo_fast master lan_br0 state DOWN group default qlen 1000
link/ether 00:19:5b:86:9d:ef brd ff:ff:ff:ff:ff:ff
3: wan_eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether 00:13:d3:b8:17:09 brd ff:ff:ff:ff:ff:ff
inet xxx.xxx.xxx.xxx/24 brd xxx.xxx.xxx.255 scope global wan_eth0
valid_lft forever preferred_lft forever
inet6 xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/64 scope link
valid_lft forever preferred_lft forever
4: lan_wifi0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq master lan_br0 state UP group default qlen 1000
link/ether 00:18:39:18:4e:51 brd ff:ff:ff:ff:ff:ff
inet6 xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/64 scope link
valid_lft forever preferred_lft forever
5: lan_br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 00:18:39:18:4e:51 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.1/24 brd 192.168.0.255 scope global lan_br0
valid_lft forever preferred_lft forever
inet6 xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/64 scope link
valid_lft forever preferred_lft forever
$ lspci -vvnn
00:0a.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] [1106:3106] (rev 86)
Subsystem: D-Link System Inc DFE-530TX rev C [1186:1403]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32 (750ns min, 2000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 18
Region 0: I/O ports at d000 [size=256]
Region 1: Memory at f6038000 (32-bit, non-prefetchable) [size=256]
[virtual] Expansion ROM at 80000000 [disabled] [size=64K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: via-rhine
Kernel modules: via_rhine
The external interface (wan_eth0) uses the same kernel driver/module as lan_eth0 (the one that isn't working).
I have a working cable connecting lan_eth0 to one of my PCs.
Unfortunately I can't try the lan_eth0 device in another computer, nor connect it to another computer than it's already connected to.
Thanks for any help!

rebootl wrote:
I'm not entirely clear whether this used to work, something has changed and it doesn't work anymore or it never worked ?
I have a working cable connecting lan_eth0 to one of my PCs.
Usually you would have a switch or hub in between there (?). I'm not really up to date on this but I think, earlier when not using a switch/hub you would have needed a cross-over cable to do this. A few searches on google reveal that this may not be needed anymore. Depending on how old your network card is...
The wiki says "Note: If one of the two computers has a gigabit ethernet card, a crossover cable is not necessary and a regular ethernet cable should be enough".
(https://wiki.archlinux.org/index.php/Internet_sharing)
Also it seems that you can check using e.g. ethtool looking for Auto-negotiation.
1) The connection itself has never worked, but the cable is as good as new and should be working.
2) The Arch box (which has lan_eth0) is supposed to act as a hub (or a router specifically), though it only has two ethernet interfaces (lan_eth0 & wan_eth0) and one Wifi (lan_wifi0). The wifi works fine.
It seems I haven't been using a crossover cable, though. I read up on it a little and apparently if the colors of the pins on the ends of a cable are in the same order, they're "regular" aka "patch" cables. I have a few cables with differently ordered pins, but they're marked "patch cable", and either way I'm pretty sure they don't work.
Also, apparently if the network card has "Auto-MDIX", it doesn't matter what kind of cable you're using, which is probably what the wiki note refers to. I don't know how to check if my card has that, I'm going to google it now.
I'm not familiar with ethtool, but it appears I can't get much information about lan_eth0? I understand that much of the information would only be available when the interface is up, but shouldn't there be more than this?
$ ethtool -s lan_eth0 mdix on
setting MDI not supported
$ ethtool --help | grep -i show
ethtool -a|--show-pause DEVNAME Show pause options
ethtool -c|--show-coalesce DEVNAME Show coalesce options
ethtool -g|--show-ring DEVNAME Query RX/TX ring parameters
ethtool -k|--show-features|--show-offload DEVNAME Get state of protocol offload and other features
ethtool -i|--driver DEVNAME Show driver information
ethtool -p|--identify DEVNAME Show visible port identification (e.g. blinking)
ethtool -S|--statistics DEVNAME Show adapter statistics
ethtool -n|-u|--show-nfc|--show-ntuple DEVNAME Show Rx network flow classification options or rules
ethtool -T|--show-time-stamping DEVNAME Show time stamping capabilities
ethtool -x|--show-rxfh-indir DEVNAME Show Rx flow hash indirection
ethtool -P|--show-permaddr DEVNAME Show permanent hardware address
ethtool -l|--show-channels DEVNAME Query Channels
ethtool --show-priv-flags DEVNAME Query private flags
ethtool --show-eee DEVNAME Show EEE settings
ethtool -h|--help Show this help
ethtool --version Show version number
$ ethtool -a lan_eth0
Pause parameters for lan_eth0:
Cannot get device pause settings: Operation not supported
$ ethtool -c lan_eth0
Coalesce parameters for lan_eth0:
Cannot get device coalesce settings: Operation not supported
$ ethtool -g lan_eth0
Ring parameters for lan_eth0:
Cannot get device ring settings: Operation not supported
$ ethtool -k lan_eth0
Features for lan_eth0:
rx-checksumming: off [fixed]
tx-checksumming: off
tx-checksum-ipv4: off [fixed]
tx-checksum-ip-generic: off [fixed]
tx-checksum-ipv6: off [fixed]
tx-checksum-fcoe-crc: off [fixed]
tx-checksum-sctp: off [fixed]
scatter-gather: off
tx-scatter-gather: off [fixed]
tx-scatter-gather-fraglist: off [fixed]
tcp-segmentation-offload: off
tx-tcp-segmentation: off [fixed]
tx-tcp-ecn-segmentation: off [fixed]
tx-tcp6-segmentation: off [fixed]
udp-fragmentation-offload: off [fixed]
generic-segmentation-offload: off [requested on]
generic-receive-offload: on
large-receive-offload: off [fixed]
rx-vlan-offload: off [fixed]
tx-vlan-offload: off [fixed]
ntuple-filters: off [fixed]
receive-hashing: off [fixed]
highdma: off [fixed]
rx-vlan-filter: off [fixed]
vlan-challenged: off [fixed]
tx-lockless: off [fixed]
netns-local: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: off [fixed]
tx-ipip-segmentation: off [fixed]
tx-sit-segmentation: off [fixed]
tx-udp_tnl-segmentation: off [fixed]
tx-mpls-segmentation: off [fixed]
fcoe-mtu: off [fixed]
tx-nocache-copy: off
loopback: off [fixed]
rx-fcs: off [fixed]
rx-all: off [fixed]
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: off [fixed]
rx-vlan-stag-filter: off [fixed]
l2-fwd-offload: off [fixed]
$ ethtool -i lan_eth0
driver: via-rhine
version: 1.5.1
firmware-version:
bus-info: 0000:00:0a.0
supports-statistics: no
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
$ ethtool -p lan_eth0
Cannot identify NIC: Operation not supported
$ ethtool -S lan_eth0
no stats available
$ ethtool -n lan_eth0
Cannot get RX rings: Operation not supported
rxclass: Cannot get RX class rule count: Operation not supported
RX classification rule retrieval failed
$ ethtool -T lan_eth0
Time stamping parameters for lan_eth0:
Capabilities:
software-receive (SOF_TIMESTAMPING_RX_SOFTWARE)
software-system-clock (SOF_TIMESTAMPING_SOFTWARE)
PTP Hardware Clock: none
Hardware Transmit Timestamp Modes: none
Hardware Receive Filter Modes: none
$ ethtool -x lan_eth0
Cannot get RX ring count: Operation not supported
$ ethtool -P lan_eth0
Permanent address: 00:19:5b:86:9d:ef
$ ethtool -l lan_eth0
Channel parameters for lan_eth0:
Cannot get device channel parameters
: Operation not supported
$ ethtool --show-priv-flags lan_eth0
No private flags defined
$ ethtool --show-eee lan_eth0
Cannot get EEE settings: Operation not supported
$ ethtool lan_eth0
Settings for lan_eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Speed: 10Mb/s
Duplex: Half
Port: MII
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000000 (0)
Link detected: no
Not sure if any of the above helps at all, apart from how little information there is I don't notice anything wrong. Anyway it seems auto-negotiation is enabled (as it should?).
UPDATE:
According to this webpage my card does not have Auto-MDI, so I -must- use a crossover cable. I'll try it and see if I notice any difference.
Last edited by Noxic (2014-03-21 15:25:33)

Similar Messages

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

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

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)

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:

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.

Supplemental Ethernet interface on iMac G5

Hi,
Is there a way to ad another physical Ethernet interface to a iMac G5 PPC ? My goal is to plug it on both private and public networks. Its user can't vpn to my gateway and needs Timbuktu on it, the only solution is to set it up with a public adress.
Thanks for your help

well u can install one as its a fixed unit, but you could buy a usb ethernet port and plug that in

FieldPoint real-time controller or Ethernet interface

Good Afternoon,
The first feature listed on the FP-2000 product page is:
Stand-alone embedded real-time controller or Ethernet interface for PC-based distributed I/O.
Has anybody successfully implented a FP-2000 as an Ethernet interface for PC-based distributed I/O? In other words, have the FP-2000 act like a FP-1600?
There are some discussion forum threads that dance around the subject but I have not found one that really answers it.
Thanks,
Ed
Solved!
Go to Solution.

Hi edlad,
After playing around with a FP-2010 for a while, I do believe that you need to install LabVIEW Real-Time on the controller in order for it to work, even if you are technically not using it because you are not running a VI/executable on the controller. As far as your issue with installing LabVIEW 8.5.1 on a FP-2000, that is troubling because there should not be an issue doing this at all. In fact, I have personally been able to install LabVIEW 8.5.1 on many FP-2000s. For that issue, I would suggest reformatting the FP-2000 from MAX and try again.
ThinkG: Regarding your question about using a cFP-2220 to communicate with Lookout, I am not sure because Lookout support is handled by our Shanghai branch via email only. However, I do know that you can use that second ethernet port to communicate with another FieldPoint network module (cFP-180x) using the FieldPoint drivers. Here are a couple good KnowledgeBase articles regarding that configuration. I hope they are helpful.
http://digital.ni.com/public.nsf/allkb/F602F6F1B243282686257495007695BB?OpenDocument
http://digital.ni.com/public.nsf/allkb/67F94BB93BCE32CF86257367006B3659?OpenDocument
Thank you for choosing National Instruments.
Aaron Pena
National Instruments
Applications Engineer
http://www.ni.com/support

How to change the Ethernet Interface name in Solaris 10

I have to install Oracle 10G RAC on three nodes with different ethernet cards, but the ethernet interface name must be the same which is the precondition for Oracle RAC installation.
So I want to know how can I change the ethernet name in Solaris.
For example, the ethernet name in the OS is "ce0", how can i change the interface name "ce0" to "e1000g0".
bash-3.00# dladm show-dev
ce0 link: unknown speed: 1000 Mbps duplex: full
ce1 link: unknown speed: 100 Mbps duplex: half
ce2 link: unknown speed: 100 Mbps duplex: half
ce3 link: unknown speed: 100 Mbps duplex: half
ce4 link: unknown speed: 100 Mbps duplex: half
ce5 link: unknown speed: 0 Mbps duplex: unknown
Thanks in advance.

s-wilson wrote:
You can't. The ce or e1000g refers to the driver as well as the adapter itself. The only exception I am aware of is: the ipge and e1000g which both refer to the Intel Pro 1000.I'm pretty sure I've renamed a driver in the past (and all references to it in name_to_major, path_to_inst, driver_aliases, and minor_perm) and had it function just fine after 'plumb'ing it up. However I just tested this by trying to turn a 'pcn' driver into a 'foobar' driver on a vmware box. It looks like everything works except some internal bits of the driver continue to create one file with 'pcn' in the name instead of 'foobar'. And since this is Solaris 10, the /devices filesystem is dynamic and read-only. I can't seem to force the change.
So while this may be possible with some drivers (and maybe only on older versions of the OS), it doesn't seem to be generally possible for all drivers on Solaris 10.
Darren

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 create a virtual ethernet interface in arch ?

I have subscribed to a distant VPN service. My computer acts as a VPN client and creates a new interface tun0 each time the VPN is active.
I want to only route the ip traffic from Transmission through VPN
I tried to follow the tutorial from here (sorry it's in french) but this tutorial is for debian-based distribs.
Since the VPN may have a dynamic IP, this tutorial proposes to create a 2nd virtual ethernet interface with a fixed IP adress. iptable is then used to perform NAT translation between the IP of this 2nd virtual ethernet interface and tun0.
With debian-based distributions, the creation the this new virtual ethernet interface is managed by adding the following lines to the file /etc/network/interfaces :
# The secondary loopback network interface
auto lo:1
iface lo:1 inet static
address 192.168.0.1
netmask 255.255.255.255
I'm not sure how to perform this in arch. I read a lot about the ip command and I think that the solution may be something like that :
ip tuntap add dev lo1 mode tap
but I'm not sure and moreover, I don't know how to give a fixed IP adress (i.e. 192.168.0.1) to this new interface
Any help would be really appreciated.

It's just a wild guess, but maybe https://wiki.archlinux.org/index.php/Systemd-networkd would help?

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

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.

Automatically starting DHCP on second ethernet interface in Solaris 8?

Hello,
In my current setup, I have a Solaris 8 server with two ethernet interfaces - elxl0, which is connected to my internal network and has a static IP, and elxl1, which is connected to a cable modem and gets its address via DHCP.
When I reboot the machine, it brings both interfaces up, but does not start DHCP on elxl1 automatically. I have an empty /etc/hostname.elxl1, which I thought was supposed to tell the OS to use DHCP for that interface. I have to manually tell the interface to get an address using ifconfig auto-dhcp start.
Is there a way to tell the OS to use DHCP for elxl1 without disturbing elxl0? It would make things significantly more convenient for me, since now I have to manually start DHCP, and then reload my IP Filter NAT rules.
Any assistance you could provide would be greatly appreciated. Thanks!
- Brad Williams

I figured it out.
What you have to do is add a file, /etc/dhcp.<interface>, in order to make this work. In my example, the file would be "/etc/dhcp.elxl1".

Ethernet interface won't go up?

Similar Messages

Maybe you are looking for