03-21-2012
How can I find which NIC is used to talk to a given host (except traceroute)
Hi all,
I'm having some trouble identifying what route is being used to talk to a target host. I can figure it out by looking at the routing tables but I want to automate this and don't much feel like scripting the network mask logic when I'd think there'd be a way to have the OS do it for me.
I tried using traceroute and looking for the "Multiple interfaces found, using..." message, but that fails for some zones (no raw sockets).
Does anyone know of another way to display the first hop in the route (ie the NIC name or the NIC IP)?
Thanks in advance,
10 More Discussions You Might Find Interesting
1. Solaris
All,
I see that there are 2 nic card available . How can I know all the details about these 2 nic cards.
-rw-r--r-- 1 root root 10 Apr 16 15:00 hostname.bge0
-rw-r--r-- 1 root other 17 Apr 22 08:56 hostname.bge2
please let me know
thanks
-prasad (4 Replies)
Discussion started by: p4cldba
4 Replies
2. UNIX for Advanced & Expert Users
I do a ssh to remote host(A1) from local host(L1). I then ssh to another remote(A2) from A1.
When I do a who -m from A2, I see the "connected from" as "A1".
=> who -m
userid pts/2 2010-03-27 08:47 (A1)
I want to identify who is the local host who initiated the connection to... (3 Replies)
Discussion started by: gomes1333
3 Replies
3. Solaris
Greetings Forumers!
I am running into an issue with multiple zones on an M5000 with 2 NICs. The NICs are on separate VLANs. These zones are using the 2 NICs to communicate with other systems but when they need to communicate with a zone on the same system, but different NIC, the application... (9 Replies)
Discussion started by: bluescreen
9 Replies
4. AIX
Hi All,
How can I find out which is ETH5 on my AIX P5 system. I have about seven different NIC card on this. I did move the cable to each one but still I was not able to see the link light up when I did netstat -v
Any idea?
Thanks. (2 Replies)
Discussion started by: samnyc
2 Replies
5. Solaris
I have a Sun Blade 2500 with SUN 5.9 OS installed. I have one NIC built-in which is working fine.
I insert another new NIC in the machine with four RJ45 connector options(means four NICs in one Card). The problem is i am not able to see the new NIC
Thanks (13 Replies)
Discussion started by: z_haseeb
13 Replies
6. Solaris
i am using solaris 10 and i am able to ping all the hosts but i am not able to traceroute any of them. how to fix this? (9 Replies)
Discussion started by: chidori
9 Replies
7. Solaris
I couldn't install my nic in solaris 10. I compiled and added
the driver but failed to attach the driver and ifconfig output
shows only loopback dev. Please see the following output and tell
me whether my nic has been detected and why the driver failed to
attach?
My nic is detected in linux... (0 Replies)
Discussion started by: vectrum
0 Replies
8. Red Hat
Dear All
I want tune my NIC's rps, rfs and xps value.
In my system I have two NIC (eth0, eth1) and I have a bond0 ( eth0, eth1).
Here is the question? Which device should I modify ?
eth0 and eth1? or just modify bond0 or modify all device (eth0, eth1, bond0)
Any advice is welcome.... (0 Replies)
Discussion started by: nnnnnnine
0 Replies
9. Solaris
Dear,
I hope you all will be ok.
I have an issue with Solaris box running on x86 Blade.
I am unable to ping a node neither traceroute. I am able to do traceroute from oce0:6 port which have IP and subnet of same type which oce0:1 has.
details are as follows:
Problem:
root@rinams02:/#... (3 Replies)
Discussion started by: khaniqshahid
3 Replies
10. Linux
Hello Admins,
My ask is how can I add two different subnet IPs to same box with two different gateways?
The issue is I can connect to the box when I am on ethernet LAN, but I am not able to connect to the same IP when I am on wifi. The server is RHEL 7 VM on vmware.
How can I get connected... (4 Replies)
Discussion started by: snchaudhari2
4 Replies
LEARN ABOUT MOJAVE
traceroute6
TRACEROUTE6(8) BSD System Manager's Manual TRACEROUTE6(8)
NAME
traceroute6 -- print the route IPv6 packets will take to a network node
SYNOPSIS
traceroute6 [-dIlnNrvU] [-f firsthop] [-g gateway] [-m hoplimit] [-p port] [-q probes] [-s src] [-w waittime] target [datalen]
DESCRIPTION
The traceroute6 utility uses the IPv6 protocol hop limit field to elicit an ICMPv6 TIME_EXCEEDED response from each gateway along the path to
some host.
The only mandatory parameter is the destination host name or IPv6 address. The default probe datagram carries 12 bytes of payload, in addi-
tion to the IPv6 header. The size of the payload can be specified by giving a length (in bytes) after the destination host name.
Other options are:
-d Debug mode.
-f firsthop
Specify how many hops to skip in trace.
-g gateway
Specify intermediate gateway (traceroute6 uses routing header).
-I Use ICMP6 ECHO instead of UDP datagrams.
-l Print both host hostnames and numeric addresses. Normally traceroute6 prints only hostnames if -n is not specified, and only numeric
addresses if -n is specified.
-m hoplimit
Specify maximum hoplimit, up to 255. The default is 30 hops.
-n Do not resolve numeric address to hostname.
-N Use a packet with no upper layer header for the probes, instead of UDP datagrams.
-p port
Set UDP port number to port.
-q probes
Set the number of probe per hop count to probes.
-r Bypass the normal routing tables and send directly to a host on an attached network. If the host is not on a directly-connected net-
work, an error is returned. This option corresponds to the SO_DONTROUTE socket option; it can be used to ping a local host through
an interface that has no route through it (e.g., after the interface was dropped by a routing daemon).
-s src Src specifies the source IPv6 address to be used.
-U Use UDP datagrams for the probes. This is the default.
-v Be verbose.
-w waittime
Specify the delay time between probes.
This program prints the route to the given destination and the round-trip time to each gateway, in the same manner as traceroute.
Here is a list of possible annotations after the round-trip time for each gateway:
!N Destination Unreachable - No Route to Host.
!P Destination Unreachable - Administratively Prohibited.
!S Destination Unreachable - Not a Neighbour.
!A Destination Unreachable - Address Unreachable.
! This is printed if the hop limit is <= 1 on a port unreachable message. This means that the packet got to the destination, but
that the reply had a hop limit that was just large enough to allow it to get back to the source of the traceroute6. This was
more interesting in the IPv4 case, where some IP stack bugs could be identified by this behaviour.
RETURN VALUES
The traceroute6 utility will exit with 0 on success, and non-zero on errors.
SEE ALSO
ping(8), ping6(8), traceroute(8)
HISTORY
The traceroute6 utility first appeared in WIDE hydrangea IPv6 protocol stack kit.
BSD
May 17, 1998 BSD