06-25-2009
Can you ping your gateway IP 172.25.4.1 ?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Dear Reader,
I have a very unique problem. Quite often my on board ethernet port( hme0 ) related message is appearing in /var/adm/messages.
The message is hme0: babble.. The port is up and alive.
What does this message mean.. Is the on board port is about to fail??
Thanks in advance, (2 Replies)
Discussion started by: joseph_shibu
2 Replies
2. UNIX for Advanced & Expert Users
How do you configure more than one network on a single hme0 interface under SunOS? And why would you want to do this?
Thanx :)
-Michelle (1 Reply)
Discussion started by: Michelle1977
1 Replies
3. BSD
hi
I want to setup my cable modem under OpenBSD. I did not configure my network while installing the system.
When I type, I get
# ifconfig -a
lo0 : ....
...
...
rl0 : ....
...
...
vr0 : ...
...
...
I have two network cards (the machine will be a router).
I created... (1 Reply)
Discussion started by: fnoyan
1 Replies
4. Solaris
Hi all,
Is there any difference between a null modem cable or a modem cable ?
i assume that a null modem cable is a normal cable that i used from cpu serial ports to a modem for dialup.
please correct if i am wrong,
thks (2 Replies)
Discussion started by: waterbear
2 Replies
5. Solaris
Hi .....
My problem is that when i reboot the system i can't connect to the network because my ethernet ( hme0 ) is down , i must up it by ifconfig command
after reboot :
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask... (1 Reply)
Discussion started by: tt155
1 Replies
6. Solaris
I have a 420r server it boots up all of the network settings are correct, however the machines network connection is not working. Cant ping anything from it, cant ping it from another machine on the network.
If I ping 127.0.0.1 it says alive.
Is there a chance the network card has been... (2 Replies)
Discussion started by: alanj4
2 Replies
7. Solaris
Hi All,
1. modify /etc/default/login file as
make commented # console=
2.put my laptops ip at both
/etc/inet/ipnodes and /etc/host file
still i can login via telnet/ftp through a DB9-serial cable, but when i tried
through a lan stratight cable directly connected that machine... (7 Replies)
Discussion started by: mahadib
7 Replies
8. Solaris
Hi all,
really interesting thing I have encountered . So :
root@host4 # uname -a
SunOS host4 5.9 Generic_122300-31 sun4u sparc SUNW,Sun-Fire-880
root@host4 # scinstall -p
3.2
latest recommended patches applied ..all SUN cluster patches applied.
SUN cluster software installed without... (2 Replies)
Discussion started by: samar
2 Replies
9. Solaris
We are unable to ping from Sun Ultra 60 to Ultra 10 machine and vice versa. We are getting an error message Cable Link Down ?. It was working fine.
Troubleshooting steps taken.
1) Changed the IPaddresses on both machines 192.168.10.10 and 192.168.10.20. These machines connected through 8 port... (2 Replies)
Discussion started by: vijaykrishna
2 Replies
10. Red Hat
I am facing strange problem regarding hostname on my Linux(2.6.18-164.el5xen x86_64 GNU/Linux), the hostname changes if reboot with lan cable and with NO lan cable
Reboot with lan cable:
The hostname is ubunut
Unable to connect Oracle database using sqlplus some times database is not... (2 Replies)
Discussion started by: LinuxLearner
2 Replies
LEARN ABOUT OSX
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