| 1 |
This is giving me some problems on a laptop - I have a 70-persistent-net |
| 2 |
rules file which attempts to pin eth0 to the ethernet interface, and |
| 3 |
eth1 to the wireless interface. This works fine on a cold boot or |
| 4 |
hibernate to disk (sus2) - without it the allocation wanders between the |
| 5 |
interfaces at will (this also occurs on a number of multi-interface |
| 6 |
servers I have - a real pain!) |
| 7 |
|
| 8 |
Recently however, if I attempt to "echo mem > /sys/power/state" (aka |
| 9 |
instant stop/start!!) it resumes with one of the interfaces having a |
| 10 |
name of "ethx_renam" and of course no network. |
| 11 |
|
| 12 |
Is it possible to: |
| 13 |
a. fix so it worked as previously - i.e., resumed on the same interface |
| 14 |
in working condition |
| 15 |
|
| 16 |
or |
| 17 |
b. able to rename the interface so I can script a fix to run after |
| 18 |
resume. |
| 19 |
|
| 20 |
and is it a bug (so I will bugzilla it) or is it a feature :( |
| 21 |
|
| 22 |
BillK |
| 23 |
|
| 24 |
|
| 25 |
|
| 26 |
On Mon, 2007-06-11 at 17:20 -0600, Trenton Adams wrote: |
| 27 |
> Yes, everything worked just fine. It indeed switched my ethernet to a |
| 28 |
> different interface (eth1). Not a problem. |
| 29 |
> |
| 30 |
> On 6/11/07, Redouane Boumghar <redouane.boumghar@×××××××××.fr> wrote: |
| 31 |
> > Hello Trenton, |
| 32 |
> > |
| 33 |
> > Ok it's been a month since this thread but... |
| 34 |
> > I found myself too oftenly in front of unsolved archived threads. |
| 35 |
> > |
| 36 |
-- |
| 37 |
gentoo-user@g.o mailing list |
Archives