How to force multicast packet to go via different interface? Post: 303044401

Sponsored Content

Operating Systems Solaris How to force multicast packet to go via different interface? Post 303044401 by solaris_1977 on Thursday 20th of February 2020 11:40:35 AM

02-20-2020

Registered User

Global and all zones are Solaris 10.

I want multicast packets to go with prod interface (e1000g3), instead of current admin interface (e1000g0) on all zones.

I don't have defaultrouter file, but can see it here for global server and zones

Code:

# cat /etc/defaultrouter
cat: cannot open /etc/defaultrouter
# netstat -nr | grep default
default              192.168.241.1        UG        1       1442
default              216.221.133.193      UG        1      17358 e1000g3
# for i in `cat /var/tmp/zones.out`; do zlogin $i netstat -nrv | grep default; done
default              0.0.0.0         192.168.241.1                1500*    0   1 UG    1442      0
default              0.0.0.0         216.221.133.193      e1000g3  1500*    0   1 UG   17359      0
default              0.0.0.0         216.221.133.193      e1000g3  1500*    0   1 UG   17359      0
default              0.0.0.0         216.221.133.193      e1000g3  1500*    0   1 UG   17359      0
default              0.0.0.0         216.221.133.193      e1000g3  1500*    0   1 UG   17359      0
default              0.0.0.0         216.221.133.193      e1000g3  1500*    0   1 UG   17359      0
default              0.0.0.0         216.221.133.193      e1000g3  1500*    0   1 UG   17359      0
#

Neo : I am not sure, if we have dynamic routing protocol in our setup. Still checking it.

Last edited by solaris_1977; 02-20-2020 at 02:24 PM..

solaris_1977

View Public Profile for solaris_1977

Find all posts by solaris_1977

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. 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...

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...

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! :)

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. ...

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...

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 =...

8. AIX

Packet loss coming with big packet size ping

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...

LEARN ABOUT FREEBSD

ifmcstat

IFMCSTAT(8)						    BSD System Manager's Manual 					       IFMCSTAT(8)

NAME

     ifmcstat -- dump multicast group management statistics per interface

SYNOPSIS

     ifmcstat [-i interface] [-f address-family] [-v] [-K] [-M core] [-N system]

DESCRIPTION

     The ifmcstat command dumps multicast group information from the kernel.

     The following options are supported:

     -i interface
		 specifies the interface to be displayed.

     -f address-family
		 specifies the address family to be displayed; inet, inet6 and link are supported.

     -v 	 specifies that link-layer memberships should be printed; they are suppressed by default.  It may not be specified for -f link.
		 Source lists for each group will also be printed.

		 If specified twice, and kvm(3) is in use, the control plane timers for each interface and the source list counters for each group
		 will also be printed.

     The following options are only available if ifmcstat has been built with support for kvm(3):

     -K 	 attempts to use kvm(3) to retrieve the multicast group information.

     -M core	 extracts values associated with the name list from the specified core, instead of the default /dev/kmem.

     -N system	 extracts the name list from the specified kernel instead of the default, which is the kernel image the system has booted from.

IMPLEMENTATION NOTES

     ifmcstat will always print the embedded scope IDs of IPv6 multicast group memberships.  This is because memberships are always scoped to an
     interface.

     When run with the -v option, ifmcstat may print multicast MAC addresses twice if they are referenced by a layer 3 protocol.

     When run with kvm(3) support, the names of all interfaces configured in the system will be printed in the first column of output, even if no
     multicast group memberships are present on those interfaces.  The output may also be slightly different, as the kernel data structures are
     being traversed with minimal post-processing of the output.

     When built without kvm(3) support, the information displayed by ifmcstat is more limited.	This support is recommended for debugging pur-
     poses.  It requires super-user privilege if used to inspect a running kernel.

SEE ALSO

     netstat(1), getifaddrs(3), getifmaddrs(3), kvm(3)

BSD
								   May 27, 2009 							       BSD