[Bug 118880] Re: network is starting with eth2 instead of eth1 on second nic

2007-06-05 Thread Mischko
I found it is a problem with a NIC module in the kernel. I think I have
it fixed now.  Sorry to bother.

I changed status to Rejected.  I don't see another good way to close the
bug in this case and I'm hoping that's the "correct" way.


** Changed in: Ubuntu
   Status: Unconfirmed => Rejected

-- 
network is starting with eth2 instead of eth1 on second nic
https://bugs.launchpad.net/bugs/118880
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 118880] network is starting with eth2 instead of eth1 on second nic

2007-06-05 Thread Mischko
Public bug reported:

I have two NIC's on my machine.  eth0 is to the Cable Modem.  eth1 is to the 
LAN.
When I rebooted, the second one did not come up.  eth2 came up instead (in 
"roaming mode") and eth1 won't come up. 
When I do /etc/init.d/networking restart:

[EMAIL PROTECTED]:/etc/network# /etc/init.d/networking restart
 * Reconfiguring network interfaces...  
  There is already 
a pid file /var/run/dhclient.eth0.pid with pid 9004
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:1a:92:59:c7:33
Sending on   LPF/eth0/00:1a:92:59:c7:33
Sending on   Socket/fallback
DHCPRELEASE on eth0 to 172.19.73.16 port 67
ath0: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.ath0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
ath0: ERROR while getting interface flags: No such device
ath0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up ath0.
wlan0: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.wlan0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
wlan0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up wlan0.
eth1: ERROR while getting interface flags: No such device
SIOCSIFADDR: No such device
eth1: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
eth1: ERROR while getting interface flags: No such device
Failed to bring up eth1.
There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:1a:92:59:c7:33
Sending on   LPF/eth0/00:1a:92:59:c7:33
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPOFFER from 10.96.192.1
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 10.96.192.1
bound to 70.162.26.204 -- renewal in 32646 seconds.

My /etc/network/interfaces file:
more /etc/network/interfaces
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0


iface eth0 inet dhcp
address 192.168.2.50
netmask 255.255.255.0
gateway 192.168.2.1


iface eth1 inet static
address 192.168.0.1
netmask 255.255.255.0


auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

auto eth1


auto eth0


This file is auto-generated and I haven't edit'd it at all.
Of course, this causes problems with things like DHCP3 server that are binding 
to interface eth1.

** Affects: Ubuntu
 Importance: Undecided
 Status: Unconfirmed

-- 
network is starting with eth2 instead of eth1 on second nic
https://bugs.launchpad.net/bugs/118880
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 81170] Re: [feisty] etodo conduit times out when syncing with a palm device

2007-05-17 Thread Mischko
I have seen the same bug with the Handspring Treo 700. Same symptoms,
etc.

-- 
[feisty] etodo conduit times out when syncing with a palm device
https://bugs.launchpad.net/bugs/81170
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs