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

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 DEBIAN

tttprobe

tttprobe(1)								net							       tttprobe(1)

NAME

       tttprobe - Tele Traffic Tapper probe -  A probe to collect local traffic-data and send it to a remote instance of tttview

SYNTAX

       ttt [-interface device] [-interval ms] [-multicast] [-port dest_port] [-ttl time-to-live] [Destination]

DESCRIPTION

       tttprobe  is  the probe program in the ttt program suite. tttprobe locally collects traffic-data and sends it over a network to an instance
       of tttview.

       To run tttview, it is not necessary to be "root".

       The ttt program suite is yet another descendant of tcpdump but it is capable of real-time, graphical, local and remote  traffic-monitoring.
       It won't replace tcpdump, rather, it helps you find out what to look into with tcpdump.

OPTIONS

       ttt [-interface device] [-interval ms] [-multicast] [-port dest_port] [-ttl time-to-live] [Destination]

       -interface device
	      specifies the interface for packet capture. If not specified, the default interface is chosen.

       -interval ms
	      Sets the interval in Milliseconds. If omitted, a interval of 1000 msec. is used as default.

       -multicast
	      Shorthand for the default multicast destination "224.8.8.0".

       -port dest_port
	      Specifies the udp port number on the remote host where the traffic-data should be sent to. If omitted, port 7288 is used as default.

       -ttl time-to-live
	      Specifies the time-to-live for multicast. If omitted, 1 is used as default to restrict the multicast to the local subnet.

       Destination
	      Specifies  the  remote  host  where the traffic-data should be sent to. Destination can be omitted only, if -multicast is specified.
	      Destination can be a uni- or multicast address.

EXAMPLES

       Remark: "hostA" is allways the host where traffic-data is collected with tttprobe and "hostB" is allways the host where the traffic-data is
       displayed with tttview.

       point-to-point monitoring:

	      hostA: tttprobe hostB
	      hostB: tttview

	      or:

	      hostA: tttprobe ip_of_hostB
	      hostB: tttview

       multicast:

	      when using the default multicast address:

	      hostA: tttprobe -multicast
	      hostB: tttview -multicast

	      this is equivalent to:

	      hostA: tttprobe 224.8.8.0
	      hostB: tttview -addr 224.8.8.0

AUTHORS

       tttprobe was written by Kenjiro Cho < kjc@csl.sony.co.jp>.

       This  manual page was written by Thomas Scheffczyk <thomas.scheffczyk@verwaltung.uni-mainz.de>, for the Debian GNU/Linux system (but may be
       used by others).

SEE ALSO

       ttt(1), tttview(1)

Kenjiro Cho								1.7							       tttprobe(1)