|
From: Renaud (R. O. <re...@ol...> - 2006-05-30 23:46:31
|
On Tuesday 30 May 2006 16:54, my mailbox was graced by a missive
from Franck Horlaville <fh....@qu...> who wrote:
> but on a live installation in a super-crowded rack with all the
> labels obsolete and the cables difficult to follow this suggestion is
> what I needed:
>
> ethtool -p ethN where N=3D0,1,2 etc.
>
> It works beautifully indeed and it reports when the card doesn't
> support the function.
>
> so for now I guess I don't need anything more :-D
>
> it also has the advantage to work 1000 km away by telephone "look at
> the network cards, I'm going to make one blink - that's the one you
> want to blabla"
[root@ron images]# ethtool -p eth1
Cannot identify NIC: Operation not supported
Does not help.
So we'll go back to another method I used this afternoon after=20
re-motherboarding my firewall:
Configures green, orange and red as 192.168.1.254, 192.168.2.254 and=20
192.168.3.254.
=46rom the neighbouring box (195.168.1.1) I tried the various outlets and p=
inged=20
the firtst IP until I found which one it was.
Changed neighbouring box IP to 192.168.2.1 and found the second socket, and=
=20
assigning the third was trivial.
=20
Cheers,
=20
Ron.
=2D-
Hindsight is an exact science.
=20
-- http://www.olgiati-in-paraguay.org --
|