On 11/27/06, Mrugesh Karnik [EMAIL PROTECTED] wrote:
On Tuesday 28 November 2006 07:31, Richard Fish wrote:
can see a 75-persistent-net-generator.rules file in there..
Hmm, not sure how I got a 70-persistent-net.rules. There is some
interaction between that and
On Wednesday 29 November 2006 17:33, Richard Fish wrote:
On 11/27/06, Mrugesh Karnik [EMAIL PROTECTED] wrote:
On Tuesday 28 November 2006 07:31, Richard Fish wrote:
can see a 75-persistent-net-generator.rules file in there..
Hmm, not sure how I got a 70-persistent-net.rules. There is
On Wednesday 29 November 2006 23:03, Richard Fish wrote:
The upshot of this is this: by far the easiest way to solve the
net-naming problem is to run
/lib/udev/write_net_rules all_interfaces
This will generate the rules for all interfaces, and then you can just
edit the file to change the
FWIW, I also upgraded and find that my laptop, which previously had eth0
and eth1 for its two cards (one wired and one wireless) now has eth0 and
eth2.
After editing my scripts and configurations (e.g. wpa_supplicant startup
and kismet conf), things seem to work fine.
HTH, newbie
--
On Mon, 27 Nov 2006 09:36:38 -0500, 7v5w7go9ub0o wrote:
FWIW, I also upgraded and find that my laptop, which previously had
eth0 and eth1 for its two cards (one wired and one wireless) now has
eth0 and eth2.
Do you have IEEE1394_ETH1394 set in your kernel? If so, it's possible
that eth1 is
On 27/11/06, 7v5w7go9ub0o [EMAIL PROTECTED] wrote:
FWIW, I also upgraded and find that my laptop, which previously had eth0
and eth1 for its two cards (one wired and one wireless) now has eth0 and
eth2.
After editing my scripts and configurations (e.g. wpa_supplicant startup
and kismet conf),
On 11/27/06, Mrugesh Karnik [EMAIL PROTECTED] wrote:
# ethernet devices
ACTION==add, SUBSYSTEM==net, SYSFS{address}==00:13:d3:60:4a:a5,
NAME=eth0
ACTION==add, SUBSYSTEM==net, SYSFS{address}==00:0d:88:45:c1:c9,
NAME=eth1
No go. They didn't swap.
Just in case, you did make those 2, not 4,
On Tuesday 28 November 2006 04:16, Richard Fish wrote:
On 11/27/06, Mrugesh Karnik [EMAIL PROTECTED] wrote:
# ethernet devices
ACTION==add, SUBSYSTEM==net, SYSFS{address}==00:13:d3:60:4a:a5,
NAME=eth0
ACTION==add, SUBSYSTEM==net, SYSFS{address}==00:0d:88:45:c1:c9,
NAME=eth1
No
On 11/27/06, Mrugesh Karnik [EMAIL PROTECTED] wrote:
udevd-event[3110]: rename_netif: error changing net interface name eth0_rename
to eth1: No such device.
Hmm, haven't seen this error, but these rules (based on
70-persistent-net.rules) might work better:
SUBSYSTEM==net,
On Tuesday 28 November 2006 06:38, Richard Fish wrote:
On 11/27/06, Mrugesh Karnik [EMAIL PROTECTED] wrote:
udevd-event[3110]: rename_netif: error changing net interface name
eth0_rename to eth1: No such device.
Hmm, haven't seen this error, but these rules (based on
On 11/27/06, Mrugesh Karnik [EMAIL PROTECTED] wrote:
On Tuesday 28 November 2006 06:38, Richard Fish wrote:
On 11/27/06, Mrugesh Karnik [EMAIL PROTECTED] wrote:
udevd-event[3110]: rename_netif: error changing net interface name
eth0_rename to eth1: No such device.
Hmm, haven't seen this
On Tuesday 28 November 2006 07:31, Richard Fish wrote:
can see a 75-persistent-net-generator.rules file in there..
Hmm, not sure how I got a 70-persistent-net.rules. There is some
interaction between that and 75-persistent-net-generator.rules (and
the /lib/udev/write_net_rules script), but
12 matches
Mail list logo
