Hi, The default gateway (172.17.220.1) cannot be pinged via the default interface bond0 (172.17.220.231), but can be pinged via interface eth1 (10.201.135.73).
Code:
# ping -I eth1 172.17.220.1
PING 172.17.220.1 (172.17.220.1) from 10.201.135.73 eth1: 56(84) bytes of data.
64 bytes from 172.17.220.1: icmp_seq=0 ttl=255 time=5.48 ms
64 bytes from 172.17.220.1: icmp_seq=1 ttl=255 time=0.523 ms
# ping -I bond0 172.17.220.1
PING 172.17.220.1 (172.17.220.1) from 172.17.220.231 bond0: 56(84) bytes of data.
From 172.17.220.231 icmp_seq=1 Destination Host Unreachable
From 172.17.220.231 icmp_seq=2 Destination Host Unreachable
Ping is supposed to work with the default interface bond0. Because the virtual interface bond0 can be pinged by systems in the same subnet, bond0 is working (right?). There must be a routing issue. Here is the interfaces info:
Hello,
I've moved to a new network with multiple AIX box's. Most of them are working fine and dandy.
On one box I need to set up a static route to a gateway.. no problem right?
Whenever I add the route it appears in the routing table as UGc and then begins adding new entries to the... (1 Reply)
I have a string as "Period= 20090531 Client Name= Clayton Lumbar Company Destination= MD"
I want to parse the string and store it in 3 different variables.
$period (should get value 20090531)
$client (should get value "Clayton Lumbar company")
$dest (should get value MD)
How can I do... (3 Replies)
I have an IP routing issue or I am just to stupid to work it out myself.
I have setup am old PC running SUSE Linux 11.3 as a router, the system has 3 Interfaces connecting 3 networks.
Interface 1 = 10.164.2.161/21
Interface 2 = 192.168.1.210/24
Interface 3 = 30.1.0.11/16
The default... (6 Replies)
I have run into a wall troubleshooting a Centos 5 networking issue. Hoping someone can assist.
I've got a box with two vlans trunked over bond0
bond0 Link encap:Ethernet HWaddr 00:22:64:C1:D6:60
inet6 addr: fe80::222:64ff:fec1:d660/64 Scope:Link ... (0 Replies)
hello everyone!:)
I have an exercise which I think is difficult for beginner like me. Here is the exercise
Create a shell script, which takes a directory as command line argument.
Script displays ten first lines from every text file in that directory. After
displaying the lines from the... (1 Reply)
hi guys
suse 11 SP1 x64
I have a server (4 NIC ports 192.168.100.100-103) that connects point to point to a storage device (same thing 4 ports 192.168.110.100-113) but this server connects to normal LAN 10.6.100.x - gateway 10.6.100.1
the issue is when testing connectivity to the storage... (7 Replies)
we are not able to ping client server (falcon-ebr.sbms.bsc.com) from netbackup master server (135.179.96.122 tsprd-ebr.edc.single.net)
However from client server we are able to ping the master Server.
Please assist on this (1 Reply)
Hi,
Please help me on issue described below,
I have 4 machine setup, M1 -> M2 -> M3 | M4. And A laptop that can be reachable through both M3 and M4.
M2 has 2 NIC conected to M3 and M4. Now I want to divide the flow coming from M1 for laptop.
At M2, I have done following,... (1 Reply)
Discussion started by: rahulbhansali24
1 Replies
LEARN ABOUT ULTRIX
route
route(8c)route(8c)Name
route - manually manipulate the routing tables
Syntax
/etc/route [ -f ] [ -n ] command args ]
Description
The program is used to manipulate the network routing tables manually. However, normally it is not needed, as the system routing table
management daemon, should tend to this task.
The program accepts two commands: add, to add a route and delete, to delete a route.
All commands have the following syntax:
/etc/route command [ net | host ] destination gateway [ metric ]
In this syntax, destination is a host or network for which the route is to, gateway is the gateway to which packets should be addressed,
and metric is an optional count indicating the number of hops to the destination. The metric is required for add commands. It must be
zero if the destination is on a directly-attached network, and nonzero if the route utilizes one or more gateways.
When adding a route with metric 0, the gateway given is the address of this host on the common network, indicating the interface to be used
for transmission. Routes to a particular host are distinguished from routes to a network by interpreting the Internet address associated
with destination. The optional keywords net and host force the destination to be interpreted as a network or host, respectively. If the
destination has a local address part of INADDR_ANY, then the route is assumed to be to a network. Otherwise, it is presumed to be a route
to a host. If the route is to a destination connected via a gateway, the metric should be greater than 0. All symbolic names specified
for a destination or gateway are looked up first as a host name using If this lookup fails, is then used to interpret the name as that of a
network.
The command uses a raw socket and the SIOCADDRT and SIOCDELRT ioctls to do its work. As such, only the superuser can modify the routing
tables.
Options-f Flushes the routing tables of all gateway entries. If is used with one of the commands described above, the tables are flushed prior
to the command's application.
-n Prevents attempts to print host and network names symbolically when reporting actions.
Restrictions
The change operation is not implemented. Therefore, you should first add the new route, and then delete the old one.
Diagnostics
add [host | network] %s: gateway %s flags %x"
The specified route is being added to the tables. The values printed are from the routing table entry supplied in the ioctl call. If the
gateway address used was not the primary address of the gateway (the first one returned by the gateway address is printed numerically as
well as symbolically.
delete [ host | network] %s: gateway %s flags %x
The specified route is being deleted from the tables. The values printed are from the routing table entry supplied in the ioctl call. If
the gateway address used was not the primary address of the gateway (the first one returned by the gateway address is printed numerically
as well as symbolically.
%s %s done
When the flag is specified, each routing table entry that is deleted is indicated with a message of this form.
Network is unreachable
An attempt to add a route failed because the gateway listed was not on a directly-connected network. The next-hop gateway must be given.
not in table
A delete operation was attempted for an entry which was not present in the tables.
routing table overflow
An add operation was attempted, but the system was low on resources and was unable to allocate memory to create the new entry.
See Alsointro(4n), routed(8c)route(8c)