Duplicate Ethernet Interface - Connection Issues

Hi,
   Recently, after rebooting, I had a continuous stream of error messages on my login terminal, and I couldn't connect to the network.
[ 669.236979] genirq: Flags mismatch irq 0. 00000080 (eth0) vs. 00015a20 (timer)
[ 670.235840] genirq: Flags mismatch irq 0. 00000080 (eth0) vs. 00015a20 (timer)
[ 671.234701] genirq: Flags mismatch irq 0. 00000080 (eth0) vs. 00015a20 (timer)
# ping www.google.com
ping: unknown host www.google.com
# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether de:34:07:d0:d9:29 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000 ## Duplicate interfaces?
link/ether 00:24:1d:a2:f7:c5 brd ff:ff:ff:ff:ff:ff
# ifconfig eth0 up
SIOCSIFFLAGS: Device or resource busy
# ifconfig eth1 up
# dhcpcd eth1
dhcpcd[732]: version 5.6.4 starting
dhcpcd[732]: eth1: sending IPv6 Router Solicitation
dhcpcd[732]: eth1: rebinding lease of 192.168.1.3
dhcpcd[732]: eth1: acknowledged 192.168.1.3 from 192.168.1.1
dhcpcd[732]: eth1: checking for 192.168.1.3
dhcpcd[732]: eth1: sending IPv6 Router Solicitation
dhcpcd[732]: eth1: leased 192.168.1.3 for 2592000 seconds
dhcpcd[732]: forked to background, child pid 780
# ping www.google.com
64 bytes from bom03s02-in-f18.1e100.net (74.125.236.146): icmp_seq=1 ttl=56 time=11.6 ms
After manually configuring eth1, and assigning it an IP, everything works normally. Another bunch of curious messages at boot up were these:
[ 0.271521] pci 0000:01:07.0: BAR 1: error updating (0xfde00000 != 0x000000)
[ 0.271553] pci 0000:01:07.0: BAR 3: error updating (0xfdf10008 != 0x000008)
[ 0.271583] pci 0000:01:07.0: BAR 2: error updating (0x00c001 != 0x00cc09)
What would be a clean way to fix this?
Thanks in advance!

Thanks for the replies.
In an attempt to establish whether it was the computer or the router I plugged in an old speedtouch 510 router which I had lying around - this worked first time, so I guess it's the netgear that is the issue and I will need to reset it and re-enter all the details, unless anyone knows of a quicker way...?

Similar Messages

  • Audio Interface Connection Issue

         I have recently purchased Native-Instruments' Komplete Audio 6 for production use in Logic Pro 9 and I have been experiencing a connection issue. The USB connection light on the interface itself blinks whenever it is plugged in and my Mac Book Pro Retina cannot detect the device whatsoever. This means, I believe,  that it is receiving power. I have been able to connect the two devices for very short periods of time (maybe 5 minutes) before it disconnects and returns to a blinking pattern sending an error message that the interface returned -2. (Whatever that means)
         I have contacted Native-Instruments directly about the issue and they only respond with "update your firmware to the latest version." This would be fine except that the interface has to be connected to run a firmware update. (If that even is the problem) I have also deleted and reinstalled the driver/firmware multiple times.
         I have gone through and completed all of the NI's websites troubleshooting guide to no avail and am becoming desperate for answers.
         Is there any input that could help me with this endeavor, or perhaps a troubleshoot that I have overlooked?
    thanks.

    If you are connecting the Audio 6 (or any other USB2 Audio/Midi device for that matter) via USB to a USB3 port on your Mac.. (which I am assuming you are doing..) try using a Powered USB2 hub.. and connect the Live 6 to that and then connect the Hub to the USB3 port... Make sure you don't connect anything else to the hub.. so the Live 6 gets the max power from the hub...
    Using a powered Hub with a USB2 device to connect to a USB3 port on a Mac or PC.. often helps out issues that are caused by the lower power that a USB3 port provides...
    Its not a certain fix but often it works...
    if it does work, you can then update the firmware which may alleviate the need for the powered hub.

  • Mac Mini Ethernet SSL connection issues

    Hi,
    Up until recently I have been using my Late 2012 Mac mini with a WiFi connection. Recently though I've had reason to switch to a Gigabit Ethernet connection (short version, moved from UK to Canada, living with in-laws and they have a crappy wireless router that can't hold a stable connection for more than a few hours).
    However, I'm getting a really odd Ethernet network issue where my mac will "corrupt" SSL connections. This normally manifests itself in web pages not fully downloading, images becoming corrupted, or errors when downloading files. The last one is particularly hurting as I have been doing some heavy downloading of DMG files and other installers, all of which are a 100% guaranteed fail with DMG files reporting as being corrupted if I try to open them.
    I have also lost my time machine backup as OSX has reported that this has failed verification and needs to be created new; I accepted creating a new one (reluctantly) and the backup now fails to complete every time it runs - either the wireless cuts out or the SSL connection corrupts the backup.
    I have a 16-port GigE Switch (Netgear GS116) with a number of computers and the home modem plugged into this.
    I've tried the following to look at this:
    I've tried (and tested) a number of different Cat5e and Cat6 cables. These all work fine with other Windows / Linux machines and according to my cable tester all check out. 100% of the cables I own produce the error leading me to believe that it's not a cable problem.
    Problem occurs even if the switch is bypassed and the mac plugged directly into the modem.
    Problem does not occur (for web pages and small downloads) when plugged into wireless - this is just sloooow and as the router seems to develop issues with DNS over WiFi, I have to reset it every few hours so long term downloads fail.
    I found an article (which I have now lost the URL for) where someone suffered intermittent network issues with Ethernet that they resolved by un-checking the "Enable automatic connection" on the 802.1X page of the network settings. This appeared to help for a couple of days and I enjoyed fast Ethernet and downloads once more. However, today the problem is back in force.
    I am able to download files from a windows machine (well, except for downloads via the App store) and then transfer them over the network to the mini with no problems at all - the corruption issue only seems to occur when SSL is involved.
    So I'm wondering what it could be and how I would go about diagnosing the issue. I'm more familiar with Windows / Linux systems, having not owned a Mac since the days of System 7 - the mini was bought so I could play with learning XCode and try my hand at Mac software development.
    Thanks in advance,
    ~MrBasset.
    Machine specs:
    Late 2012 Mac Mini running OXS Mavericks 10.9.3
    2.5Ghz Intel Core i5
    16GB Ram

    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    The title of the Console window should be All Messages. If it isn't, select
              SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar at the top of the screen.Click the Clear Display icon in the toolbar. Then try the action that you're having trouble with again. Select any messages that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    Some private information, such as your name, may appear in the log. Anonymize before posting.

  • Ethernet/wireless connectivity issues with Airport Express

    I am having problems with my PC seeing my newly aquired AE and was hoping someone can help, none of the topics already discussed seem to be exaclty the same as my issue.
    Scenario:
    * iTunes on the PC does not detect the AE so I cannot play my iTunes setup through my stereo.
    * The PC can ping the AE.
    * The PC can configure the AE if I open the AirPort utility and go to File, Configure Other and enter teh units details.
    * Both laptops can connect to the AE via iTunes and the AE Utility also picks up the device.
    Equipment
    * I have an Open Networks 625W 4 port ADSL router with wireless included in the unit.
    * My PC is connected to my LAN via ethernet and is running Windows Vista fully service packed.
    * I have two laptops both connected via wireless on my LAN and all devices (ethernet and wireless) can see each other.
    * I have an AE with latest firmware and the latest version of the Airport Utility running.
    * The bonjour service is running on the PC.
    * I have tried turning the PC's F/W off with no change.
    * I have tried connecting one of the laptops to my network via ethernet and had the same issues as the PC.
    Configuration:
    I have tried many different methods of configuration but the one that has me working this far is-
    * Joined to a wireless network.
    * Using DHCP (and getting IP addresses fine off the third party router)
    * Connection sharing is off by default so its working in bridged mode.
    Its almost as if the router is not allowing those packets related to Airtunes to pass through from/to the wireless router(and I have tried so many different settigns there). I believe Bonjour is required and Im not sure if any routers have issues with bonjour but I believe its encapsulated within IP packets (not sure on that though). Or Maybe some routers don't work in this scenario and I need to update to a Belkin Wireless G or N or other. Or maybe the software will only accept direct wireless connections if its configured for wireless - I have no idea and am losing hair fast.
    Please, any help would be appreciated.

    I finally cracked it!
    I have enabled dynamic routing with RIP v2 (v1 works too), enabled multicast with IGMP proxy and used a bridge filter allowing all traffic between the LAN and the wireless networks. All three settings are required with my router. If I drop any of them AE from LAN to wireless will not work.

  • Audio interface connection issues - growing very frustrated!

    Hi there,
    I'm having a **** of a time with a very basic recording set-up.  I'm using an M-Audio Fast Track with Logic Pro 9.  I have a digital stage piano which is connected via USB to my macbook pro, but I am also connecting one of the audio output ports from my piano (a Kawai MP5) into the audio interface device. Basically I want to take advantage of the software instruments, AND some of the built-in piano sounds of my digital piano.  My set-up is like this:  the audio interface device is connected via USB to my macbook pro.  My piano is also connected via USB to the macbook pro.  My piano has another connection going into the audio interface device.  I want to be able to hear ALL audio via the headphone output on the macbook pro.  I have the audio settings within Logic Pro set up such that the audio input device is the Fast Track, and the audio output device is the built-in output of the macbook.
    Within Logic Pro, I create a real instrument track, and I have it record enabled, BUT - I cannot hear anything coming through.  The signal indicator on the Fast Track lights up whenever I play the piano...but I do not hear anything in my headphones (connected to the macbook's built-in output).  If I create a software instrument track, I have no problem hearing anything.
    Would somebody please PLEASE tell me how to connect my devices or adjust settings so that I can hear my piano within Logic Pro?  Technically, the way I have connected everything should work from the way I see it.  I don't know if I have to have a monitor enabled or disabled somewhere in order to hear the piano, but I have been playing around for over an hour now trying to get sound to come through with no success.
    Thanks.

    There are Audio track types  Mono (one meter) Stereo (two smaller parallel meters) They can be changed using the small circle(s) at the bottom of the channel strip under the meter. It's self explanatory once you click on the circle.
    The Inputs reflect your audio Interface.  I assume Input 1 is your Mic Input, Input 2 is your guitar input... If you use a stereo track you will probably see Input 1-2 which means both inputs are being monitored... If your guitar is plugged into Input 2 you will only hear one side.
    My audio interface has 8 inputs so I if I'm choosing inputs for a stereo strip I see pairs.. 1-2, 3-4, 5-6, 7-8. If I choose inputs for a mono track I see 8 individual inputs. If I have in instrument plugged into channel 1 I will only hear sound if the inputs have 1-2, or 1. If it's a stereo track it will be on one side only.
    And you have the pan adjustment.. pan left, pan right, pan center.   
    Use Logic online help for some quick hints

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

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

  • Ethernet connectivity issue with Microsoft Small Business Server (SBS)

    Just recently updated my OS to Yosemite, and am now having ongoing problems connecting to my company's Microsoft Small Business Server (SBS).
    I'm having no other issues connecting to outside server's via wifi or ethernet, but once I connect to our local business server I lose internet connection and also my email account goes offline (Microsoft Outlook 2011). Sometimes the connection will intermittently return, but will be very slow and won't load images. I had no connection issue's before the update.
    Anyone experienced a similar problem?

    "That depends on what what resources you use the server for."
    - I will be using the printer for print sharing and file sharing. There is an estimating application I will load on a Mac Mini and will want to share that to other desktops.

  • Connectivity issues caused by coax, will Verizon install ethernet line to the second floor?

     Lately i've been having connectivity issues(bad lag, pages stop loading) and the problem appears to be the coax line that is running between my ONT(in the garage) and office(two floors up) .  How do i know it's the coax? Well, when the router is in the office and  I ping yahoo.com, i get an average of 120ms, ~10% packet loss. Then I moved the actiontec router to a 3 foot cable directly attached to my ONT and I get 20ms, zero packet loss. Unless im missing something it seems like there is a problem with the lines in my house and their ability to do internet over coax. My FIOS TV service works fine. I have tested all my other coax lines and they all have the same issue except for the one in the living room, however i cant use that line because wireless doesn't reach the office. So the only solution im seeing is to run an ethernet line from the ONT directly to the office. The distance is at most 75ft so signaling should not be an issue. Will Verizon install the ethernet line for me or will I have to do it myself? I feel like im not getting proper service and Verizon should be responsible for fixing it. If anyone here has other suggestions to remedy my problem please let me know. Thx guys!

    I can't answer the question about Verizon running Cat5 for you.  I'm sure someone else here will have that answer.  But some thoughts about the problem you're seeing.
    Is the coax from the garage to your office reasonably new and in good shape?
    Have you tried changing the connectors at both ends?
    How are splitters configured?  I would think you should have the router on one 3.5 dB leg of the first splitter and the rest of the house off any other splits.  And a splitter could be bad.  You could try getting a coax "barrel" from Radio Shack and, as a test, bypassing any splitter in between the ONT and the router in your office.
    Is the run from the garage to the router about the same as the run to the living room?  I'm wondering if the router itself might be defective and require more signal than it should. 
    FWIW, it sounds like I have a similar setup to yours and it just works.  I know some prefer Cat5 ONT-router for various reason but I like the Verizon default configuration for it's simplicity and for the fact that Verizon will support it if support is needed.   I wonder what tech support would say about your situation if you could get past tier 1 script reading. 
    Good luck.
    P.S.
    The more I think about it the more I suspect a splitter is your problem.  I say that because if I understand you correctly, you get the same results at the end of every piece of coax except in the living room.  Right?  That leads me to think the connection to the ONT is getting screwed up somewhere that it's being split.  FWIW.
    edit & P.P.S.
    This is the "barrel" I had in mind to bypass any splitters for troubleshooting purposes:
    http://www.radioshack.com/product/index.jsp?productId=2103648

  • EA6900 Internet Connection Issue - Desktop connected via ethernet cable

    Hi there,
    I have an HP p6837c, 64-bit OS with Windows 7 Home Premium. It is directly connected to the EA6900 via ethernet cable. My internet connection constantly drops (as in variably every 5 seconds to 5 minutes) then re-establishes itself. I have no internet connection issues when directly connected to the modem. All of the wirelss devices that are connected via the EA6900 are working without any issue. My husband's laptop, which has Windows 8.1, functions with no problem when directly connected to the EA6900 via ethernet cable. We've tried swapping out the cable. We've tried adjusting the MTUs per Support's suggestion. Nothing has solved the issue
    Any thoughts on what the issues might be? Settings? The version of Windows? Any help would be much appreciated!

    Internet Service Provider and Modem Configurations
    What ISP Service do you have? Cable or DSL?
    What ISP Modem Mfr. and model # do you have?
    Is ISP Modem/Service using Dynamic or Static WAN IP addressing?
    What ISP Modem service link speeds UP and Down do you have?
    Check cable between Modem and Router and PC, swap out to be sure. Link>http://en.wikipedia.org/wiki/CAT6 is recommended.
    Check ISP MTU requirements, Cable is usually 1500, DSL is around 1492 down to 1472. Call the ISP and ask.
    I recommend that you have your ISP check the cabling going to the ISP modem, check signal levels going to the ISP modem. For cable Internet, RG-6 coaxial cable is needed, not RG-59. Check for t.v. line splitters and remove them as they can introduce noise on the line and lower the signal going to the ISP modem. Connecting to the ISP modem could result in a false positive as the signal to the modem could be just enough to that point then adding on a router, could see problems. The router operation is dependent upon getting good data flow from the ISP modem and the modem is dependent upon getting good signal from the ISP Service.
    Router and Wired Configurations
    Setup DHCP reserved IP addresses for all devices ON the router. This ensures each devices gets its own IP address when turned on and connected, eliminates IP address conflicts and helps in troubleshooting and maintain consistency for applications that need to connect as well as mapped drives.
    Ensure devices are set to auto obtain an IP address.
    If http://en.wikipedia.org/wiki/Ipv6 is an option on the router, select Local Connection Only.
    PC 3rd Party Security Software Configurations
    Turn off all anti virus and firewall programs on PC while testing. 3rd party firewalls are not generally needed when using routers as they are effective on blocking malicious inbound traffic.
    Router Placement
    Forum User - "Well I feel really dumb. After moving the router away from other electronic devices my speeds are back to normal. Just a heads up for anyone experiencing slow speeds, you might want to move it away from other electronics and see if that helps."
    3-6' feet minimum safe distance between devices.
    Placement on main level floor and central in the building and WELL ventilated is preferred. Not in basements or closets as building materials, or near by electronics devices could interfere or hinder good signal propagation.

  • Lan connectivity Issue on autonomous AP with throttles

              Hello,
      I encounter a strange problem on several AP 1242 in version 12.4(25d)JA1 of a customer :
      He has 10 autonomous AP covering a factory and is using them for laptop connectivity and TOIP with mainly 7921 Cisco Wifi Phones.
      The phones are configured to use only 802.11a.
      The APs loose LAN connectivity randomly and therefore the clients don't work anymore.
      The AP are connected on a 2960 and a 3560 wich are in turn connected on a 3750 wich route the trafic.
      After checking spanning-tree no loops are present.
      When I check the counters on the AP involved I see the "trhottles" and "ignored" counters incrementing on the fa0 link of the AP impacted wich mean I think it can't handle the incoming traffic. This incoming traffic seems not to be too big however. I can see drops on the switch interface connecting the AP.
    There is a lot of roaming on the AP due to people walking in the factory with their wifi phones.
    Here is a view of the fa0 counters :
    AP1242-LOGIST#sh int fa0
    FastEthernet0 is up, line protocol is up
      Hardware is PowerPCElvis Ethernet, address is 001d.a1ce.26e2 (bia 001d.a1ce.26e2)
      MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA, loopback not set
      Full-duplex, 100Mb/s, MII
      ARP type: ARPA, ARP Timeout 04:00:00
      Last input 00:00:00, output 00:00:00, output hang never
      Last clearing of "show interface" counters never
      Input queue: 0/160/0/0 (size/max/drops/flushes); Total output drops: 0
      Queueing strategy: fifo
      Output queue: 0/40 (size/max)
      5 minute input rate 81000 bits/sec, 53 packets/sec
      5 minute output rate 29000 bits/sec, 26 packets/sec
         7447113 packets input, 674891974 bytes
         Received 286839 broadcasts, 0 runts, 0 giants, 549631 throttles
         0 input errors, 0 CRC, 0 frame, 0 overrun, 549631 ignored
         0 watchdog
         0 input packets with dribble condition detected
         4422100 packets output, 609868806 bytes, 0 underruns
         0 output errors, 0 collisions, 4 interface resets
         1 unknown protocol drops
         0 babbles, 0 late collision, 0 deferred
         0 lost carrier, 0 no carrier
         0 output buffer failures, 0 output buffers swapped out
      Here is a small part of logs concerning roaming, i don't see errors or log indicating that something is wrong nor in the switches log :
    Jun  6 12:57:27.007: %DOT11-6-ASSOC: Interface Dot11Radio1, Station SEP001E4A3EE15D 001e.4a3e.e15d Associated KEY_MGMT[WPAv2 PSK]
    Jun  6 12:57:42.499: %DOT11-6-ASSOC: Interface Dot11Radio1, Station SEP588D09D3A92B 588d.09d3.a92b Reassociated KEY_MGMT[WPAv2 PSK]
    Jun  6 12:58:02.620: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating Station 588d.09d3.a92b Reason: Sending station has left the BSS
    Jun  6 12:58:03.653: %DOT11-6-ASSOC: Interface Dot11Radio1, Station SEP588D09D3A92B 588d.09d3.a92b Reassociated KEY_MGMT[WPAv2 PSK]
    Jun  6 12:59:15.564: %DOT11-6-ROAMED: Station 588d.09d3.a92b Roamed to 001e.134c.5a50
    Jun  6 12:59:15.564: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating Station 588d.09d3.a92b Reason: Sending station has left the BSS
    Jun  6 12:59:41.905: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating Station 442b.0355.ab28 Reason: Previous authentication no longer valid
    Jun  6 12:59:54.728: %DOT11-6-ASSOC: Interface Dot11Radio1, Station SEP442B0355AB28 442b.0355.ab28 Associated KEY_MGMT[WPAv2 PSK]
    Jun  6 13:01:12.541: %DOT11-6-ASSOC: Interface Dot11Radio1, Station SEP588D09D3A92B 588d.09d3.a92b Reassociated KEY_MGMT[WPAv2 PSK]
    Jun  6 13:02:35.841: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating Station 001e.4a3e.d875 Reason: Previous authentication no longer valid
    Jun  6 13:02:36.489: %DOT11-6-ASSOC: Interface Dot11Radio0, Station   ec85.2f7c.c837 Associated KEY_MGMT[WPAv2 PSK]
    Jun  6 13:03:29.256: %DOT11-6-ROAMED: Station 588d.09d3.a92b Roamed to 001e.134c.5a50
    Jun  6 13:03:29.256: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating Station 588d.09d3.a92b Reason: Sending station has left the BSS
    Jun  6 13:04:32.754: %DOT11-6-ASSOC: Interface Dot11Radio1, Station SEP001E4A3ED875 001e.4a3e.d875 Associated KEY_MGMT[WPAv2 PSK]
    Jun  6 13:06:47.858: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating Station 001e.4a3e.e15d Reason: Previous authentication no longer valid
    Jun  6 13:07:18.107: %DOT11-6-ROAMED: Station 001f.6c7a.5101 Roamed to 001d.a2bb.15b0
    Jun  6 13:07:18.107: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating Station 001f.6c7a.5101 Reason: Sending station has left the BSS
    Jun  6 13:07:38.109: %DOT11-6-ASSOC: Interface Dot11Radio1, Station SEP588D09D3A92B 588d.09d3.a92b Reassociated KEY_MGMT[WPAv2 PSK]
    Jun  6 13:07:42.031: %DOT11-6-ROAMED: Station 588d.09d3.a92b Roamed to 001e.134c.5a50
    Jun  6 13:07:42.031: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating Station 588d.09d3.a92b Reason: Sending station has left the BSS
    Jun  6 13:07:46.489: %DOT11-6-ASSOC: Interface Dot11Radio1, Station SEP001F6C7A5101 001f.6c7a.5101 Reassociated KEY_MGMT[WPAv2 PSK]
    Jun  6 13:08:27.712: %DOT11-6-ASSOC: Interface Dot11Radio1, Station SEP588D09D3A92B 588d.09d3.a92b Reassociated KEY_MGMT[WPAv2 PSK]
    Jun  6 13:08:44.502: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating Station 588d.09d3.a92b Reason: Sending station has left the BSS
    Jun  6 13:08:44.572: %DOT11-6-ASSOC: Interface Dot11Radio1, Station SEP588D09D3A92B 588d.09d3.a92b Associated KEY_MGMT[WPAv2 PSK]
    Jun  6 13:08:56.778: %DOT11-6-ROAMED: Station 588d.09d3.a92b Roamed to 001e.134c.5a50
    Jun  6 13:08:56.779: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating Station 588d.09d3.a92b Reason: Sending station has left the BSS
    Jun  6 13:09:17.874: %DOT11-6-ROAMED: Station 001f.6c7a.5101 Roamed to 003a.9a92.8d70
    Jun  6 13:09:17.874: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating Station 001f.6c7a.5101 Reason: Sending station has left the BSS
    The AP are configured as follow :
    Current configuration : 5184 bytes
    ! No configuration change since last restart
    version 12.4
    no service pad
    service timestamps debug datetime msec
    service timestamps log datetime msec
    service password-encryption
    hostname AP1242-LOGIST
    logging rate-limit console 9
    aaa new-model
    aaa authentication login default local
    aaa authorization exec default local
    aaa session-id common
    clock timezone gmt+1 1
    clock summer-time gmt recurring last Sun Mar 2:00 last Sun Oct 3:00
    dot11 syslog
    dot11 vlan-name Data vlan 11
    dot11 vlan-name Voix vlan 14
    dot11 vlan-name Webguest vlan 5
    dot11 ssid WLAN_data
       vlan 11
       authentication open
       authentication key-management wpa
       mbssid guest-mode
       wpa-psk ascii 7 10600C0E261B173C252203797479633F371A29
    dot11 ssid WLAN_voice
       vlan 14
       authentication open
       authentication key-management wpa
       mbssid guest-mode
       wpa-psk ascii 7 080F49592A1500203B2D25567A7A7622263C0C
    dot11 ssid Webguest
       vlan 5
       authentication open
       mbssid guest-mode
    dot11 wpa handshake timeout 1000
    dot11 arp-cache
    dot11 priority-map avvid
    dot11 phone
    power inline negotiation prestandard source
    class-map match-all _class_voice0
    match ip dscp ef
    class-map match-all _class_voice1
    match ip dscp cs3
    policy-map voice
    class _class_voice0
      set cos 6
    class _class_voice1
      set cos 3
    bridge irb
    interface Dot11Radio0
    no ip address
    no ip route-cache
    encryption vlan 11 mode ciphers aes-ccm
    encryption vlan 14 mode ciphers aes-ccm
    ssid WLAN_data
    ssid WLAN_voice
    ssid Webguest
    mbssid
    power client 17
    channel 2472
    station-role root
    dot11 qos class voice local
        admission-control
        admit-traffic narrowband max-channel 75 roam-channel 6
    dot11 qos class voice cell
        admission-control
    no cdp enable
    infrastructure-client
    interface Dot11Radio0.5
    encapsulation dot1Q 5
    no ip route-cache
    no cdp enable
    bridge-group 5
    bridge-group 5 subscriber-loop-control
    bridge-group 5 block-unknown-source
    no bridge-group 5 source-learning
    no bridge-group 5 unicast-flooding
    bridge-group 5 spanning-disabled
    interface Dot11Radio0.11
    encapsulation dot1Q 11
    no ip route-cache
    no cdp enable
    bridge-group 11
    bridge-group 11 subscriber-loop-control
    bridge-group 11 block-unknown-source
    no bridge-group 11 source-learning
    no bridge-group 11 unicast-flooding
    bridge-group 11 spanning-disabled
    interface Dot11Radio0.14
    encapsulation dot1Q 14
    no ip route-cache
    no cdp enable
    bridge-group 14
    bridge-group 14 subscriber-loop-control
    bridge-group 14 block-unknown-source
    no bridge-group 14 source-learning
    no bridge-group 14 unicast-flooding
    bridge-group 14 spanning-disabled
    interface Dot11Radio1
    no ip address
    no ip route-cache
    encryption vlan 11 mode ciphers aes-ccm
    encryption vlan 14 mode ciphers aes-ccm
    ssid WLAN_data
    ssid WLAN_voice
    ssid Webguest
    no dfs band block
    mbssid
    channel dfs
    station-role root
    interface Dot11Radio1.5
    encapsulation dot1Q 5
    no ip route-cache
    no cdp enable
    bridge-group 5
    bridge-group 5 subscriber-loop-control
    bridge-group 5 block-unknown-source
    no bridge-group 5 source-learning
    no bridge-group 5 unicast-flooding
    bridge-group 5 spanning-disabled
    interface Dot11Radio1.11
    encapsulation dot1Q 11
    no ip route-cache
    no cdp enable
    bridge-group 11
    bridge-group 11 subscriber-loop-control
    bridge-group 11 block-unknown-source
    no bridge-group 11 source-learning
    no bridge-group 11 unicast-flooding
    bridge-group 11 spanning-disabled
    interface Dot11Radio1.14
    encapsulation dot1Q 14
    no ip route-cache
    no cdp enable
    bridge-group 14
    bridge-group 14 subscriber-loop-control
    bridge-group 14 block-unknown-source
    no bridge-group 14 source-learning
    no bridge-group 14 unicast-flooding
    bridge-group 14 spanning-disabled
    interface FastEthernet0
    no ip address
    no ip route-cache
    speed 100
    full-duplex
    no cdp enable
    hold-queue 160 in
    interface FastEthernet0.1
    encapsulation dot1Q 1 native
    no ip route-cache
    no cdp enable
    bridge-group 1
    no bridge-group 1 source-learning
    bridge-group 1 spanning-disabled
    interface FastEthernet0.5
    encapsulation dot1Q 5
    no ip route-cache
    no cdp enable
    bridge-group 5
    no bridge-group 5 source-learning
    bridge-group 5 spanning-disabled
    interface FastEthernet0.11
    encapsulation dot1Q 11
    no ip route-cache
    no cdp enable
    bridge-group 11
    no bridge-group 11 source-learning
    bridge-group 11 spanning-disabled
    interface FastEthernet0.14
    encapsulation dot1Q 14
    no ip route-cache
    no cdp enable
    bridge-group 14
    no bridge-group 14 source-learning
    bridge-group 14 spanning-disabled
    service-policy input voice
    service-policy output voice
    interface BVI1
    ip address 10.17.10.5 255.255.255.0
    no ip route-cache
    ip default-gateway 10.17.10.254
    ip http server
    ip http authentication aaa
    no ip http secure-server
    ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
    logging trap warnings
    logging 10.15.51.115
    no cdp run
    bridge 1 route ip
    line con 0
    line vty 0 4
    sntp server 10.15.1.50
    sntp broadcast client
    end
    Does someone ever experienced a similar problem ?
    When I shut radio interfaces they're is no more problems on the LAN. Can this be an overlapping coverage issue ?
    Can someone please give me advices on how to troubleshoot this issue ?
    Thank you in advance as I'm a bit stuck.
    Best Regards,

         Hi Scott,
    Thanks for your reply.
    Do you think this can be the origin of the issue my customer encounters or is it only to be standard ? As this change will have to be made on all clients, if there is a chance it solves the problem I will do it ASAP, if not I will delay it in a less busy period :-)
    Can the constant roaming associations and dissasociations overload the AP and make it stop responding on the LAN or is it only a throuhput problem ?
    Thanks in advance for your answer.
    Best Regards,

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

  • HP Slate 21 Pro: WiFi connection issues

    Hi,
    I recently ordered two HP Slate 21 Pro devices. Unfortunately, both of them have WiFi connection issues. After some time the properly configured WiFi connection will be dropped, which results in connectionless devices. The WiFi AP is disabled after this, and so a timed reconnect will not succeed.
    After inspecting the Logcat I found following lines:
    12-05 08:56:58.939 V/EthernetStateTracker(675): report interface is up for eth0
    12-05 08:56:58.939 I/EthernetStateTracker(675): interface up event, kick off connection request
    12-05 08:56:58.939 I/EthernetStateTracker(675): interface up but ethernet is disabled, stop this interface
    12-05 08:56:58.939 I/EthernetStateTracker(675): stop dhcp and interface
    12-05 08:56:58.947 V/EthernetStateTracker(675): report interface is up for eth0
    12-05 08:56:58.948 I/EthernetStateTracker(675): interface up event, kick off connection request
    12-05 08:56:58.948 I/EthernetStateTracker(675): interface up but ethernet is disabled, stop this interface
    12-05 08:56:58.954 I/EthernetStateTracker(675): report new state DISCONNECTED on dev eth0
    12-05 08:56:58.954 V/EthernetStateTracker(675): update network state tracker
    12-05 08:56:58.954 V/EthernetStateTracker(675): Ethernet is disabled, ignore state change event
    12-05 08:56:59.080 D/ConnectivityService(675): ConnectivityChange for WIFI: DISCONNECTED/DISCONNECTED
    12-05 08:56:59.080 D/ConnectivityService(675): Attempting to switch to BLUETOOTH_TETHER
    12-05 08:56:59.080 V/EthernetStateTracker(675): reconnect +++
    12-05 08:56:59.080 D/ConnectivityService(675): Attempting to switch to ETHERNET
    12-05 08:56:59.094 D/ConnectivityService(675): resetConnections(wlan0, 3)
    12-05 08:56:59.201 I/EthernetStateTracker(675): stop dhcp and interface
    12-05 08:56:59.208 D/Nat464Xlat(675): requiresClat: netType=1, hasIPv4Address=false
    12-05 08:56:59.208 D/ConnectivityService(675): handleInetConditionChange: no active default network - ignore
     Especially this line:
    12-05 08:56:59.080 D/ConnectivityService(675): ConnectivityChange for WIFI: DISCONNECTED/DISCONNECTED
    Is this issue already known? Has someone a solution for me?
    Thanks in advance,
    Christian

    That really shouldn't affect it.
    I'm a little stumped because I haven't seen this issue with this device before. The only similar issue I found was this, and it's unresolved.
    Have you tried doing a hard reboot of the Slate 21? 
    I work on behalf of HP (But this isn't my job)
    Mark my post as “Accept as Solution" if you feel my post solved your issue, so that others with the same question can find the answer.
    Please give me Kudos if I wrote something that helped you.

  • [Solved] Default interface routing issues

    I have two network interfaces connected to my newly installed ArchLinux server,  one LAN and one WAN connection.  The trouble is that all traffic that is trying to connect to the wan interface gets no response, while the LAN connection work without any issue.
    I am using udev to change my interfaces to lan0 and wan0, and i use netcfg to load the diffrent profiles.
    Lan0 uses a static local ip 192.168.0.118  with 192.168.0.2 as gateway
    Wan0 uses dhcp  with dynamic ip from my ISP.
    When i manually bring down my lan0 interface all my traffic goes through wan0 correctly, and it even responds to external calls.
    So i belive the issue lies somewhere in the local routing?
    I am trying to post all config files needed directly.
    /etc/rc.conf
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # LANG in /etc/locale.conf takes precedence
    # DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
    # startup and during the boot process. If set to 'no', the C locale is used.
    # HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
    # in the hardware clock being left untouched (useful for virtualization)
    # Note: Using "localtime" is discouraged, using "" makes hwclock fall back
    # to the value in /var/lib/hwclock/adjfile
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # Note: if unset, the value in /etc/localtime is used unchanged
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="sv_SE.UTF-8"
    DAEMON_LOCALE="no"
    HARDWARECLOCK="UTC"
    TIMEZONE="Europe/Stockholm"
    KEYMAP="sv-latin1"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
    # Replace every !module by an entry as on the following line in a file in
    # /etc/modprobe.d:
    # blacklist module
    # See "man modprobe.conf" for details.
    MODULES=()
    # Udev settle timeout (default to 30)
    UDEV_TIMEOUT=30
    # Scan for FakeRAID (dmraid) Volumes at startup
    USEDMRAID="no"
    # Scan for BTRFS volumes at startup
    USEBTRFS="no"
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="yes"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="weed-devil"
    # Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
    # Wired network setup
    # - interface: name of device (required)
    # - address: IP address (leave blank for DHCP)
    # - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
    # - broadcast: broadcast address (ignored for DHCP) (optional)
    # - gateway: default route (ignored for DHCP)
    # Static IP example
    # interface=eth0
    # address=192.168.0.2
    # netmask=255.255.255.0
    # broadcast=192.168.0.255
    # gateway=192.168.0.1
    # DHCP example
    # interface=eth0
    # address=
    # netmask=
    # gateway=
    #interface=eth0
    #address=
    #netmask=
    #broadcast=
    #gateway=
    # Setting this to "yes" will skip network shutdown.
    # This is required if your root device is on NFS.
    NETWORK_PERSIST="no"
    # Enable these netcfg profiles at boot-up. These are useful if you happen to
    # need more advanced network features than the simple network service
    # supports, such as multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This requires the netcfg package
    NETWORKS=(sluggy local)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    # If you are sure nothing else touches your hardware clock (such as ntpd or
    # a dual-boot), you might want to enable 'hwclock'. Note that this will only
    # make a difference if the hwclock program has been calibrated correctly.
    # If you use a network filesystem you should enable 'netfs'.
    DAEMONS=(syslog-ng !ufw !network net-profiles @alsa crond dbus sshd lircd sensors mysqld @ddclient @hddtemp httpd samba stunnel sabnzbd sickbeard)
    /etc/network.d/sluggy
    CONNECTION='ethernet'
    DESCRIPTION='A basic dhcp ethernet connection using iproute'
    INTERFACE='wan0'
    IP='dhcp'
    ## for DHCPv6
    #IP6='dhcp'
    ## for IPv6 autoconfiguration
    #IP6='stateless'
    /etc/network.d/local
    CONNECTION='ethernet'
    DESCRIPTION='A basic static ethernet connection using iproute'
    INTERFACE='lan0'
    IP='static'
    ADDR='192.168.0.118'
    GATEWAY='192.168.0.2'
    output of route -nl
    Destination Gateway Genmask Flags Metric Ref Use Iface
    0.0.0.0 192.168.0.2 0.0.0.0 UG 0 0 0 lan0
    0.0.0.0 85.24.137.1 0.0.0.0 UG 203 0 0 wan0
    85.24.137.0 0.0.0.0 255.255.255.0 U 203 0 0 wan0
    192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 lan0
    I have had this server running Ubuntu for the past 2 years with the same setup on the NIC's and there everything worked, so I guess i have become a little lazy.
    *EDIT* Updated my post with "code" block instead of quote
    Last edited by kurri (2011-11-01 22:07:14)

    kurri, please edit your post.
    When pasting code, please use [ code ] tags https://bbs.archlinux.org/help.php#bbcode
    like this
    It makes the code more readable and more convenient to scroll through.

Maybe you are looking for