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.

Similar Messages

How can I put wireless and ethernet interfaces together?

I have a 877w router, and I'm trying to configure a wireless network.
I have an RFC1483 bridged ADSL, so I have ATM0.1 in a bridge group, and I then defined a BVI1 interface.
However, after configuring the wireless interface, I noticed that my laptop gets the IP address from the provider, as if wireless had precedence over the BVI interface. Putting the Dot11 interface in a separate bridge under VLAN1 doesn't seem to help either. I tried to put everything in the same bridge, but fast ethernet interfaces don't support bridging (how does the BVI work then, I wonder).
What should I do? Should I use two separate VLANs? I wouldn't like to do that. Any help appreciated. Thank you

Hey, thank you, that did it.
So I should have followed more the article. I guess I just don't understand how BVI works. From the article I thought that the BVIs were on the same level, that is, all of them right behind the ATM interface. I was also thinking that one BVI could bridge more VLANs. Now my next mission is to understand why I was wrong on both points.
Guys, thank you for the help. Now I'll try to undertand better what I just did :-)

EIGRP IPv6 and VLAN interfaces

We've found that we have to set static link local IPs when two routers might peer over multiple VLAN interfaces.
The issue is that the routers, 6500s with sup720s, utilize the same autoconfig'd link local address on each VLAN interface.   EIGRP IPv6 refuses to peer with the other router on multple VLANs when the link local are the same.
Anyone else encounter this?   Did we miss a config option that would force unique link locals on different VLANs interfaces?
Because of this issue, we've made it our best practice to configure static link local for all inter-router transits.

HI Gary,
I had a setup with SU720 on 2 7600s and I am able to enable the neighborship without any issues. I didnt configure static link local as below,
Ryanair#show ipv6 int vlan 500 | inc FE
IPv6 is enabled, link-local address is FE80::21C:B0FF:FEB5:6D00
Ryanair#sho ipv6 int vlan 501 | inc FE
IPv6 is enabled, link-local address is FE80::21C:B0FF:FEB5:6D00
Ryanair#show ipv6 eigrp nei
EIGRP-IPv6 neighbors for process 100
H   Address                 Interface       Hold Uptime   SRTT   RTO Q Seq
                                            (sec)         (ms)       Cnt Num
1   Link-local address:     Vl501             11 00:15:51 816 4896 0 13
    FE80::222:55FF:FE17:25C0
0   Link-local address:     Vl500             11 00:17:14    1   200 0 12
    FE80::222:55FF:FE17:25C0
Ryanair#
Can you let us know the version on oth the devices?.
Regards,
Nagendra

Difference between serial & ethernet interface.

Hi every one,
i have some doubts in basic stuffs.
Q1: What are the differences between serial interface and ethernet interfaces.
Q2: Can we use ethernet interfaces to terminate WAN connectivity just like serial.Why always we are using serial interfaces to connect the WAN.
Please help me out by answering these questions.
!!!!THANKS IN ADVANCE!!!!!

Hi There,
   Good explanation by Navin.
   On top of that, Serials are by nature flexible and it can be comfortably devided like per customer or provider needs from T1 or E1 connection.
   So the Bandwidth allowed to have physical pipe can be clearly configured and adjusted because of TDM structure each T1 or E1 is multiples of 64 kbps slots ( example :- 64 x 32 fpr E1 which 2048 Kbps or 2 Mb circuit) same follow for T1. This is good to have exactly what we run when designing Layer 3 Routing, so Routing protocols can take Routing decisions based on Bandwidth provisioned automatically or adjust with Policy based Routing.
   When it comes to FastEthernet the original build was for LAN connectivity. Of course we can use for MAN or WAN because of multilayer aware of transmissions capability is already rocking in Market. Because of Switching and Routing enhancements ( merge ) and many devices are aware of Layer 2 to 7 traffic patterns in many vendors. So it is difficult to clearly define the scope for these two types these days.
   Hope you got some clarification !
   Happy Reading

Need help for HDMI, USD and Ethernet example SoC for VC707

I'm developin an SoC with HDMI, USB and Ethernet interfaces.
In this USB and Ethernet interfaces are not working.
Can i get any example SoC's for above mentiones IPS.

bump ... nobody has anything helpful to post ?
Am I trying to do something that is not possible with the open source driver ? start a game in wine 32bit?
Or maybe the problem is in one of the libraries ?
I did mess around with the catalyst before, but the 2d was so bad that I decided not to even try the 3D watching a movie was impossible at a decent fps O.o
And I do believe that I removed all and re-installed Open Source libraries + drivers properly. Is there a definitive way to check ?

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)

Ethernet and Airport Interfaces Reversed

I created an image of the new Mac Book Pro(Mid 2010) and slapped it on the new Mac Mini(Mid 2010) and everything worked fine except one thing. I used the DVD that came with the Mac Book Pro(Mid 2010) to create the Master Image.
Under Network Preferences, the Ethernet Interface is displaying the Airport status window(i.e, "Turn Airport On/Off" button is in there). And the Airport Interface is displaying the Ethernet stats.
Any ideas what could be causing this?
Message was edited by: jjpotter

I had the same problem (reversed Ethernet and Airport interfaces) on my 13" MacBook Air after plugging in my Thunderbolt Display. The solution was to go to Network in System Preferences, click the minus symbol under interfaces to delete both of them, click plus to add each one back, then click Apply. Now everything is as it should be.

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.

Ip wccp redirection direction at ethernet and serial interface.

hi all.
commonly, we use 'ip wccp 62 redirect in' at serial interface to grap packet for sending cisco waas.
but some document is mentioned that 'ip wccp 62 redirect out' ethernet interface facing data center side.
I guess, there is same meaning, I think that It's better to apply 'ip wccp 62 redirect in' at serial interface due to router performance. Right?
Can you explain clarify for me?
Thank you.

You are correct redirect in is less cpu intensive as compared to redirect out
WCCP redirection can be configured to occur as packets enter a router or switch interface (inbound, or ingress, redirection) or as they are beginning to leave a router or switch interface (outbound, or egress, redirection).
* Inbound redirection - the WCCP process inspects traffic to find packets that should be optimized before the packets enter the router or switch forwarding/routing selection process. Inbound redirection is less CPU intensive than outbound redirection (when using process or other SW based switching).
* Outbound redirection - the WCCP process inspects traffic to find packets that should be optimized as the packets are ready to leave a router or switch interface, after the packet has gone through the router or switch forwarding/routing selecting process. Outbound redirection is more CPU intensive than inbound redirection.
Thanks
-Smita

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

The difference between IEEE802.1Q Native VLAN sub-interface and Physical interface?

Hello
I think the following topologies are supported for Cisco Routers
And the Physical interface also can be using as Native VLAN interface right?
Topology 1.
R1 Gi0.1 ------ IEEE802.1Q Tunneling L2SW ------ Gi0 R2
R1 - configuration
interface GigabitEthernet0.1
encapsulation dot1Q 1 native
ip address 10.0.0.1 255.255.255.0
Topology 2.
R1 Gi0 ------ IEEE802.1Q Tunneling L2SW ------ Gi0 R2
interface GigabitEthernet0
ip address 10.0.0.1 255.255.255.0
And is it ok to use the physical interface and sub-interface with dynamic routing such as EIGRP or OSPF etc?
R1 Gi 0 ---- Point to Multipoint EIGRP or OSPF ---- Gi0 R2 / R3
Gi 0.20--- Point to Point EIGRP or OSPF --- Gi0.10 R4 (same VLAN-ID)
R1 - configuration
interface GigabitEthernet0
ip address 10.0.0.1 255.255.255.0
interface GigabitEthernet8.20
encapsulation dot1Q 20
ip address 20.0.0.1 255.255.255.0
Any information is very appreciated. but if there is any CCO document please let me know.
Thank you very much and regards,
Masanobu Hiyoshi

Hello,
The diagram is helpful.
If I am getting you correctly, you have three routers interconnected by a switch, and you want them to operate in a hub-and-spoke fashion even though the switch is capable of allowing direct communication between any of these routers.
Your first scenario is concerned with all three routers being in the same VLAN, and by using neighbor commands, you force these routers to establish targeted EIGRP adjacencies R1-R2 and R1-R3, with R1 being the hub.
Your second scenario is concerned with creating one VLAN per spoke, having subinterfaces for each spoke VLAN created on R1 as the router, and putting each spoke just in its own VLAN.
Your scenarios are not really concerned with the concept of native VLAN or the way it is configured, to be honest. Whether you use a native VLAN in either of your scenarios, or whether you configure the native VLAN on a subinterface or on the physical interface makes no difference. There is simply no difference to using or not using a native VLAN in any of your scenarios, and there is no difference to the native VLAN configuration being placed on a physical interface or a subinterface. It's as plain as that. Both your scenarios will work.
My personal opinion, though, is that forcing routers on a broadcast multi-access segment such as Ethernet to operate in a hub-and-spoke fashion is somewhat artificial. Why would you want to do this? Both scenarios have drawbacks: in the first scenario, you need to add a neighbor statement for each spoke to the hub, limiting the scalability. In the second scenario, you waste VLANs and IP subnets if there are many spokes. The primary question is, though: why would you want an Ethernet segment to operate as a hub-and-spoke network? Sure, these things are done but they are motivated by specific needs so I would like to know if you have any.
Even if you needed your network to operate in a hub-and-spoke mode, there are more efficient means of achieving that: Cisco switches support so-called protected ports that are prevented from talking to each other. By configuring the switch ports to spokes as protected, you will prevent the spokes from seeing each other. You would not need, then, to configure static neighbors in EIGRP, or to waste VLANs for individual spokes. What you would need to do would be deactivating the split horizon on R1's interface, and using the ip next-hop-self eigrp command on R1 to tweak the next hop information to point to R1 so that the spokes do not attempt to route packets to each other directly but rather route them over R1.
I do not believe I have seen any special CCO documents regarding the use of physical interfaces or subinterfaces for native VLAN or for your scenarios.
Best regards,
Peter

Setup more than one ethernet interface

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

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

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

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

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

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.

Ipv6 and ethernet interface

Similar Messages

Maybe you are looking for