Hi,

>    i'm experiencing some errors with dhcpcd-2.0.0. When i try to run
> net.eth1 to start the a wireless device, dhcpcd stops with errors. In
> /var/log/dhcpcd.log i can see:
>
> dhcpStart: interface eth1 is not Ethernet or 802.2 Token Ring
>

it seems all related to the fact that when running

# ifconfig -a

eth0      Link encap:UNSPEC  HWaddr
00-C0-9F-00-00-1C-A1-53-00-00-00-00-00-00-00-00
          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)

eth1      Link encap:Ethernet  HWaddr 00:C0:9F:3B:9F:45
          inet addr:192.168.0.3  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5616 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5377 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6306862 (6.0 Mb)  TX bytes:657471 (642.0 Kb)
          Interrupt:6

eth2      Link encap:Ethernet  HWaddr 00:0E:35:44:5D:52
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:8689 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1299 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:10 Base address:0x6000 Memory:d0214000-d0214fff

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:300 (300.0 b)  TX bytes:300 (300.0 b)

eth1 is my ethernet card while eth2 is the wireless interface. What about eth0?
I've nothing set on udev local rules? Where did it come from?

Regards,
MC

-- 
gentoo-user@gentoo.org mailing list

Reply via email to