07-08-2010
Going by that error message, you are using the wrong gateway address. The gateway you have used is not on a directly-connected network, you need to use the next-hop gateway instead.
10 More Discussions You Might Find Interesting
1. IP Networking
I am running RH7.3 on a compaq presario box. The network card is a Linksys one. I am only able to communicate with the local network (only the local IPs are accessible). When I try to ping another box I get a "Connect: Network is unreachable" message. What could be the problem.
Thanks in... (2 Replies)
Discussion started by: skotapal
2 Replies
2. Solaris
Hi,
I am trying to add route command in Solaris 10 machine in the following fashion:
route add -host 10.8.112.10 180.144.1.250 -interface lo0:1
this command fails with an error "lo0:1: bad value"
I want to add a route to 10.8.112.10 that picks 180.144.1.250 as the gateway via the... (3 Replies)
Discussion started by: sudhir_shet
3 Replies
3. Red Hat
hi,
i would like to share this
/etc/sysconfig/network-script/route-eth0
GATEWAY0=XXXXXX
NETMASK0=XXXXXX
ADDRESS0=XXXXXXX
a delete route command with "route del -net xxxx...." will work but if the above exist and you reboot the linux then old route will be invoke on that config-route.
... (0 Replies)
Discussion started by: itik
0 Replies
4. Solaris
Hi All,
yesterday I was trying to add a network route to my solaris 8 host using 'route add'. Everytime I tried, I kept getting the response 'network is unreachable'.
I was trying all kinds of different methods, however I eventually got it to work after bouncing the interface that I was... (2 Replies)
Discussion started by: badoshi
2 Replies
5. Solaris
Hi there,
I'm trying to configure an additional network interface on Solaris 8 (eri0). The interface has been activated, but all the frames are still routed to the current default interface (ce0) I've tried following command (with various syntaxes...) unsuccessfully so far:
# route add... (2 Replies)
Discussion started by: sreiniche
2 Replies
6. IP Networking
I have built a new linux server, via a iLo connection.
and I am trying to connect via my desktop to the server I have just built to the management port eth0 via putty.
Please could some one advise how to connect to this server from my desktop. Do i need to create add a route access on the... (0 Replies)
Discussion started by: venhart
0 Replies
7. Solaris
Please , I have a problem
I have add a statis route on Solaris 10, but after this, the network interface of Server was Offline.
The system is in cluster mode (3.2)
route add -net 10.10.1.128 -netmask 255.255.255.128 10.10.1.51
-------------------
lo0:... (1 Reply)
Discussion started by: Ruggero
1 Replies
8. Linux
Assalam o Alaikum!
After configuring and starting service of samba, when I access shared folder from windows XP it gives this error " Network Route was not found".
My server IP 192.168.1.252, client is on same network.
selinux is disabled
smb,conf:
workgroup = WORKGROUP
server string =... (2 Replies)
Discussion started by: ukengr
2 Replies
9. UNIX for Advanced & Expert Users
Hi,
I have installed RHEL4 using vmware workstation..
Host OS: Windows XP
Guest OS: RHEL4
Pls refer step 17 & 18 in below link...
ORACLE-BASE - Red Hat Enterprise Linux 4 and Centos 4 Installation
1) If i choose to assign IP automatically (using DHCP) means, i am able to connect RHEL4... (3 Replies)
Discussion started by: thomasraj87
3 Replies
10. Solaris
Seems to wanboot ok but then fails to connect to server. What do I need to check?
{0} ok boot net - install
Boot device: /pci@300/pci@1/pci@0/pci@1/network@0 File and args: - install
1G link up
<time unavailable> wanboot info: WAN boot messages->console
<time unavailable>... (2 Replies)
Discussion started by: psychocandy
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