Ethernet Interface en0 name not DNS name???

When I look in the server admin all of a sudden (we did just recently put the server outside of the firewall due to SIP issues) now my server no longer reflects the correct FQDN in the General Settings/Network tab. Instead it shows the generic ISP name. Any ideas?

It should work anyway but the server needs to go to root servers to look up all other domains.
To avoid that you can put in ISP DNS as forwarders to speed up lookups.
In the Leopard DNS GUI there is now an option to do so.
Forwarders offload lookups from your server to whichever DNS you can use as forwarder DNS.
To test if a DNS will work as a forwarder from your public IP (ISP DNS should "always" work):
host <IP or name you want to lookup - use something "remote" like www.apple.com> <DNS IP you want to test>
It's important to test a domain or IP that isn't part of the ISP range/domain or you might be fooled to think it works for all domains.

Similar Messages

Ethernet interface down when make entry in autopush file

Hi,
my kernel STREAMS module is working fine when i push it just above ethernet interface through ifconfig cmd, but when i make its entry in autopush file as: iprbo -1 0 simod
then during boot ethernet interface iprb0 is not getting up & even system is getting crashed?
how i can sort out this prob ?

Hi Prakash
Chech if the host name entry in maintained on DNS server. DNS server is responsible to resolve your host-name to IP setting.
refer this link - http://forums.techarena.in/server-dns/905529.htm
Regards
Mitesh Parekh

Vfc interface down until "shut/no shut" on Ethernet interface(s)

Hello, I'm hoping someone out there has had this problem and knows the solution, or can provide some insight as to whether the problem is with the CNA, Host OS, or Nexus. I've not yet posted anything to the Brocade discussion forums about this issue.
I have vfc interfaces that are not coming up naturally; the log states that it fails "waiting for flogi" (see 'google'). The only solution that I've found posted for that problem is to apply the QoS settings for FCoE. Those settings were already applied during the initial configuration of the switch, and I've since double and triple checked them. I've also gone through the Cisco Nexus 5000 Troubleshooting Guide, Troubleshooting FCoE Issues, and everything checks out except a couple of things:
1) The interfaces don't get past the FIP Solicitation stage: They show Triggered Event: [FCOE_MGR_VFC_EV_FIP_SOLICITATION] over and over again.
2) While the troubleshooting guide states that the FCoE vLAN should be STP forwarding on the underlying Ethernet interfaces, it is not. However, I have a working configuration elsewhere (with different make/model CNA hardware and Nexus software revisions) and the FCoE vLAN is not STP forwarding on those underlying Ethernet interfaces either.
The interesting part is that if I do a "shut" then "no shut" on the underlying Ethernet interfaces, after the hosts have completely booted, the vfc interfaces come up and successfully register in the flogi database. At that point everything is functional. If the hosts then reboot, the vfc interfaces fail to come up until I perform the "shut/no shut" on the underlying Ethernet interfaces.
One other noteworthy symptom is that during POST, when the CNA initializes, it displays the error message "Link initialization failed. Disabling BIOS."
Here is a configuration synopsis:
Cisco Nexus 5548UP [Ver. 5.1(3)N2(1)]
Brocade 1020 CNA [Rev. 3.2.1.0]
ESXi vSphere [Ver 5.1], [CNA Driver Rev. 3.2.1.0]
There are two vSANs; A-side and B-side. Each is bound to a unique and dedicated vLAN.
Po1 is the vPC peer-link. The FCoE vLANs are *not* allowed on it.
Po1011 is DB1's vPC port-channel. It is an 802.1q Trunk; the native vLAN (1) and the FCoE vLANs are allowed, among other Ethernet data vLANs.
Po1021 is DB1's vPC port-channel. It is an 802.1q Trunk; the native vLAN (1) and the FCoE vLANs are allowed, among other Ethernet data vLANs.
vfc1011 is DB1's Virtual FC interface. It is a Trunk (mode TF), allowing the A-side vSAN only. It is in the vSAN membership database.
vfc1021 is DB2's Virtual FC interface. It is a Trunk (mode TF), allowing the B-side vSAN only. It is in the vSAN membership database.
EDIT: The Port-Channels are LACP.
Thanks for your time.
Message was edited by: Michael Hertrick

I agree that the more distance you can put between the fabrics ever converging into one, the better off you are. You don't want faults on one SAN to interrupt and cause faults on your redundant SAN.
Nevertheless, the aforementioned configuration does not converge the two vSANs.
The host does not bridge between the two adapters, nor do the switches bridge between the two. Remember, even though you bind the vfc to the port-channel in the configuration, the vfc is really bound only to the Ethernet interface on the local switch and is not participating in the port-channel at all. There is no way, with that configuration as-is, for SAN A traffic to land on SAN B. A series of a few mis-configurations would be required for the SAN segmentation to be eroded.
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/configuration_guide_c07-543563.html
See sections "Configuration Parameters That Must Be Identical" and "Configuration Parameters That Should Be Identical"
Under "must" there is:
Enable or disable state per VLAN"
Under "should" there is:
Spanning Tree Protocol interface settings:
VLANs (Rapid Per-VLAN Spanning Tree Plus [PVST+])
Would you mind pointing out in the document you linked where Cisco recommends that the allowed vLANs on each side of the vPC should be different? I didn't exactly find that. What I did see was that they have vlan 101 and 102 allowed on both port-channel11 and port-channel12 in their example. vsan 101 is bound to vlan 101, vsan 102 is bound to vlan 102.
Kind Regards.

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 en0 does not exist

Hi,
I got a new mac book last week. It was able to connect via ethernet and suddendly the ethernet did not work anymore.
I'm writing this with my pc laptop, using the same cable modem, so it's not a cable/modem issue.
I checked all system preferences/network preferences and so on but it does not help.
In network port configurations, my ethernet is greyed out. I cannot make it active and I cannot create new ethernet port.
When I go to the terminal and run a ifconfig en0, I have "en0 does not exist" where as system profiler defines en0 as the built-in ethernet. (no mac address is shown though).
I used the apple hardware test at boot-up. Macaddress of the ethernet is 00:00:00:00:00. Is this normal ?
Any one have any idea ? Is my built-in ethernet broken ? Is it software issue or hardware ?
thanks,
Lionel

Things to try:
1. Go to Applications / Utilities / Disk Utility and do a Fix permissions. This often cures strange errors.
2. Go to the Control Panel and add a new user. Log in as the new user and try to connect. This may not help, but when I was having trouble with wireless, Apple tech support sugested it. (Didn't help me.)
3. It is a pain in the neck, but try doing an arhcive reinstall of OSX.
4. If you look in the Discussions for Macbook Ethernet port, you'll probably find some articles about blown ports. It sounds like the Macbook Ethernet port may be easier to fry than typical, or there may have been a bad batch of Macbooks.
5. If the Macbook is new, it is worth a shot calling Applecare. It would be cost free other than the time required. One would hope they'd be aware of any common problems with en0.
6. If you are within a reasonable distance of an Apple retail store, take your machine in and let the Genius Bar take a look.
Best wishes resolving the problem.
Bill

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

[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/

Hi i got a mac mini but when i connect it to my smartax mt882 modem via ethernet it says device not connected can anyone solve this issue it work fine with the usb connection but the ethernet is giving me problems plz help

hi i got a mac mini but when i connect it to my smartax mt882 modem via ethernet it says device not connected can anyone solve this issue it work fine with the usb connection but the ethernet is giving me problems plz help

Hello, give this a try...
Make a New Location, Using network locations in Mac OS X ...
http://support.apple.com/kb/HT2712
10.5, 10.6, 10.7 & 10.8…
System Preferences>Network, top of window>Locations>Edit Locations, little plus icon, give it a name.
10.5.x/10.6.x/10.7.x/10.8.x instructions...
System Preferences>Network, click on the little gear at the bottom next to the + & - icons, (unlock lock first if locked), choose Set Service Order.
The interface that connects to the Internet should be dragged to the top of the list.
For 10.5/10.6/10.7/10.8, System Preferences>Network, unlock the lock if need be, highlight the Interface you use to connect to Internet, click on the advanced button, click on the DNS tab, click on the little plus icon, then add these numbers...
208.67.222.222
208.67.220.220
(There may be better or faster DNS numbers in your area, but these should be a good test).
Click OK.

Service binded on only one ethernet interface

Hello everyone.
I am stuck with a little problem on Snow Leopard Server.
I want to open an auxiliary ssh server on the port 443, so I duplicated the /System/Library/LaunchDaemons/sshh.plist
I modified the label with a new name and set the socketName to https (443)
After loading and starting the services I have the following pb:
on 127.0.0.1:443 the server is working fine.
on my LAN interface (en1 or en2)10.0.0.1:443 the server is working fine
on my WAN interface (en0) 82.XX.XX.XX:443 the server cannot be reached...
the firewall is setted to let pass everything and I am sure of any NAT.
even if I try an "ssh 82.XXX.XXX.XXX -p 443" on the server itself, I have no answer.
Any idea?
Best Regards

Construct your MulticastSocket with not just a port number but with a SocketAddress as the bind address, containing the port number and a non-null InetAddress representing the local IP address to bind to, i.e. the network interface to listen at. If the InetAddress is null or absent the socket listens at all local network interfaces.
MulticastSocket.setNetworkInterface() controls which interface is used when sending.
If you are doing all this, so as to restrict multicasting, you also need to make sure to join and leave your multicast group(s) via the same network interface(s) as above.

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)

MDNS and multiple addresse on interface en0

Hello,
my Xserve has multiple IP addresses on interface en0. The output of ifconfig and dig is:
ifconfig
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 1.2.3.10 netmask 0xffffff00 broadcast 1.2.3.255
inet 1.2.3.11 netmask 0xffffff00 broadcast 1.2.3.255
inet 1.2.3.15 netmask 0xffffff00 broadcast 1.2.3.255
dig -p 5353 @xserve xserve.local.
;; QUESTION SECTION:
;xserve.local. IN A
;; ANSWER SECTION:
xserve.local. 10 IN A 1.2.3.10
xserve.local. 10 IN A 1.2.3.11
xserve.local. 10 IN A 1.2.3.15
I have a cupsd.conf on a Linux client. The client asks with BrowsePoll the cups daemon on
1.2.3.10 about printers. The client gets the printers, but with an incorrect address. The address
should be 1.2.3.10, but the client gets 1.2.3.15 and therefore an incomplete printer configuration!
On the Linux client the output of avahi-resolve is:
avahi-resolve -n xserve.local.
xserve.local 1.2.3.15
It should be 1.2.3.10!
How can I define for xserve.local the IP 1.2.3.10 ?
A hosts file exists in the configuration of the avahi-daemon. Is there any similary in the mDNS configuration
of MacOSX?
Regards.
P.

Hello,
the Xserve is fully intergrated in DNS, has a DNS Service running.
The IP addresses 1.2.3.xx are fictive. The Xserve has the IP 1.2.3.10,
name xserve.mydomain.de, and has NFS, Samba, Print and other services running.
A wiki server is running on 1.2.3.11:443, name wiki.mydomain.de.
A calendar server is running on 1.2.3.15:443, name ical.mydomain.de.
Therefore the interface has 3 IP addresses in the same subnet.
I am troubleshooting the CUPS problem and searched the reason of
the false information. I located it in mDNSResonder.
Another problem is the printing via DeviceURI
mdns://myprinter%20%40%20xserve.ipp.tcp.local.
or dnssd://myprinter%20%40%20xserve.ipp.tcp.local.
from MacOS-clients is very slow, using ipp://xserve:631/printers/myprinter
is faster.
I guess the reason is the mDNSResonder.
Regards.
P.

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)

My macbook air diagnostics say I am connected to the net [ethernet] but I am not. Am I missing something?

My macbook Air diagnostics say I am connected to the net [ethernet] but I am not. Am I missing something? Thanks

Change your router channel. Sometimes this is all you will have to do.
Power cycling the router. Read the router's user manual or contact their tech support for instructions.
System Preferences/Internet & Network/Network
Unlock the padlock
Locations: Automatic
Highlight Airport
Click the Assist Me button
In the popup window click the Diagnostic button.
System Preferences/Network- Unlock padlock. Highlight Airport. Network Name-select your name. Click on the Advanced button. Airport/Preferred Networks-delete all that is not your network.
Place a check mark next to "Remember networks this computer has joined." Click the OK button and lock the padlock. Restart your computer.
http://support.apple.com/kb/TS1920 Mac OS: How to release and renew a DHCP lease
No internet connection (wireless)
Check to see if an extra entry is present in the DNS Tab for your wireless connection (System Preferences/Network/Airport/Advanced/DNS).
Delete all extra entries that you find.
Place a check mark next to "Remember networks this computer has joined."
Other resources to check into:
How to diagnose and resolve Wi-Fi slow-downs
Pv6 troubleshooting
Mac OS X 10.6 Help: Solving problems with connecting to the Internet
What Affects Wireless Internet?
Solutions for connecting to the Internet, setting up a small network, and troubleshooting

`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"

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

Ethernet Interface en0 name not DNS name???

Similar Messages

Maybe you are looking for