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
TALK(1) BSD General Commands Manual TALK(1)
NAME
talk -- talk to another user
SYNOPSIS
talk person [-x] [ttyname]
DESCRIPTION
Talk is a visual communication program which copies lines from your terminal to that of another user.
Options available:
person If you wish to talk to someone on your own machine, then person is just the person's login name. If you wish to talk to a user on
another host, then person is of the form 'user@host' ( or 'host.user' or 'host!user' or 'host:user' ).
-x If you wish to talk to a user who has dot character in username, the -x argument will force 'user@host' form of the person and talk
will take dots as part of user name.
ttyname If you wish to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal
name, where ttyname is of the form 'ttyXX' or 'pts/X'.
When first called, talk contacts the talk daemon on the other user's machine, which sends the message
Message from TalkDaemon@his_machine...
talk: connection requested by your_name@your_machine.
talk: respond with: talk your_name@your_machine
to that user. At this point, he then replies by typing
talk your_name@your_machine
It doesn't matter from which machine the recipient replies, as long as his login name is the same. Once communication is established, the
two parties may type simultaneously; their output will appear in separate windows. Typing control-L (^L) will cause the screen to be
reprinted. The erase, kill line, and word erase characters (normally ^H, ^U, and ^W respectively) will behave normally. To exit, just type
the interrupt character (normally ^C); talk then moves the cursor to the bottom of the screen and restores the terminal to its previous
state.
As of netkit-ntalk 0.15 talk supports scrollback; use esc-p and esc-n to scroll your window, and ctrl-p and ctrl-n to scroll the other win-
dow. These keys are now opposite from the way they were in 0.16; while this will probably be confusing at first, the rationale is that the
key combinations with escape are harder to type and should therefore be used to scroll one's own screen, since one needs to do that much less
often.
If you do not want to receive talk requests, you may block them using the mesg(1) command. By default, talk requests are normally not
blocked. Certain commands, in particular nroff(1), pine(1), and pr(1), may block messages temporarily in order to prevent messy output.
FILES
/etc/hosts to find the recipient's machine
/var/run/utmp to find the recipient's tty
SEE ALSO
mail(1), mesg(1), who(1), write(1), talkd(8)
BUGS
The protocol used to communicate with the talk daemon is braindead.
Also, the version of talk(1) released with 4.2BSD uses a different and even more braindead protocol that is completely incompatible. Some
vendor Unixes (particularly those from Sun) have been found to use this old protocol.
Old versions of talk may have trouble running on machines with more than one IP address, such as machines with dynamic SLIP or PPP connec-
tions. This problem is fixed as of netkit-ntalk 0.11, but may affect people you are trying to communicate with.
HISTORY
The talk command appeared in 4.2BSD.
Linux NetKit (0.17) November 24, 1999 Linux NetKit (0.17)