Sponsored Content
Operating Systems Solaris How to force multicast packet to go via different interface? Post 303044374 by hicksd8 on Thursday 20th of February 2020 05:33:40 AM
Old 02-20-2020
I've read your post a number of times but I still don't understand exactly what you are trying to do.

This is all Solaris 10? One global zone (Solaris 10) and seven non-global zones (all Solaris 10)?

One of the non-global zones you want to change its routing? The other six zones are routing okay?

To start with, what default gateways are these zones configured to and reading at boot time?

Please post the configuration of one working zone and the faulty routing zone.
Code:
# cat /etc/defaultrouter

(This, of course, assumes that you haven't executed commands to change the routing since boot-time, but it's somewhere to start.)
 

9 More Discussions You Might Find Interesting

1. Programming

Joining multicast group on IPADDR_ANY - which interface?

Hello all, I have the following question: if you join a multicast group (with setsockopt() and IP_ADD_MEMBERSHIP) and specify INADDR_ANY as network interface to join on, the kernel is supposed to choose which interface to use (if there are multiple network interfaces, of course). Does... (2 Replies)
Discussion started by: AlexI
2 Replies

2. UNIX for Advanced & Expert Users

Double question: Apache mod_proxy and force connection over specific interface

Double question here ... Running on Debian Etch and Apache 2.0 1) Using mod_proxy and/or mod_proxy_http in apache 2.0. The basics of using mod_proxy are pretty simple so long as you're using a static config. I'm trying to figure out how to do it dynamically - that is, allow the entry of a... (4 Replies)
Discussion started by: Halfwalker
4 Replies

3. Solaris

Reboot, System is Frozen at setting interface for multicast HELP

I'm not an advanced user by any strech, that being said here is my problem: I ran "reboot" on a sun blade 2500 When loading up it runs through the usual routine, checking disks, filesystems and then it locks up after the following message: ***** starting rpc services: rpcbind... (6 Replies)
Discussion started by: eyukins
6 Replies

4. Solaris

How to force the LAN interface running on 10M

Hi all, I would like to force the LAN card to use 10MB instead of 100MB in UNIX enviroment, please help. thanks! :) (3 Replies)
Discussion started by: Felixkoo
3 Replies

5. Solaris

how to force e1000g0 interface in solaris 10

Hi all, I encounter some problem with my e1000g interface running on sol 10. I can't permanently change the auto-nego to disable, if i use ndd commands, it will only stay until the next reboot. But i can't change the link speed either is set to /etc/init.d/nddconfig or using ndd commands. ... (1 Reply)
Discussion started by: mailbox80
1 Replies

6. HP-UX

How to determine network interface that will be used to send a packet for an IP

Hello, I'm writing to you because I encountered the following problem. My program displayes all network interfaces that are available in the system, but I would like to add a functionality in which a user can enter a destination address IP (ex. the IP address of the Google search engine) and will... (1 Reply)
Discussion started by: foxrafi
1 Replies

7. Solaris

Packet loss on ce interface.

Hi, I am using the ce interface on my Solaris 9 server and there is significant packet loss when transmitting large packets. Does anyone have a fix for this? ----10.1.0.0 PING Statistics---- 51 packets transmitted, 42 packets received, 17% packet loss round-trip (ms) min/avg/max =... (12 Replies)
Discussion started by: sparcman
12 Replies

8. AIX

Packet loss coming with big packet size ping

(5 Replies)
Discussion started by: Vishal_dba
5 Replies

9. IP Networking

Packet going out of wrong interface due to OS automatically added cache route with lower metric

RHEL 7.0, IPV6 Scenario: I have routed specific network using network scripts. 1. "ip -6 route show" shows that route has been added. ( with metric 1024) 2. Ping of the specific IP through that route is successful. 3. Now after few days, for some reason, we see that cache route appears for... (3 Replies)
Discussion started by: msr1981
3 Replies
ping(1M)																  ping(1M)

NAME
ping - send ICMP Echo Request packets to network host SYNOPSIS
address-family] address] interval] ttl] host count timeout]] address-family] address] interval] ttl] host packet-size count timeout]] DESCRIPTION
The command sends ICMP Echo Request (ECHO_REQUEST) packets to the host once per second. Each packet that is echoed back via an ICMP Echo Response packet is written to the standard output, including round-trip time. ICMP Echo Request datagrams ("pings") have an IP and ICMP header, followed by a (see gettimeofday(2)) and an arbitrary number of "pad" bytes used to fill out the packet. The default datagram length is 64 bytes, but this can be changed by using the packet-size option. Options The following options and parameters are recognized by If host is a multicast address, send multicast datagrams from the interface with the local IP address specified by address in "dot" notation (see inet(3N)). If the option is not specified, multicast datagrams are sent from the default inter- face, which is determined by the route configuration. If host is not a multicast address, the option is ignored. Insert an IP Record Route option in outgoing packets, summarizing routes taken when the command terminates. It may not be possible to get the round-trip path if some hosts on the route taken do not implement the IP Record Route option. A maximum of 9 Internet addresses can be recorded due to the maximum length of the IP option area. The new Path MTU information is displayed when a ICMP message is received from a gateway. The option must be used in conjunction with a large packetsize and with the option. Bypass the normal routing tables and send directly to a host on an attached network. If the host is not on a directly-connected network, an error is returned. This option can be used to ping the local system through an interface that has no route through it, such as, after the inter- face was dropped by (see gated(1M)). If host is a multicast address, set the time-to-live field in the multicast datagram to ttl. This controls the scope of the multicast datagrams by specifying the maximum number of external systems through which the datagram can be for- warded. If ttl is zero, the datagram is restricted to the local system. If ttl is one, the datagram is restricted to systems that have an interface on the network directly connected to the interface specified by the option. If ttl is two, the datagram can be forwarded through one multicast router at the most; and so forth. zero to 255. The default value is 1. This option specifies the interval in seconds, between each packet to be transmitted. The default interval is 1 second. Verbose output. Show ICMP packets other than Echo Responses that are received. The address-family determines whether the host is an IPv4 or IPv6 host. The address families currently supported are for IPv4 addresses and for IPv6 addresses. host Destination to which the ICMP Echo Requests are sent. host can be a hostname or an IPv4 or IPv6 Internet address. All symbolic names specified for host are looked up by using (see gethostent(3N)) for IPv4, and (see getaddrinfo(3N)) for IPv6. If host is an Internet address, it must be in "dot" notation (see inet(3N)) for IPv4, and in "colon" notation (see inet6(3N)) for IPv6. If the address-family is specified, and host is an Internet address, the address family of the Internet address must be the same as that specified in the address-family option. If the address-family is not specified, and host is a symbolic name, an attempt will be made to resolve host into an IPv4 address first. If that fails, a second attempt will be made to resolve host into an IPv6 address. The ping command does not accept IPv4-mapped IPv6 addresses. To ping an IPv4 node, an IPv4 address should be used. IPv4-mapped IPv6 addresses are used to address IPv4-only nodes from an IPv6 node in a socket program only. IPv4-mapped IPv6 addresses are always converted to an IPv4 address before they are used in packets sent over the network. If a system does not respond as expected, the route might be configured incorrectly on the local or remote system or on an intermediate gateway, or there might be some other network failure. Normally, host is the address assigned to a local or remote network interface. (inet only) If host is a broadcast address, all systems that receive the broadcast should respond. Normally, these are only systems that have a network interface on the same network as the local interface sending the ICMP Echo Request. If host is a multicast address, only systems that have joined the multicast group should respond. These may be distant systems if the option is specified, and there is a multicast router on the network directly connected to the interface specified by the option. packet-size The size of the transmitted packet, in bytes. By default (when packet-size is not specified), the size of transmitted packets is 64 bytes. The minimum value allowed for packet-size is 8 bytes, and the maximum value is 65500 bytes. If packet-size is smaller than 16 bytes, there is not enough room for timing information. In that case, the round-trip times are not displayed. The number of packets will transmit before terminating. The is not needed if also specifying packet-size. Range: zero to 2147483647. The default is zero, in which case sends packets until interrupted. Override the default timeout value (10 seconds) which uses to timeout (in seconds) when a host or network is unreachable. This option is valid only with the option or when count is specified. The option should not be used with count equal to 0. The option is not effective for reachable hosts or networks. Using ping for Fault Isolation When using for fault isolation, first specify a local address for host to verify that the local network interface is working correctly. Then specify host and gateway addresses further and further away to determine the point of failure. sends one datagram per second, and it normally writes one line of output for every ICMP Echo Response that is received. No output is produced if there are no responses. If an optional count is given, only the specified number of requests is sent. Round-trip times and packet loss statistics are computed. When all responses have been received or the command times out (if the count option is specified), or if the command is terminated with a a brief summary is displayed. This command is intended for use in testing, managing and measuring network performance. It should be used primarily to isolate network failures. Because of the load it could impose on the network, it is considered discourteous to use unnecessarily during normal operations or from automated scripts. RETURN VALUE
exits with one of the following values: On success. On failure such as unknown host, illegal packet size, etc. On a unreachable host or network. AUTHOR
was developed in the Public Domain. FILES
SEE ALSO
getaddrinfo(3N), gethostent(3N), inet(3N), inet6(3N). ping(1M)
All times are GMT -4. The time now is 05:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy