Bruce Dubbs wrote:
I have the hardware, but I don't use it that often. What do I need to
do to check the problem/solution.
Let's try and reproduce the problem first. To do that, create a rule
based either on MAC address or on PCI bus position (i.e., any of the two
methods in the book) that r
Alexander E. Patrakov wrote:
> One more issue is with Atheros wi-fi driver: it reportedly creates two
> interfaces with identical MAC addresses, and our rules go crazy. Since I
> don't have the corresponding hardware, I can't offer a working solution.
I have the hardware, but I don't use it that
Bryan Kadzban wrote:
Alexander E. Patrakov wrote:
(20:29:08) Tizer: Interface eth0 doesn't exist... why not?
Here's what we have today:
These rules will always rename the network cards to "realtek" and
"intel", independently of the original numbering provided by the
kernel (i.e.: the origin
Alexander E. Patrakov wrote:
> (20:29:08) Tizer: Interface eth0 doesn't exist... why not?
Here's what we have today:
> These rules will always rename the network cards to "realtek" and
> "intel", independently of the original numbering provided by the
> kernel (i.e.: the original "eth0" and "et
IRC log illustrating the problem is pasted below.
(20:28:38) Tizer: Hi patrakov
(20:28:46) patrakov: Hello Tizer
(20:28:46) Tizer: networking woes...
(20:28:50) ***Joe|afk wakes
(20:28:51) Joe|afk: hi patrakov
(20:28:54) Joe|afk теперь известен как Joe
(20:28:57) patrakov: Hello Joe.
(20:29:08) T
