Eth0 changes to eth1

with the new kernel 2.6.19 my eth0 card sometimes changes to eth1, anyone know if this is a bug or something?
my computer specs:
MSI k8n SLI-FI
AMD Athlone 64 3200+
512 mb ram
i do only have one network card so i think its wired that it changes from eth0 to eth1 sometimes..

Snowman wrote:this might help:
http://wiki.archlinux.org/index.php/Ude … _Each_Boot
I think that wiki is a little outdated as far as the actual file to modify. On my system its /etc/udev/rules.d/70-persistent-net.rules. If you find that file and modifying works let us know and I (or you can) update the wiki.

Similar Messages

How to permanently set wicd wired interface? eth0 changes to vboxnet0

I use wicd in Gnome. Works well, only problem is that everytime I use the laptop on-the-go (which is daily) without a wired LAN connection via eth0, wicd changes my default wired connection to vboxnet0 (obviously, I have virtualbox installed). Is there some way of permanently setting my wired connection to be eth0? It gets iritating to keep having to manually change it back when I get back to my office.
For the record, the output of cat /etc/wicd/manager-settings.conf shows
wired_interface = eth0
Can't think of any other configuration files I may edit, except for /usr/lib/*.py, which I don't have the command of python to grasp.
Assistance appreciated. And yes, i do know about netcfg, but don't really want to be hand-editing stuff for networking.

Problem solved? If not, http://wiki.archlinux.org/index.php/Ude … _Each_Boot

How to swap eth0 - eth1 with testingudev rules[SOLVED

Hi,
I want to use the udev in testing because my ML-1710P works just out of the box. Of course there is one problem ... I have two network cards and they are recognized by kernel as eth0 the one that uses 8139too (a Realtek I belive) and as eth1 the one that uses tulip. I need to swap their names because I use the tulip one for internet (my ISP uses MAC address for validation)
Previously I had in /etc/modprobe.conf
alias eth0 tulip
alias eth1 8139too
I already tried
KERNEL="eth*", SYSFS{address}="xx-xx-xx-xx-xx-xx", NAME="eth1"
KERNEL="eth*", SYSFS{address}="xx-xx-xx-xx-xx-xx", NAME="eth0"
in a file /etc/udev/rules.d/00_my.rules with correct MAC address (and lines order swapped also), but it won't work.
Any ideea how to do this?
PS: I have MOD_AUTOLOAD="yes" in /etc/rc.conf

I would add the modules to the modules section in rc.conf, in the order you need them to be loaded. It does not change the autoload function, but this modules are loaded just before autoloader starts. So here is a good point to touch the system. In the end, it does what your old modprobe.conf entries did.
The first one will allways be eth0 etc.

[SOLVED]eth1 and eth0 keep switching

Ok I've got two NIC's in this computer, one refuses to get an IP address from DHCP the other work perfectly fine. However each time I start up the one that previously was eth0 is now eth1 and vise versa.
eth0="dhcp"
INTERFACES=(eth0)
00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev f3) # WORKS
05:0c.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13) # BORK
[01:21 AM][desktop:~]# uname -rm
2.6.30-ARCH x86_64
Last edited by fumbles (2009-07-01 04:05:07)

http://wiki.archlinux.org/index.php/Ude … _Each_Boot

Oracle Redhat 6.4 - eth0: no IPv6 routers present

Dear Experts,
I installed Oracle Redhat 6.4.
But the network is not working.
What is the secret to making it work?
Analysis below.
Thanks a lot!
Use:
file /usr/share/system-config-network/netconf_tui.py
/usr/share/system-config-network/netconf_tui.py: a /usr/bin/python script text executable
- brings up a character based GUI
DEVICE CONFIGURATION
DNS Configuration
change DNS Configuration from Belkin to the DNS of the router.
Device:
DHCP
save and quit
(This will be changed to static eventually, but my
practice/experience is to get it to first work with DHCP)
/sbin/ifdown eth0
Error: Device 'eth0' (/org/freedesktop/NetworkManager/Devices/0) disconnecting failed: This device is not active
/sbin/ifup eth0
Active connection state: activating
Active connection path: /org/freedesktop/NetworkManager/ActiveConnection/32
** (process:29591): WARNING **: nmobject_get_property: Error getting 'State' for /org/freedesktop/NetworkManager/ActiveConnection/32: (19) Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist
state: unknown
Error: Connection activation failed.
Reboot.
dmesg | grep -i "eth"
e1000e 0000:04:00.0: eth0: (PCI Express:2.5GT/s:Width x4) 00:23:54:73:5f:01
e1000e 0000:04:00.0: eth0: Intel(R) PRO/1000 Network Connection
e1000e 0000:04:00.0: eth0: MAC: 6, PHY: 5, PBA No: FFFFFF-0FF
e1000e 0000:04:00.1: eth1: (PCI Express:2.5GT/s:Width x4) 00:23:54:73:5f:00
e1000e 0000:04:00.1: eth1: Intel(R) PRO/1000 Network Connection
e1000e 0000:04:00.1: eth1: MAC: 6, PHY: 5, PBA No: FFFFFF-0FF
ADDRCONF(NETDEV_UP): eth0: link is not ready
e1000e: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
e1000e 0000:04:00.0: eth0: 10/100 speed: disabling TSO
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
8021q: adding VLAN 0 to HW filter on device eth0
ADDRCONF(NETDEV_UP): eth1: link is not ready
8021q: adding VLAN 0 to HW filter on device eth1
eth0: no IPv6 routers present
eth0: no IPv6 routers present
eth0: no IPv6 routers present
ping yahoo.com
ping: unknown host yahoo.com
ifconfig
eth0 Link encap:Ethernet HWaddr 00:23:54:73:5F:01
inet6 addr: fe80::223:54ff:fe73:5f01/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:38 errors:0 dropped:0 overruns:0 frame:0
TX packets:61 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7121 (6.9 KiB) TX bytes:6394 (6.2 KiB)
Interrupt:18 Memory:b0200000-b0220000

Thanks for responding.
I edited a few of the files. But the symptom remains.
See the output below.
cd /etc/sysconfig
cat network
NETWORKING=yes
NETWORKING_IPV6=yes
HOSTNAME=black
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
IPADDR=192.168.2.201
NETMASK=255.255.255.0
GATEWAY=192.168.2.1
DEVICE=eth0
TYPE=Ethernet
UUID=b87686b8-079b-4e86-a6ed-ad9dbc14f2ac
ONBOOT=yes
NM_CONTROLLED=yes
BOOTPROTO=dhcp
HWADDR=00:23:54:73:5f:01
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=yes
NAME="System eth0"
USERCTL=no
cat /etc/resolv.conf
nameserver 192.168.2.1
Reboot
ping yahoo.com
ping: unknown host yahoo.com
dmesg | grep -i "eth0"
e1000e 0000:04:00.0: eth0: (PCI Express:2.5GT/s:Width x4) 00:23:54:73:5f:01
e1000e 0000:04:00.0: eth0: Intel(R) PRO/1000 Network Connection
e1000e 0000:04:00.0: eth0: MAC: 6, PHY: 5, PBA No: FFFFFF-0FF
ADDRCONF(NETDEV_UP): eth0: link is not ready
e1000e: e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
e1000e 0000:04:00.0: eth0: 10/100 speed: disabling TSO
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
8021q: adding VLAN 0 to HW filter on device eth0
eth0: no IPv6 routers present
eth0: no IPv6 routers present
eth0: no IPv6 routers present
eth0: no IPv6 routers present
eth0: no IPv6 routers present
eth0: no IPv6 routers present
eth0: no IPv6 routers present
eth0: no IPv6 routers present
ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:23:54:73:5F:01
inet6 addr: fe80::223:54ff:fe73:5f01/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:50 errors:0 dropped:0 overruns:0 frame:0
TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6775 (6.6 KiB) TX bytes:8918 (8.7 KiB)
Interrupt:18 Memory:b0200000-b0220000
eth1 Link encap:Ethernet HWaddr 00:23:54:73:5F:00
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:19 Memory:b0220000-b0240000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:960 (960.0 b) TX bytes:960 (960.0 b)
virbr0 Link encap:Ethernet HWaddr 52:54:00:26:12:A9
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
virbr0-nic Link encap:Ethernet HWaddr 52:54:00:26:12:A9
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
which nm-connection-editor
/usr/bin/nm-connection-editor
Showed 2 connections for eth0
Deleted one.
IPV4 - set to Automatic DHCP
IPV6 - set to Automatic
No routes.
Yes, the ethernet cable is in the correct port.
Whatis:
8021q: adding VLAN 0 to HW filter on device eth0
How can I tell if I'm running NetworkManager?
Thanks a lot!

Clean Access HTTP redirect wrong after IP address change

Hi,
Wondered if anyone had seen this:
We have a Clean Access server running in VGW mode for VPN traffic, after a redesign the IP address has changed (the trusted and untrusted are the same).
Unfortunately when a user logs in it still uses the old IP address in the HTTP redirect, this has been confirmed by looking at the HTML source.
Apart from that it looks fine, new SSL certificate etc.
Any ideas apopreciated, thanks.
Jim.

For all deployments, if planning to configure the Clean Access Server in Virtual Gateway mode (IB or OOB), do not connect the untrusted interface (eth1) of the standalone CAS or HA-Primary CAS until after you have added the CAS to the CAM from the web admin console. For Virtual Gateway HA-CAS pairs, also do not connect the eth1 interface of the HA-Secondary CAS until after HA configuration is fully complete. Keeping the eth1 interface connected while performing initial installation and configuration of the CAS for Virtual Gateway mode can result in network connectivity issues.
When setting up a CAS in Virtual Gateway mode, you specify the same IP address for the trusted (eth0) and untrusted (eth1) network interfaces during the initial installation of the CAS via CLI. At this point in the installation, the CAS does not recognize that it is a Virtual Gateway. It will attempt to connect to the network using both interfaces, causing collisions and possible port disabling by the switch. Disconnecting the untrusted interface until after adding the CAS to the CAM in Virtual Gateway mode prevents these connectivity issues. Once the CAS has been added to the CAM in Virtual Gateway mode, you can reconnect the untrusted interface.
Administrators must use the procedure mentioned in the below URL for correct configuration of a Virtual Gateway Central Deployment:
http://www.cisco.com/en/US/docs/security/nac/appliance/configuration_guide/418/cas/s_instal.html#wp1045874

Ethernet card no longer showing in ifconfig [solved]

Hey,
Normally I don't have any problems with my networking, but this morning my wireless decided not to work. I haven't made made any changes in the past couple of days, so unsure what has caused it. Last Syu was on Thursday and every day including up until last night was fine.
So spent a while trying stuff out and stressing my tiny little brain for ideas, quick version is I did this:
netcfg: said interface didn't exist.
ifconfig: didn't list the interface (wireless is usually eth1)
lsmod: confirmed the module (ipw2200) was loaded
lspci: confirmed the card was there
After copying the output of the above commands plus the obligatory rc.conf onto usb to move to this machine (and just before pushing <submit> on a much larger post than this :-) I decided to check the mac address listed in ifconfig with what is on the sticker under my machine. Voila! My wireless has actually moved to eth0. OK, that's that solved. (Wish I checked that first though...)
But that means that the reason that my wireless card is now eth0 instead of eth1 is because my old-skool wired ethernet card is no longer there to be numero 0. Why isn't it working? lsmod shows that the tg3 module is loading (it's an Intel card with Broadcom chipset in a Thinkpad T43) , but it no longer shows up in ifconfig. lspci is not showing it (see below), only the wireless card comes up. Does this mean the hardware is borken? What else can I do to check the card?
$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 3 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: ATI Technologies Inc M22 [Mobility Radeon X300]
0b:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 8d)
0b:02.0 Network controller: Intel Corporation PRO/Wireless 2915ABG [Calexico2] Network Connection (rev 05)
Appreciate any advice you can give.
Cheers,
vW
Edited subject
Last edited by von_Wanderlust (2009-07-28 16:10:22)

Yeah, doesn't give me anything about the ethernet card, but does show the wireless one. No, hang on, just found it. Hmmm, didn't see it before, but I was grepping for 'net' then.
$ dmesg | grep -i eth
eth1: Tigon3 [partno(BCM95751M) rev 4101] (PCI Express) MAC address 00:12:34:56:78:9a
eth1: attached PHY is 5750 (10/100/1000Base-T Ethernet) (WireSpeed[1])
eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
eth1: dma_rwctrl[76180000] dma_mask[64-bit]
OK, so it is at eth1 now, that makes sense since I put ipw2200 right at the beginning and tg3 right at the end of the MODULES array in rc.conf to avoid the system getting crossed up while trying load them too close together. Thanks B, so at least we know something is happening at boot time.
Btw, my assumption is that ifconfig shows hardware once it is loaded correctly, is that right? But apart from the modules, what else do I need to do to get it showing up in ifconfig?

IPv6 Test Case for LinkSys Routers - Based on Ubuntu + Radvd + DHCPv6 - E1200v2 isn't ready for IPv6

Hello!
Here on this guide, you'll learn how to deploy your own Linux IPv6 Router, that can be used in ANY network, to give IPv6 connectivity to ANY ethernet device, including Windows, Mac, Ubuntu Server and Desktop, RedHat and, of course, LinkSys routers like E1200v2 and E2500 for its WAN interfaces.
I wrote this guide because I found a BUG on E1200v2, which doesn't work with IPv6 yet, already lost some money to figure this out.
That's it, when you see a E1200v2 box at the store, you can read: "* IPv6 Enabled", but that is not entirely true, since it does not work as expected.
Here on this post, it is a complete procedure to reproduce the problem.
NOTE: The model E2500 v1 does not suffer from this problem!
NOTE: This guide is very usefull if you have a LinkSys E2500 router and want to connect it directly into a Linux Router!
Who am I?
A.: I'm Thiago, I work in Brazil, for a company called iG (ig.com.br), I'm working here as a Network Engineer / SysAdmin and I have +10 years of experience with IPv4 networks + 5 years with IPv6.
* Brief
1- Install a Ubuntu 12.04.3, to act as your router, on a PC computer with two ethernet cards (eth0 will be Ubuntu's default route, eth1 will be used to connect LinkSys E1200v2);
2- Prepare your Ubuntu Router (very important step, read it carefully)
3- Connect E1200v2 directly into Ubuntu's eth1 ethernet card;
4- Connect a Windows PC at E1200v2 LAN port 1 (used to configure your E1200 with Cisco Connect everytime a reset is desired);
5- Reset (restore it from factory defaults) your E1200v2 router;
6- Install Cisco Connect in your Windows PC (LAN port 1);
7- Configure your E1200v2 as usual;
8- Browse the Internet (still IPv4);
9- Open Windows Command Prompt and type: ipconfig, ping, etc;
10- Open Google Chrome or Firefox and go to your E1200v2 Web Admin Interface at http://192.168.1.1/
11- Install a Ubuntu 12.04.3 Server connected at E1200v2 LAN port 2 to test IPv6 connectivity in deep, or;
12- Boot a Ubuntu Desktop 13.04 Live CD connected at E1200v2 LAN port 3 to test IPv6 connectivity in deep;
IMPORTANT NOTE:
* This tests will require IPv4 connectivity to the Internet, since the IPv6 blocks used on this example, are blocks used only for documentation (or small tests) porpuses, which means that those IPv6 tests we're about to do, will not reach the Internet (in IPv6), neighter be routed out from your E1200v2. But it is enough to prove that E1200v2 drops its clients IPv6 connectivity. Feel free to replace those IPv6 address with your current / valid IPv6 blocks (if you have a IPv6 /48 block from your ISP, you know what I'm talking about).
* Network Topology (Ubuntu Linux Router)
IPv6:
eth0
2001:db8:0:1::/64 = uplink allocation
2001:db8:0:1::1 = upstream router IP (Ubuntu's gateway IPv6)
2001:db8:0:1::2 = customer configured IP (your WAN uplink interface to provider - Ubuntu's eth0 IPv6 address)
eth1
2001:db8:1::/48 = statically routed subnet pointing at 2001:db8:0:1::2 that come from you IPv6-ISP
2001:db8:1::1 = your first IPv6 within your own infrastructure (Ubuntu's eth1 - E1200v2 directly connected here)
eth1:0
2001:db8:1:1::/64 = your first IPv6 /64 with Router Advertisement plus DHCPv6 running on Linux (radvd) (Ubuntu's eth1:0 - E1200v2 gets its WAN IPv6 address from this subnet)
2001:db8:1:1::1 = IP of your first /64 subnet, Radvd + DHCPv6 running here, Ubuntu as IPv6 router
IPv4:
eth0
192.168.10.0/24 = uplink allocation
192.168.10.1 = upstream router IP (Ubuntu's gateway IPv4)
192.168.10.2 = customer configured IP (your WAN uplink interface to provider - Ubuntu's eth0 IPv4 address)
eth1
192.168.20.1 = your E1200 will gets its WAN IPv4 address from this subnet - most common scenario for IPv4 wifi routers running inside enterprise environments today
* Complete procedure
1- Install a Ubuntu 12.04.3, to act as your router, on a PC computer with two ethernet cards
Install the following packages in your Ubuntu Router:
sudo apt-get install radvd isc-dhcp-server
2- Prepare your Ubuntu Router (very important step, read it carefully)
2.1- Ubuntu's file /etc/network/interfaces contents:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
# IPv6
iface eth0 inet6 static
address 2001:db8:0:1::2
netmask 64
gateway 2001:db8:0:1::1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 2001:4860:4860::8888
dns-search linksys.com
# IPv4
iface eth0 inet static
address 192.168.10.2
netmask 24
gateway 192.168.10.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 8.8.8.8 8.8.4.4
dns-search linksys.com
# The secondary network interface, E1200 LinkSys wifi-router is connected here (WAN port)
auto eth1
# IPv6
iface eth1 inet6 static
address 2001:db8:1::1
netmask 48
auto eth1:0
iface eth1:0 inet6 manual
up ip -6 address add 2001:db8:1:1::1/64 dev $IFACE
down ip -6 address del 2001:db8:1:1::1/64 dev $IFACE
# IPv6 /56 block routed to LinkSys E1200v2, it is delegated to it through Prefix Delegation using DHCPv6
# Uncomment it later when your E1200v2 gets its own IPv6 Internet IP Address, keep reading this guide
#up ip -6 route add 2001:db8:1:f00::/56 via 2001:db8:1:1::2000
# IPv4
iface eth1 inet static
address 192.168.20.1
netmask 24
2.2- Configure Ubuntu /etc/sysctl.conf file
Uncomment the following two lines on it:
net.ipv4.ip_forward=1
net.ipv6.conf.all.forwarding=1
After writting, run "sudo sysctl -p" to apply the changes.
2.3- Configuring Linux Router Advertisement daemon (radvd)
Your Linux Router Advertisement daemon running on Ubuntu, must have the following content:
# Ubuntu eth1
interface eth1
# Enable RA
AdvSendAdvert on;
# Enable clients getting their IPs from DHCPv6
AdvManagedFlag on;
AdvOtherConfigFlag on;
# Enable RA to the following subnet
prefix 2001:db8:1:1::/64
AdvOnLink on;
# When not allowing clients to auto-generate their IPv6 address (SLAAC), DHCPv6 will be used instead
AdvAutonomous off;
2.4- Configuring DHCPv6
Your isc-dhcp-server6 configuration file (/etc/dhcp/dhcpd6.conf) for IPv6 must have the following content:
ddns-update-style none;
default-lease-time 600;
max-lease-time 7200;
authoritative;
log-facility local7;
# Ubuntu eth1
# This is a very basic subnet declaration with Prefix Delegation enabled.
subnet6 2001:db8:1:1::/64 {
# Range for clients
range6 2001:db8:1:1::2 2001:db8:1:1::2000;
# Extra DHCP options
option dhcp6.name-servers 2001:4860:4860::8888, 2001:4860:4860::8844;
option dhcp6.domain-search "linksys.com";
  # The following line will delegate a subnet to LinkSys E1200v2,
  # using Prefix Delagation standards.
  # You'll be able to see this "Prefix Address" under "Status -> Local Network" E1200v2 menu.
prefix6 2001:db8:1:100:: 2001:db8:1:f00:: /56;
# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.
# Ubuntu eth0 - no DHCPv6 running but doesn't hurt to declare it here
subnet6 2001:db8:0:1::/64 {
Reference: http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/hints-daemons-isc-dhcp.html
2.5- Configuring DHCPv4
Your isc-dhcp-server configuration file (/etc/dhcp/dhcpd.conf) for IPv4 must have the following content:
ddns-update-style none;
default-lease-time 600;
max-lease-time 7200;
authoritative;
log-facility local7;
# Ubuntu eth1
# This is a very basic subnet declaration.
subnet 192.168.20.0 netmask 255.255.255.0 {
range 192.168.20.2 192.168.20.200;
option routers 192.168.20.1;
option domain-name "linksys.com";
option domain-name-servers 8.8.8.8, 8.8.4.4;
# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.
# Ubuntu eth0 - no DHCPv4 running but doesn't hurt to declare it here
subnet 192.168.10.0 netmask 255.255.255.0 {
* Reboot your Ubuntu Router to apply all the changes
After rebooting it, try to "ping 8.8.8.8" to make sure your Ubuntu Router have at least, IPv4 Internet connectivity.
NOTE: From this point, you'll be able to start testing IPv6 from behind your Ubuntu Router (i.e. from its eth1), if you connect a Ubuntu Desktop, a Mac or a Windows on Ubuntu's eth1, it will provide IPv4 and IPv6 address to that devices, including your E1200v2 WAN port...
3- Connect E1200v2 directly into Ubuntu's eth1 ethernet card;
Plug a RJ45 cable between Ubuntu eth1 ethernet card and E1200v2 WAN port.
4- Connect a Windows PC at E1200v2 LAN port 1
This Windows computer will be used to (re)configure your E1200v2 with Cisco Connect everytime a reset is desired.
5- Reset (restore it from factory defaults) your E1200v2 router;
Press and hold the reset button for about 10 seconds.
6- Install Cisco Connect in your Windows PC (LAN port 1);
Boot(reboot) Windows and install Cisco Connect on it.
7- Configure your E1200v2 as usual (by finishing Cisco Connect installation procedure);
After concluding this step, your Windows PC will have both IPv4 and IPv6 address, that come from E1200v2.
Windows gets its IPv4 from DHCP and IPv6 from SLAAC (main point of the problem), both provided by E1200v2.
NOTE: From this point, you'll be able to see the problem with E1200v2 internal RA daemon, you'll lose your IPv6 connectivity that come from E1200v2. But, lets keep testing it...
8- Browse the Internet (still IPv4);
That's it, try to browse google.com from your Windows PC, if Ubuntu Router can "ping google.com", Windows PC should be able to do it so.
9- Open Windows Command Prompt and type: ipconfig, ping, etc;
Run "ipconfig" to see your IPv4 and IPv6 address...
Run "ping 8.8.8.8" to see if you can reach the Internet...
10- Open Google Chrome or Firefox and open your E1200v2 Web Admin Interface at http://192.168.1.1/
Access your E1200v2 Web Admin and go to the "Status -> Router" menu.
Write down its Internet IPv6 address, it will be something like this:
IPv6 - Internet IP Address: 2001:db8:1:1::2000
NOTE: You can get this address at the Ubuntu Router itself, by reading the file /var/log/syslog (`grep pool' might help), for example:
# grep pool /var/log/syslog
Sep 24 00:47:13 ubuntu-router-1 dhcpd: Picking pool address 2001:db8:1:1::2000
Sep 24 00:47:13 ubuntu-router-1 dhcpd: Picking pool prefix 2001:db8:1:1::/56
You'll see the above message on your Ubuntu Router, right after turning on your E1200v2. Pool address is the IPv6 Internet IP Address of your E1200v2's WAN port, pool prefix is the delegated subnet to your E1200v2 router. After thatn, it will start to advertiser that block on its LAN ports and WiFi (which doesn't work as expected, there is a problem there, whithin E1200v2 itself.
11- Install a Ubuntu 12.04.3 Server connected at E1200v2 LAN port 2, to test IPv6 connectivity in deep;
Here is the most important test:
* Testing the IPv6 connectivity from E1200v2 LAN ports.
This test is very simple, we just need to try ping E1200v2's IPv6 Internet IP Address.
This Ubuntu Server will have the following content on its /etc/network/interfaces file:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
# IPv6 - SLAAC - No DHCPv6 client required - E1200v2 will kicks off this IPv6, and I don't know why...
iface eth0 inet6 auto
# IPv4 - Requires DHCPv4
iface eth0 inet dhcp
After this, your Ubuntu Server will be able to "ping 8.8.8.8" and "ping6 2001:db8:1:1::2000" (E1200v2 WAN IPv6 Address noted before).
To prove that E1200v2 have a problem with IPv6, try to ping it, just run:
mtr -n 2001:db8:1:1::2000
...And after a few minutes, Ubuntu Server will lose its IPv6 address, because E1200v2 is kicking it off.
You'll be able to see a lots of package loss going on "mtr -n 2001:db8:1:1::2000".
If you connect a Mac OSX on E1200v2 LAN por 3, for example, it will also lose its IPv6 from time to time.
Wireless clients connected at E1200v2, like Android, iPad, Windows, Mac and Ubuntu laptops, also loses its IPv6 (that come from E1200v2) from time to time.
You guys must note that the E1200v2 itself, ramdomly becomes unreacheable from its own LAN ports (via IPv6)!! Which is unnaceptable.
12- Boot a Ubuntu Desktop 13.04 Live CD connected at E1200v2 LAN port 3 to test IPv6 connectivity in deep;
Boot a Ubuntu Desktop connected at your LinkSys E1200v2 router, and open 2 Terminals, on each of it, you should run:
Terminal 1:
mtr -n 2001:db8:1:1::2000
Terminal 2:
sudo tail -f /var/log/syslog
You'll be able to see a lots of package loss going on "mtr -n 2001:db8:1:1::2000" after a few minutes AND at the syslog, you'll be able to see when you lose your IPv6, that come from E1200v2.
Conclusion
E1200v2 doesn't have a working IPv6 Router Advertisement service. Please Cisco, fix it!
The IPv4 from behind E1200v2 is fine, I'm using LinkSys products for about +10 years now... First time with problems like this but, IPv6 is more or like new and, problems are expected... Lets work on it?!
Best Regards,
Thiago

Try to use dhclient perhaps? Might I also suggest letting systemd deal with the dhcp issue and not NM. That may seem incongruous but it is possible NM is mis-handling the dhcp hand-off to the network card. I'm no guru but I got thinking about this when I saw this in your output:
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
It is very possible that I'm mis-interpreting this information so please take it with a boulder of salt.

[solved] dhcpcd: timed out after reinstalling arch

Hi erveryone!
After reinstalling arch I can't connect to my wireless network anymore.
Typed:
wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant_vienna.conf
dhcpcd wlan0
Got:
dhcpcd: wlan0: waiting for carrier
dhcpcd: timed out
wpa_supplicant_vienna.conf (ssid and psk deleted):
network={
ssid=""
proto=RSN
pairwise=CCMP TKIP
key_mgmt=WPA-PSK
psk=
I reinstalled arch on my netbook at the same time and there's everything working fine (even with the same wireless-card). The only difference between the two systems is that my laptop has an i686 installation while on my netbook I've installed x86_64.
Things I've tried:
+ Update the system via wired-connection (mirrors.kernel.org) --> the download never gets faster than 10KB/s (?).
+ Configure the wireless interface via netcfg --> same problem
+ Reinstalled again and only changed LOCALE in /etc/rc.conf --> same problem
So you may see, I have no idea what I could be doing wrong and hope that theres anybody out there who knows what to do!
P.S. Well, i have now by-passed my problem.
1.) Created a list of packages installed during system-update on my netbook.
2.) In this list I changed package-name-x86_64.tar.gz to package-name-i686.tar.gz
3.) Downloaded the list with wget.
4.) Ccopied the packages to my laptop
5.) Created a local repository and made a system-update.
Last edited by kronfeld (2010-05-04 17:34:43)

Hi trusktr
This might seem stupid but are you sure you are using "eth0" and not "eth1" etc.? As an example I have two on-board lans and I'm plugged into eth1. I had to change rc.conf as it defaults to using eth0.
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth1="dhcp"
INTERFACES=(eth1)
Since I am using eth1 and not eth0 here is what I get when I try:
ifconfig eth0:
eth0 Link encap:Ethernet HWaddr 00:04:4B:00:88:0E
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:23 Base address:0x6000
Look familiar?
I'm not saying this is the case but it could be something as simple as that.
ifconfig -a
should show you how many lans you have.
Thought I would drop the obvious first in case that's all it is.

Disk by uuid

In Grub, the root device is specified by UUID, example:
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/8def79a8-3257-4412-a9d3-fe95a55fcb06 ro
After I built my custom kernel, which doesn't need an initrd, booting using UUIDs no longer worked (I got a kernel panic saying that it could not mount the root fs). Using the traditional /dev/sdX way works fine however.
Please can someone verify that the usage of UUIDs is only necessary when using an initrd (because the initrd might change the /dev/sdX naming)? If it's not, then in what way do I need to change my kernel config so it can handle UUIDs?
Thanks!
Last edited by roog (2008-08-13 05:42:53)

roog wrote:Please can someone verify that the usage of UUIDs is only necessary when using an initrd (because the initrd might change the /dev/sdX naming)? If it's not, then in what way do I need to change my kernel config so it can handle UUIDs?
The need for uuids is because they are a naming system that almost guarantees that that uuid belongs to that partition: if you reformat that partition, then you can't boot the new partition using a uuid, since that isn't the same partition. /dev/sdx naming would try to boot the new one.
That is more an issue if you have multiple disks and switch them, or if you have two hdd controllers whose modules cannot be loaded in a predefined order (people see this more often with which network device is eth0, which is eth1), or if the driver changes between releases to call a disk /dev/sda instead of /dev/hda, or some other scheme.
In any case it is a more robust system to use uuids, but the other way works too!
The code that goes into the ata_piix might have some info, though something might pop up when you run diff (vimdiff?) on your config and arch's config.

I think I need help with driver (software) settings for D110a

I think I need help with driver (software) settings for D110a all-in-one
Product: D110a all-in-one
OS: Windows XP Professional
Error messages: None
Changes before problem appeared: None--new installation
The quality of photo images (mostly JPG files) in printouts is awful even though the files display beautifully on the PC screen. I am using
IrfanView software for displaying/printing. As far as I can tell, IrfanView is not the problem.
When I print the same images on a Deskjet 5150 attached to a different PC also running XP Pro and IrfanView, the quality of the printouts is at
least acceptable, Some would probably say good or very good.
It's dificult to explain in words the problem with the printouts. A picture of really pretty vegetables (squashes, tomatoes, watermelon, etc) comes
out much too red. Moreover, the red, which appears shaded on the screen, seems to be all one shade in the D110a printouts.
Something similar happens to a view of a huge tree in full leaf. On screen, there are subtle variations in the "greenness" of the leaves. In the
printout, all green is the same shade. In the same printout, the trunk of the tree is all a single shade of grey. It isn;t even obvious that the
trunk is a round, solid object.
I liken the effect to audio that disappears entirely when you lower the volume and gets clipped into square waves in even moderately loud passages.
I don't know whether the D110a driver software permits adjusting the parameters that appear to be set incorrectly, and if adjustments are possible,
how I would identify which parameters to adjust, how I would access them, or how I would adjust them. I'm hoping that someone can help. Thanks.
I forgot to mention that I have used the diagnostic application and it tells me that there are no problems.
e-mail me at [email protected]

brazzmonkey wrote:
Hi everyone,
I noticed the following message when network starts on my gateway
Warning: This functionality is deprecated.
Please refer to /etc/rc.conf on how to define a single wired
connection, or use a utility such as netcfg.
Then I realized the way network settings should be written in rc.conf has changed. But I can't figure out how this should be done.
Currently, my set up is the following (old way):
INTERFACES=(eth0 eth1)
eth0="dhcp"
eth1="eth1 192.168.0.10 netmask 255.255.255.0 broadcast 192.168.0.255"
ROUTES=(!gateway)
eth0 is on DHCP because the IP is dynamically assigned my ISP.
eth1 has a fix IP because it's on the LAN side.
No problem to use DHCP on eth0 with the new settings.
But for eth1, I don't know what I am supposed to write for gateway.
Wiki isn't clear on that one either, and it looks like many articles still refer to the old way.
Any guidance appreciated, thanks.
brazzmonkey,
you can't define 2 interfaces the old way (even though I saw some tricky workaround somewhere in the forums).
Use, f.e., netcfg:
Comment your old lines.
In /etc/rc.conf insert:
NETWORKS=(Eth0-dhcp Eth1-static)
DAEMONS=(..... !network @net-profiles ....)
In /etc/network.d create 2 files:
First one is named Eth0-dhcp.
Contents:
CONNECTION="ethernet"
DESCRIPTION="Whatever text"
INTERFACE=eth0
HOSTNAME="your hostname"
IP="dhcp"
DHCP_TIMEOUT=15
Second one is named Eth1-static.
Contents:
CONNECTION='ethernet'
DESCRIPTION='whatver'
INTERFACE='eth1'
HOSTNAME='hname'
IP='static'
ADDR='192.168.0.10'
GATEWAY='192.168.0.1' # your gateway IP
DNS=('192.168.0.1') # your DNS server
The names Eth0-dhcp and Eth1-static are not magic. They just must be the same in rc.conf and in /etc/network.d.
Hope it helps.
mektub
PS: netcfg must be installed.
Last edited by Mektub (2011-07-20 14:07:05)

[Solved] Netcfg switches between interfaces

Hello,
I switched to netcfg, to get a pure systemd install.
How ever, sometimes the netcfg can't bring up the interface even though it used that interface before.
It's like netcfg are switching between what interface it can use. Sometimes it's eth0 other times eth1.
So when I boot and don't have any network connection, I change the config files to use the other interface (ex. eth1) and netcfg can connect.
How can this be?
configs:
/etc/network.d/mynetwork
CONNECTION='ethernet'
DESCRIPTION='A basic static ethernet connection using iproute'
INTERFACE='eth1'
IP='static'
ADDR='192.168.1.3'
#ROUTES=('192.168.0.0/24 via 192.168.1.2')
GATEWAY='192.168.1.1'
DNS=('dns1', 'dns2)
## For IPv6 autoconfiguration
#IP6=stateless
## For IPv6 static address configuration
#IP6='static'
#ADDR6=('1234:5678:9abc:def::1/64' '1234:3456::123/96')
#ROUTES6=('abcd::1234')
#GATEWAY6='1234:0:123::abcd'
/etc/conf.d/netcfg
# Enable these netcfg profiles at boot time.
# - prefix an entry with a '@' to background its startup
# - set to 'last' to restore the profiles running at the last shutdown
# - set to 'menu' to present a menu (requires the dialog package)
# Network profiles are found in /etc/network.d
NETWORKS=(mynetwork)
# Specify the name of your wired interface for net-auto-wired
WIRED_INTERFACE="eth1"
# Specify the name of your wireless interface for net-auto-wireless
#WIRELESS_INTERFACE="wlan0"
# Array of profiles that may be started by net-auto-wireless.
# When not specified, all wireless profiles are considered.
#AUTO_PROFILES=("profile1" "profile2")
Last edited by KLIM (2012-12-06 14:22:23)

Did you checked for netcfg.service is enabled (systemd) ?
BTW, I see a missing single quote on DNS line : DNS=('dns1', 'dns2)
You may check these forum posts :
"[SOLVED] Netcfg.service always failing." @ https://bbs.archlinux.org/viewtopic.php?id=148079
"Systemd and Netcfg" @ https://bbs.archlinux.org/viewtopic.php?id=151662
"netcfg/systemd not bringing up eth0 (static profile)" @ https://bbs.archlinux.org/viewtopic.php?id=147300
"[SOLVED] netcfg fails at boot" @ https://bbs.archlinux.org/viewtopic.php?pid=1200518
And this wiki entry about netcfg @ https://wiki.archlinux.org/index.php/Netcfg

[SOLVED] Need to manually toggle rc.d/network for network card to work

I installed (or actually re-installed) Arch yesterday and have an unusual problem. After boot, I don't have internet connection and I think that the network card isn't active either because i can't see light in my switch's panel.
I have managed to get the connection to work but the procedure is pretty strange.
There's a line "interface=eth1" in my /etc/rc.conf. I change it to "interface=eth0" and execute "/etc/rc.d/network restart". For some reason it prints "RTNETLINK answers: File exists" at this point.
Now there's no internet connection nor activity in switch's panel. I change "interface=eth1" back to /etc/rc.conf and execute "/etc/rc.d/network restart". Now i can connect to internet and there's a green light in switch's panel.
According to lspci my two network cards are named "NVidia Corporation nForce2 Ethernet Controller (rev a1)"(integrated into motherboard) and "Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)."
I already thought that maybe they are just loading in different orders at boot so I added their modules into rc.conf but it didn't do the trick. Googling about that RTNETLINK thing gave some results, but if understood them correctly, they are doing something similar what I have been doing.
Last edited by mylvari (2011-10-28 08:39:52)

I don't know if this card is Realtek based, but wiki's advice for Realtek cards worked. https://wiki.archlinux.org/index.php/Ne … _WOL_issue

Query on adding new node to existing 2 node cluster

Hi experts
current environment
Oracle VM 2 Node RAC cluster
Oracle 11G 11.2.0.3.0
Oracle 11g rel 2 GI
on current 2 node cluster we have GI and RAC db configured
Nodes: vmorarac1,vmorarac2
we shutdown vmorarac1 to clone it to vmorarac5
on new node I have changed the hostname to vmorarac5
In /etc/sysconfig/network-scripts/ifcfg-eth0 change ip to new ip and same for /etc/sysconfig/network-scripts/ifcfg-eth1
152.144.199.210,152.144.199.211
mad echanges to /etc/hosts on vmorarac1/2 for 2 new IP address assigned to vmorarac5
152.144.199.171 vmorarac1.pbi.global.pvt vmorarac1
192.168.2.30 vmorarac1-priv.pbi.global.pvt vmorarac1-priv
152.144.199.184 vmorarac1-vip.pbi.global.pvt vmorarac1-vip
152.144.199.172 vmorarac2.pbi.global.pvt vmorarac2
192.168.2.31 vmorarac2-priv.pbi.global.pvt vmorarac2-priv
152.144.199.185 vmorarac2-vip.pbi.global.pvt vmorarac2-vip
152.144.199.210 vmorarac2.pbi.global.pvt vmorarac2
192.168.2.32 vmorarac2-priv.pbi.global.pvt vmorarac2-priv
152.144.199.211 vmorarac2-vip.pbi.global.pvt vmorarac2-vip
152.144.199.201 vmorarac-scan.pbi.global.pvt
Query is is that all ok to reboot the new node to reflect changes as below and change the hostname to vmorarac2
152.144.199.210 vmorarac2.pbi.global.pvt vmorarac2
192.168.2.32 vmorarac2-priv.pbi.global.pvt vmorarac2-priv
152.144.199.211 vmorarac2-vip.pbi.global.pvt vmorarac2-vip
hostname change in /etc/sysconfig/network
please let me know
On new node vmorarac5, there is alreay software for RAC DB and GUI cloned from vmorarac1
addnode.sh is used to add existing node, but as part of pre-requisite configuratoin is there any config step missing
thanks

The only thing you want "cloned" is the base OS install... The GI home directory, the oraInventory and a whole lot of other stuff is configured at addNode time or cluster install time. I would say that proceeding with your current plans will corrupt your clusterware. You really need to STOP LISTENING to the SA's and START reading the documentation on how to add a node to a cluster. Simply changing the hostname IS NOT a supported "feature".
Start with a CLEAN OS. Configure shared devices, networks, /etc/hosts, memory and packages.
Follow the instructions for addNode.
Doing this any other way has the potential to corrupt your entire cluster.

Can't get a internet lease. Dhcpcd and manual

After two different problems with my wireless card i have finally almost gotten it to work. I am capable of connecting to my router, but every time i run dhcpcd eth1 it times out at broadcasting for a lease
rc.conf Network part
eth1="dhcp"
eth0="dhcp"
interfaces=(eth1 eth0)
gateway="default gw 192.168.2.1"
ROUTES=(gateway)
iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11bg ESSID:"sputnik"
Mode:Managed Frequency:2.457 Acces Point:00:25:3C:**:56:** (stars are to hide what i think is mac address...)
Bit Rate:54Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:yadda yadda yadda Security mode:open
Power Management:off
Link Quality=86/100 Signal level=-44 dBm Noise level=-85 dBm
Rx invalid nwid:0 Rx invalid crypt:1443 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Miseed beacon:8
I've also tried the
ifconfig wlan0 192.168.0.2
route add default gw 192.168.0.1
example from https://wiki.archlinux.org/index.php/Wi … nual_setup but after when i ping google i get unknown host. So maybe im just missing a step. Also if you need any command outputs just ask and i'll respond once i notice.
Last edited by Foxhead (2010-12-28 07:36:36)

Hi,
Just after a quick read:
gateway="default gw 192.168.2.1"
and
ifconfig wlan0 192.168.0.2
Check - perhaps it can help - the two last entries in the IP addresses. As an example 192.168.1.2 and 192.168.2.1 may not be able to "see" each other...one of the two needs to be changed...the choice is yours
Had the same with a print server, it came with IP address 192.168.0.1, my LAN is at 192.168.1.x, noticed the diffrerence?
Possibly a networking thing...
Wellness
Thor
Last edited by Thor@Flanders (2010-12-28 13:42:02)

Eth0 changes to eth1

Similar Messages

Maybe you are looking for