02/14/2013 03:45 AM, poma wrote:
On 02/14/13 01:14, Rick Stevens wrote:
On 02/13/2013 02:42 PM, Mike Wright issued this missive:
Hi all,
I need to be able to identify which networks are on which NICs on a
multi-homed box.
There is a program that, when given an IP, will cause the associated
NI
On Thu, Feb 14, 2013 at 6:45 AM, poma wrote:
>
> ethtool -p eth-r8169
> Cannot identify NIC: Operation not supported
> ethtool -p eth-forcedeth
> Cannot identify NIC: Operation not supported
> ethtool -p eth-usbnet
> Cannot identify NIC: Operation not supported
>
I used the ifconfig command to d
On 02/14/13 01:14, Rick Stevens wrote:
> On 02/13/2013 02:42 PM, Mike Wright issued this missive:
>> Hi all,
>>
>> I need to be able to identify which networks are on which NICs on a
>> multi-homed box.
>>
>> There is a program that, when given an IP, will cause the associated
>> NIC's leds to blin
On 02/13/2013 02:42 PM, Mike Wright issued this missive:
Hi all,
I need to be able to identify which networks are on which NICs on a
multi-homed box.
There is a program that, when given an IP, will cause the associated
NIC's leds to blink, whether or not it has a physical connection to an
ether
Mike Wright writes:
Hi all,
I need to be able to identify which networks are on which NICs on a multi-
homed box.
There is a program that, when given an IP, will cause the associated NIC's
leds to blink, whether or not it has a physical connection to an ethernet
cable. Used for debuggin
Hi all,
I need to be able to identify which networks are on which NICs on a
multi-homed box.
There is a program that, when given an IP, will cause the associated
NIC's leds to blink, whether or not it has a physical connection to an
ethernet cable. Used for debugging.
Thought it was ping
