Sponsored Content
Full Discussion: HPUX Routing Question
Special Forums IP Networking HPUX Routing Question Post 61060 by robanic on Thursday 27th of January 2005 04:38:30 PM
Old 01-27-2005
IP addresses get changed

To clarify: What is happening is that the ip address leaving the machine, if not on the same network, always gets translated to the ip address of the gateway, so that traffic never gets beyond that point.

When I plug in my windows laptop to that network port and use the ip of the unix machine, everything works correctly, the ip addresses don't get changed. My windows machine can ping remote addresses and get beyond the gateway. The same is true for a Solaris machine on that same switch. Traffic can be detected going from the Solaris machine to machines on other networks - for example, I can successfully ping Yahoo, Cisco, Google..etc. and I can see those destination addresses in the sniffer.

On the HPUX machine however, if I ping Yahoo, Cisco, Google or another network on our VPN link, the destination coming from that box always shows as the gateway interface. Smilie
 

10 More Discussions You Might Find Interesting

1. IP Networking

Routing

I have SCO Unix. I have 2 routers. as it is now, when someone telnets to UNIX and goes through router #1 everything is fine. The users who go through router #2 can not connect at all. I talked to CISCO and they said I need to set up a second Gateway on UNIX. They said what is happening is that... (1 Reply)
Discussion started by: john fli
1 Replies

2. IP Networking

Routing

ok i configured my gateway and IP address(es) using ifconfig and route.. but how can i bind unique IPs to users ? (im using FreeBSD 4.2 RELEASE #3) (9 Replies)
Discussion started by: DevilGREEN
9 Replies

3. UNIX for Advanced & Expert Users

routing

Hi, in which file and how shuold be decalred a gateway and its IP adresse ? Where and how add a gateway ? Many thanks before. (4 Replies)
Discussion started by: big123456
4 Replies

4. Shell Programming and Scripting

Need Script to Use CPUs on a HPUX server to simulate Workload Manager on HPUX.

I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies

5. HP-UX

HPUx sendmail Question

why is that I need to go to /usr/sbin> in order to run send mail how can I run sendmail where ever folder I'm in... e.g. like /stuff/games/sendmail ksh: sendmail: not found (7 Replies)
Discussion started by: makaveli
7 Replies

6. HP-UX

A question about HPUX PV link...

Are "/dev/dsk/c58t6d7" and "/dev/dsk/c94t0d4" assigning to a same disk? results of "vgdisplay -v" PV Name /dev/dsk/c58t6d7 PV Name /dev/dsk/c94t0d4 Alternate Link PV Name /dev/dsk/c75t6d7 Alternate Link PV Name ... (1 Reply)
Discussion started by: JoyOnLine
1 Replies

7. Red Hat

routing table question

I have below routing table in linux kernel 2.6.9 # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.155.24.0 0.0.0.0 255.255.252.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U ... (5 Replies)
Discussion started by: chuikingman
5 Replies

8. HP-UX

pwage-hpux-T for Trusted HPUX servers

I'm sharing this in case anybody needs it. Modified from the original solaris pwage script. This modified hpux script will check /etc/password file on hpux trusted systems search /tcb and grep the required u_succhg field. Calculate days to expiry and notify users via email. original solaris... (2 Replies)
Discussion started by: sparcguy
2 Replies

9. IP Networking

routing problem/question

Internet Gateway 192.168.0.201 Server 1 192.168.0.101 192.168.1.101 192.168.2.101 gateway: 192.168.0.201 VIP: 192.168.1.100 VIP: 192.168.2.100 Server 2 192.168.0.102 192.168.1.102 192.168.2.102 gateway: 192.168.0.201 Client 1 192.168.2.201 gateway: 192.168.2.100 (1 Reply)
Discussion started by: hopfensp
1 Replies

10. UNIX for Advanced & Expert Users

A little question: packaging for hpux

Simple question: how to package from source in hpux? On Linux slackware i Use configure,make,make install DESTDIR=$pkg,etc.. and then makepkg -l y -c n. Is possible something similar on hpux? I want to create a depot for samba because,the official doesn't had the winbind pam,and the package on... (1 Reply)
Discussion started by: Linusolaradm1
1 Replies
ping(1M)                                                  System Administration Commands                                                  ping(1M)

NAME
ping - send ICMP (ICMP6) ECHO_REQUEST packets to network hosts SYNOPSIS
/usr/sbin/ping host [timeout] /usr/sbin/ping -s [-l | -U] [-adlLnrRv] [-A addr_family] [-c traffic_class] [-g gateway [ -g gateway...]] [-F flow_label] [-I interval] [-i interface] [-P tos] [-p port] [-t ttl] host [data_size] [npackets] DESCRIPTION
The utility ping utilizes the ICMP (ICMP6 in IPv6) protocol's ECHO_REQUEST datagram to elicit an ICMP (ICMP6) ECHO_RESPONSE from the speci- fied host or network gateway. If host responds, ping will print: host is alive on the standard output and exit. Otherwise, after timeout seconds, it will write: no answer from host The default value of timeout is 20 seconds. When you specify the s flag, sends one datagram per second (adjust with -I) and prints one line of output for every ECHO_RESPONSE that it receives. ping produces no output if there is no response. In this second form, ping computes round trip times and packet loss statistics; it displays a summary of this information upon termination or timeout. The default data_size is 56 bytes, or you can specify a size with the data_size command-line argument. If you specify the optional npackets, ping sends ping requests until it either sends npackets requests or receives npackets replies. When using ping for fault isolation, first ping the local host to verify that the local network interface is running. OPTIONS
The following options are supported: -A addr_family Specify the address family of the target host. addr_family can be either inet or inet6. Address family determines which protocol to use. For an argument of inet, IPv4 is used. For inet6, IPv6 is used. By default, if the name of a host is provided, not the literal IP address, and a valid IPv6 address exists in the name service database, ping will use this address. Otherwise, if the name service database contains an IPv4 address, it will try the IPv4 address. Specify the address family inet or inet6 to override the default behavior. If the argument specified is inet, ping will use the IPv4 address associated with the host name. If none exists, ping will state that the host is unknown and exit. It does not try to determine if an IPv6 address exists in the name service database. If the specified argument is inet6, ping uses the IPv6 address that is associated with the host name. If none exists, ping states that the host is unknown and exits. -F flow_label Specify the flow label of probe packets. The value must be an integer in the range from 0 to 1048575. This option is valid only on IPv6. -I interval Turn on the statistics mode and specify the interval between successive transmissions. The default is one second. See the discussion of the -s option. -L Turn off loopback of multicast packets. Normally, members are in the host group on the outgoing interface, a copy of the multicast packets will be delivered to the local machine. -P tos Set the type of service (tos) in probe packets to the specified value. The default is zero. The value must be an integer in the range from 0 to 255. Gateways also in the path can route the probe packet differently, depending upon the value of tos that is set in the probe packet. This option is valid only on IPv4. -R Record route. Sets the IPv4 record route option, which stores the route of the packet inside the IPv4 header. The contents of the record route are only printed if the -v and -s options are given. They are only set on return pack- ets if the target host preserves the record route option across echos, or the -l option is given. This option is valid only on IPv4. -U Send UDP packets instead of ICMP (ICMP6) packets. ping sends UDP packets to consecutive ports expecting to receive back ICMP (ICMP6) PORT_UNREACHABLE from the target host. -a ping all addresses, both IPv4 and IPv6, of the multihomed destination. The output appears as if ping has been run once for each IP address of the destination. If this option is used together with -A, ping probes only the addresses that are of the specified address family. When used with the -s option and npackets is not specified, ping continuously probes the destination addresses in a round robin fashion. If npackets is specified, ping sends npackets number of probes to each IP address of the destination and then exits. -c traffic_class Specify the traffic class of probe packets. The value must be an integer in the range from 0 to 255. Gateways along the path can route the probe packet differently, depending upon the value of traffic_class set in the probe packet. This option is valid only on IPv6. -d Set the SO_DEBUG socket option. -g gateway Specify a loose source route gateway so that the probe packet goes through the specified host along the path to the target host. The maximum number of gateways is 8 for IPv4 and 127 for IPv6. Note that some factors such as the link MTU can further limit the number of gateways for IPv6. -i interface_address Specify the outgoing interface address to use for multicast packets for IPv4 and both multicast and unicast packets for IPv6. The default interface address for multicast packets is determined from the (unicast) routing tables. interface_address can be a literal IP address, for example, 10.123.100.99, or an interface name, for example, eri0, or an interface index, for example 2. -l Use to send the probe packet to the given host and back again using loose source routing. Usually specified with the -R option. If any gateways are specified using -g, they are visited twice, both to and from the destination. This option is ignored if the -U option is used. -n Show network addresses as numbers. ping normally does a reverse name lookup on the IP addresses it extracts from the packets received. The -n option blocks the reverse lookup, so ping prints IP addresses instead of host names. -p port Set the base UDP port number used in probes. This option is used with the -U option. The default base port number is 33434. The ping utility starts setting the destination port number of UDP packets to this base and increments it by one at each probe. -r Bypass the normal routing tables and send directly to a host on an attached network. If the host is not on a directly attached network, an error is returned. This option can be used to ping a local host through an interface that has been dropped by the router daemon. See in.routed(1M). -s Send one datagram per second and collect statistics. -t ttl Specify the IPv4 time to live, or IPv6 hop limit, for unicast and multicast packets. The default time to live (hop limit) for unicast packets can be set with the ndd module, /dev/icmp, using the icmp_ipv4_ttl variable for IPv4 and the icmp_ipv6_hoplimit variable for IPv6. The default time to live (hop limit) for multicast is one hop. See EXAM- PLES. For further information, seendd(1M). -v Verbose output. List any ICMP (ICMP6) packets, other than replies from the target host. OPERANDS
host The network host EXAMPLES
Example 1: Using ping With IPv6 This example shows ping sending probe packets to all the IPv6 addresses of the host xyz, one at a time. It sends an ICMP6 ECHO_REQUEST every second until the user interrupts it. istanbul% ping -s -A inet6 -a xyz PING xyz: 56 data bytes 64 bytes from xyz (4::114:a00:20ff:ab3d:83ed): icmp_seq=0. time=0.479 ms 64 bytes from xyz (fec0::114:a00:20ff:ab3d:83ed): icmp_seq=1. time=0.843 ms 64 bytes from xyz (4::114:a00:20ff:ab3d:83ed): icmp_seq=2. time=0.516 ms 64 bytes from xyz (fec0::114:a00:20ff:ab3d:83ed): icmp_seq=3. time=4.94 ms 64 bytes from xyz (4::114:a00:20ff:ab3d:83ed): icmp_seq=4. time=0.485 ms 64 bytes from xyz (fec0::114:a00:20ff:ab3d:83ed): icmp_seq=5. time=2.20 ms ^C ----xyz PING Statistics---- 6 packets transmitted, 6 packets received, 0% packet loss round-trip (ms) min/avg/stddev = 0.479/1.58/4.94/1.8 Example 2: Using ndd to Set the icmp_ipv6_hoplimit This example shows the ndd module, /dev/icmp, used to set the icmp_ipv6_hoplimit. # ndd -set /dev/icmp icmp_ipv6_hoplimit 100 EXIT STATUS
The following exit values are returned: 0 Successful operation; the machine is alive. non-zero An error has occurred. Either a malformed argument has been specified, or the machine was not alive. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWbip | +-----------------------------+-----------------------------+ SEE ALSO
ifconfig(1M), in.routed(1M), ndd(1M), netstat(1M), rpcinfo(1M), traceroute(1M), attributes(5), icmp(7P), icmp6(7P) SunOS 5.10 11 Mar 2004 ping(1M)
All times are GMT -4. The time now is 07:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy