Multicast relay

Hi, im receiving a stream from a radio station, i want to use my server (actually receiving and working unicast)as multicast relay in order to allow users inside the local network to connect and lowering bandwidth.
When configuring a multicast relay there is an option regarding a .sdp file that should be placed in a specific folder, but i dunno where to get one example file or how to configure it.
there is also said about creating a destination, but if any user should be able to connect, should i leave this option empty?
any idea
regards
killabyte

Can you be a little more specific about your equipment? I think what you are trying is possible given you have the right stuff and a good network there.

Similar Messages

Multicast stops after about 2 minutes

Hi,
We are testing IP Multicast, with Flahs media player 4.0.
We set up the encoder and generated the manifest file.
Multicast start, but we see lot of bufferring and video running fast.
After about 2 minutes, the encode stops publishing to the server.
We are using digital rapids as the encoder.
Any idea this might be causing ?

A few things to try:
1. If you're using the 'multicast' application that ships with FMS4, it logs state transitions and event info to the app log as the server-side multicast relay (a server-side NetConnection/NetGroup/NetStream) start up and redirect the ingest stream from FMLE into the Flash Group. I'd recommend reading through that and verifying that the server-side objects handling the relay into the Group are happy (i.e. not disconnecting or being closed down).
2. The multicastplayer client SWF app has some flashvars defined in the HTML shim file that loads it. One of these is a debug flag. If you set that to true, you'll get some debug info surfaced up to your UI. This will include the various events the client is processing on its NetConnection/NetGroup/NetStream that's being used to play the multicast stream out of the target Flash Group. Feel free to post those details back to this thread.
3. If you're doing IP multicast, that won't work over the public internet. In that case you'll want to be using P2P multicast.
Best,
Seth

Multicast ip-pim-sparse mode

Hi, my consideration are correct for the multicast protocol ?
As for the command "ip pim rp-address 173.17.2.1 VALID_GROUP" which is on the site of Padriciano I did a search and, practically, it automatically creates a tunnel interface.
This thing, as I said, you need to create / enable multicast. Being something of CCNP R & S do not know the different syntax but "PIM" stands for Protocol-Independent Multicast.
Because you do not have to do often directly with the multicast explain it to follow but it is as a reality check for me:
Multicast uses the connectionless protocol UDP for transport (transport layer, Layer 4 - L4) and allows you to send, with just sending the same packet to multiple nodes; since UDP does not guarantee delivery. You can think of as a multicast broadcast changed.
For example: if you have 6 nodes (node = router), for simplicity called ABCDEF, and the node A has to send a packet only to nodes BCDF (excluding the node E) then, with multicast, the packet is sent only once and is delivered to all hosts BCD F.
That's the theory but in practice petty commands ip pim NOT know them being the subject of CCNP R & S.
>> A concrete example of multicast: the election of the DR (Designated Router) and the Des BDR (Backup ignated Router) in multiaccess networks (such as Frame Relay networks) with OSPF.
All routers in the network that are NOT DR or BDR are Drothers (read as DR-Others). The Drothers can only communicate with the DR (simultaneously with the BDR).
This feature allows you to NOT flood the LSA (Link State Advertisement) to all routers in the network so that only the Drothers send their LSA to the DR and BDR using the multicast address 224.0.0.6 IPv4 or IPv6 multicast address ff02 :: 6.
224.0.0.6 and ff02 :: 6 = all routers DR
When the DR receives packets is responsible for forwarding these LSA to all other routers. The DR uses the multicast address 224.0.0.5 IPv4 or IPv6 multicast address ff02 :: 5. The end result is that there is only one router that does the flooding of all LSA in the multiaccess network.
>> 224.0.0.5 and ff02 :: 5 = all OSPF routers
ip multicast-routing
interface GigabitEthernet0/1.134
description LAN EDA
encapsulation dot1Q 134
ip address 134.1.192.31 255.255.255.240
no ip redirects
ip directed-broadcast
standby 134 ip 134.1.192.33
standby 134 timers msec 300 msec 950
standby 134 priority 90
standby 134 preempt delay reload 10
no shutdown
router ospf 1
network 134.1.192.32 255.255.255.240 area 15    ! LAN PMU
! Avalaible Routing Multicast for LAN EDA
ip multicast-routing
interface GigabitEthernet0/0
ip pim sparse-mode
interface GigabitEthernet0/1.500
ip pim sparse-mode
interface Serial0/1/0.36 point-to-point
ip pim sparse-mode
interface GigabitEthernet0/1.134
ip pim sparse-mode
ip igmp join-group 224.0.224.1
ip pim rp-address 173.17.2.1 VALID_GROUP
ip access-list standard VALID_GROUP
permit 224.0.224.1
router ospf 1
network 134.1.192.32 255.255.255.240 area 15    ! LAN PMU
! Avalaible Routing Multicast for LAN EDA
ip multicast-routing
interface GigabitEthernet0/0
ip pim sparse-mode
interface GigabitEthernet0/1.500
ip pim sparse-mode
interface Serial0/1/0.39 point-to-point
ip pim sparse-mode
interface GigabitEthernet0/1.134
ip pim sparse-mode
ip igmp join-group 224.0.224.1
ip pim rp-address 173.17.2.1 VALID_GROUP
ip access-list standard VALID_GROUP
permit 224.0.224.1
I did some tests simulated and I think I figured out why is assigned an IP address instead of another.
Given that the interface Tunnel0 is created when you type the command "ip pim rp-address 173.17.2.1 VALID_GROUP", in the tests I've done, I Tunnel0 Bind to the IP address associated with the FastEthernet0/0.
R-SCTI-PADRICIANO-1#sh ip int b
>>     Interface                  IP-Address      OK? Method Status             Protocol
>>     FastEthernet0/0            173.27.200.22   YES manual up                    up
>>     FastEthernet0/1            unassigned      YES manual up                    up
>>     FastEthernet0/1.20         172.27.195.118 YES manual up                    up
>>     FastEthernet0/1.30         172.27.230.100 YES manual up                    up
>>     FastEthernet0/1.31         173.27.254.118 YES manual up                    up
>>     FastEthernet0/1.32         173.27.216.28   YES manual up                    up
>>     FastEthernet0/1.134        134.1.192.33    YES manual up                    up
>>     FastEthernet0/1.500        172.27.250.37   YES manual up                    up
>>     Serial1/0                  unassigned      YES unset administratively down down
>>     Serial1/1                  unassigned      YES unset administratively down down
>>     Serial1/2                  unassigned      YES unset administratively down down
>>     Serial1/3                  unassigned      YES unset administratively down down
>>     Loopback0                  172.27.254.10   YES manual up                    up
>>     Tunnel0                    173.27.200.22   YES unset up                    down
R-SCTI-PADRICIANO-1#conf t
>>     R-SCTI-PADRICIANO-1(config)#int f0/0
>>     R-SCTI-PADRICIANO-1(config-if)#sh
>>     *Feb 6 16:09:31.439 CET: %LINK-5-CHANGED: Interface FastEthernet0/0, changed state to administratively down
>>     *Feb 6 16:09:32.439 CET: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to down
>>     R-SCTI-PADRICIANO-1(config-if)#do sh ip int b
>>     Interface                  IP-Address      OK? Method Status                Protocol
>>     FastEthernet0/0            173.27.200.22   YES manual administratively down down
>>     FastEthernet0/1            unassigned      YES manual up                    up
>>     FastEthernet0/1.20         172.27.195.118 YES manual up                    up
>>     FastEthernet0/1.30         172.27.230.100 YES manual up                    up
>>     FastEthernet0/1.31         173.27.254.118 YES manual up                    up
>>     FastEthernet0/1.32         173.27.216.28   YES manual up                    up
>>     FastEthernet0/1.134        134.1.192.33    YES manual up                    up
>>     FastEthernet0/1.500        172.27.250.37   YES manual up                    up
>>     Serial1/0                  unassigned      YES unset administratively down down
>>     Serial1/1                  unassigned      YES unset administratively down down
>>     Serial1/2                  unassigned      YES unset administratively down down
>>     Serial1/3                  unassigned      YES unset administratively down down
>>     Loopback0                  172.27.254.10   YES manual up                    up
>>     Tunnel0                    172.27.250.37   YES unset up                    down
>>
>> IP address Tunnel0 = IP address FastEthernet0/1.500

Well, this is all looks like it is has to be. What confuses you?
Tun0 created by pim process to decapsulate multicast traffic coming to RP from source router. It doesn't matter what ip used inside of this interface.

Streaming Server Relay help please

I have QT B'Caster and QTSS installed on my PMG5. I have successfully captured and encoded video with broadcaster and transmitted an automatic unicast. On the same machine I am in my QTSS setup in Safari. If I go into the Broadcaster section of StreamingServer and click View Broadcast, I can see that in fact it is streaming what was coming out of Broadcaster.
My question is how to set up a multicast to the internet. I think I need to add a new relay, but that's where I get confused. The source is pretty straight forward, and I just have it waiting for announced streams anyway. What info do I fill in for the destination settings? Do I need to get some more hardware or services to point to? After that's settled, how will users know where to look to view the reflected stream?
I'm almost there, but I'm just missing a few key elements. Anyone who can help me understand would be much appreciated. TIA!

Hi,
did you ask your host/provider whether your password and your username are correct?
Otherwise you could try connecting not with DW features, but with a different software.
For various reasons I prefer to upload my files and sometimes for the opposite way, for a necessary download from my server, with a program which works "outside" of the DW. Therefore I am using filezilla with great success and it looks for me easier to keep track of all operations precisely and generate or reflect easily the desired tree structure.
Here is the link to get it and where you can read informations about how it works:
http://filezilla-project.org/.
Needless to say, as a precondition of course, is that you have all access data to your server and of course a logical structure of your directory tree.
Hans-G.

Fram Relay hub and spoke scenario

See the attachment please
Requirements:
1.Using only physical interfaces configure a Frame Relay hub-and-spoke network between RTA and RTB and RTC, RTB as the hub.
2.Traffic from RTA destined for RTC should transit RTB, and vice versa.
3.Use only the DLCIs specified in the diagram.
4.Do not use any Dynamic layer 3 to layer 2 mappings over these frame Relay connections.
5.Do not send any redundant broadcast traffic from the spokes to the hub.
RTB (Hub):
interface Serial0/0
ip address 3.1.1.2 255.255.255.0
encapsulation frame-relay
frame-relay map ip 3.1.1.1 200 broadcast
frame-relay map ip 3.1.1.3 300 broadcast
no frame-relay inverse-arp
RTA (Spoke):
interface Serial0/0
ip address 3.1.1.1 255.255.255.0
encapsulation frame-relay
frame-relay map ip 3.1.1.2 22 broadcast
frame-relay map ip 3.1.1.3 22
no frame-relay inverse-arp
RTC (Spoke):
interface Serial1/0
ip address 3.1.1.3 255.255.255.0
encapsulation frame-relay
frame-relay map ip 3.1.1.2 33 broadcast
frame-relay map ip 3.1.1.1 33
no frame-relay inverse-arp
My queries:
A- Does he use these two statements because (frame-relay map ip 3.1.1.3 22 and frame-relay map ip 3.1.1.1 33 ) of requirement number 2 ?
B- Doesnt he use keyword broadcast in these two statements (frame-relay map ip 3.1.1.3 22 and frame-relay map ip 3.1.1.1 33) because of requirement 5?
C- Does that mean if requirement 5 is not there we should have used broadcast keyword ?
D- Does not that contradict with what Cisco syas: The broadcast keyword is commonly used with the frame relay map command ?
E- By using these two statements (frame-relay map ip 3.1.1.3 22 and frame-relay map ip 3.1.1.1 33) doesnt my network become full mesh? but if you look to the diagram it is partial mesh ?

Answers to your queries:
A. Correct
B. Correct
C. That depends. In most cases, it is a good idea to have broadcasts on, especially when using routing protocols like OSPF which send traffic to multicast destinations. I would habe it on most times.
D. The recommendation from Cisco is not contradictory. The lab scenario is making you do something quite specific so you have to follow that. You don't always have to follow requirements in order to make things work.
E. No. Full-mesh refers to a full mesh of PVCs. If there was a PVC from A to C it would be full mesh.
Hope that helps - pls rate the post if it does.
Paresh

Quicktime multicast

Dear all,
We are developing and streaming video platform, encoding the video in h.264, and then encapsulated in rtp packets.
We are trying differents approachs, namely unicast and multicast.
In unicast we are sending the stream to QTSS, with the client connecting to QTSS to view either a live or pre-recorded content.
Our big issue is with live streaming, in which QTSS acts as a simple relay ... it seems unnecessary as the only thing done is a previous rtsp initialization.
This is why we are trying to use multicast. Maybe we are wrong in our approach, but isn't possible to stream just the rtp packets generated by the encoder to a multicast address and then the client connects directly using this multicast address? (In this scenario we don't have QTSS)
Can Quicktime play multicast streams directly? It is needed any session protocol(RTSP,SAP,SIP)? It is mandatory the use of QTSS to view multicast streams?
Thanks in advance,
A.Silva

Can you say the steps you took to make the movie that the viewer use? I've done multicast, and I've tried typing in the IP numbers and not got too far, but when I did an export movie, and used that, the other machine saw the feed right away.

Configuring Multicast for Video

I have a WAN network with frame-relay link (bandwidth 256Kbps)and conected to one there is a Catalyst 3550 doing Inter-VLAN. the switch port conected to router is routing (no switchport) and all others ports of the switch are at VLAN 1 (default). The Video-conference Server is at VLAN 1. What are the basic requirements or requisites? Do I have to configure multicast routes (ip mroute)? Anybody have examples configurations? Thanks.

The following URLs might help you:
http://www.cisco.com/warp/public/473/94.html
http://www.cisco.com/warp/public/473/38.html
http://www.cisco.com/warp/public/473/22.html

DHCP Relay through another firewall

Hello,
I have set up two ISA Servers in my lab (learning environment).
One faces the internet, the other one is in between the lan and the perimetral network.
Sort of:
LAN <--- ISA2---> DMZ <---ISA1---> INTERNET.
The thing is that the other office connects to ISA1 through a VPN-Site-to-Site, and it goes all fine except that ISA1 cannot take any ip from the dhcp server standing on the lan.
I have read this: http://technet.microsoft.com/en-us/library/cc302680.aspx
But in my lab, there are two isa servers , so I don't know how to send dhcp requests from isa1 to isa2 excepto for broadcast 255.255.255.255 , but the isa1 does not know how to forward that to the dhcp server in the lan.
I am mixed up because I am not an expert and am learning now about this dhcp relay thing now.
Thanks in advance!!
Luis Olías Técnico/Admon Sistemas . Sevilla (España - Spain)

Thanks a lot Keith.
I was all wrong. The relation between perimeter and lan (in ISA2) is route. And as far as I have read, that is how it should be, when no external network is involved.
I have a question, I feel doubtful about: When ISA1 takes the DHCP request, does he make a broadcast petition to 255.255.255.255 or a unicast request directly to dhcp-server machine ? , because the ISA1 machine is a DHCP relay so, when I configured it I
was asked to write the ip of the dhcp server, then maybe it just knows where to send the dhcp requests from the client and does not perfom multicast 255.255.255.255 but unicast to the dhcp server ?
EDITION: In the statistics of dhcp-server, there is no dhcp requests, so the traffic is not reaching it.
I am still digging in. This is difficult for me.
Luis Olías Técnico/Admon Sistemas . Sevilla (España - Spain)

Vaibility of RTP relay server using JMF

Hello!
I am thinking of making an RTP server that would just relay the streams received from single user to multiple users.
I want to ask following questions:
1- Is it viable to make such a Server using JMF?
2- If it is, then how should I proceed?
3- Should I need to create Processor for each recieved stream at the server or just cloning the DataSource received and sending them using separate RTPManagers would solve my problem?
4- Is cloning of data source needed at all?
I am asking this before doing any coding just in case if it is not possible than you warn me ,and because I had real bad experiences while cloning the data source and this server, I think depends on cloning.
Else, I want some help regarding code. I would highly appreciate some code snippets.
Thanks in advance.
Thanks!
P.S.: captfoss, Are you listening?

Now some simple questions from a novice, thats me:I will answer them out of order
3- Are these terms specific to JMF or are they general Networking terms?They are general networking terms.
2- What is difference b/w unicasting and multicasting?Uni = Latin prefix for "one".
Multi = Latin prefix for "many"
Broad = Latin prefix for "all" (okay, this one is probably not true, but...)
unicast = sending data to a single recipient.
broadcast = sending data to all recipients.
multicasting = sending data to many recipients.
It deals with how the underlaying UDP packets are handled.
Unicast addresses the packets to a specific host, so all other hosts that receive those packets go "Not for me" and ignore it.
Broadcast addresses the packets to a special IP address, the broadcast ip, so all hosts that receive it say "Oh, this is a broadcast message so it's for me"
Multicast addresses the packets to an IP address in a special range (Class D addresses), and all hosts can opt to join in to the "multicast session". If they join the multicast session, it basiclly means when they receive packets addressed to any multicast addresses that they have joined the session of, they will consider those packets to be "for them".
1- What exactly is multicasting in JMF?JMF multicasting is basiclly where the "host" can send out a single stream, and any number of "clients" can receive the stream.
4- How multicasting is handled at Transmitter and Reciever side using JMF, some java statements please.Multicasting is almost handled "automaticlly".
It's handled by giving the transmitter a multicast IP address to send to. "224.123.123.123" is an example of the one I always used for testing (because it was easy to remember). Transmitting multicast packets is handled automaticlly.
Receiving multicast packets requires a little special handling.
From AVReceive2.java
if( ipAddr.isMulticastAddress()) {
    // local and remote address pairs are identical:
    localAddr= new SessionAddress( ipAddr,
                       session.port,
                       session.ttl);
    destAddr = new SessionAddress( ipAddr,
                       session.port,
                       session.ttl);
} else {
    localAddr= new SessionAddress( InetAddress.getLocalHost(),
                            session.port);
    destAddr = new SessionAddress( ipAddr, session.port);
}The main difference here is that your "local" address isn't going to be LocalHost address, "127.0.0.1", it's going to be the multicast address.
And you should define the TTL (time to live) for the SessionAddress because multicast packets can only travel a certain number of "hops" (number of times forwarded).
But honestly, I'm pretty sure I ripped that IF statement out and multicasting still worked (but I define the TTL for unicast as well, so bear that in mind...)
Ignoring all of the stuff above, multicasting is a great idea for a local LAN application where there are no routers between the host and the clients. If you've got a router between them, then the router may not forward the multicast packets and your stream may never get to the remote clients.
That's why in my project, which is web based, clients attempt to get the multicast packets and if they fail at that, then they request a unicast from my server.

Cdp ? in Frame Relay environment

Hi,
I have set up a lab to look at F/R with a partial mesh and sub-interfaces.
I have 3 DTE routers connected to a Frame Switch. One Router named 'middle' has the sub-interfaces configured on it. The other 2 routers named 'Top' & 'Bottom' are just physical interfaces.
I used RIP to route the two networks between Top & Middle and Bottom & Middle respectively. The F/R side has gone well, however, CDP switched itself off on both of the physical interfaces on routers Top & Bottom !!!
Is there a good reason for this ?
To rectify this I have simply enabled cdp on both the serial interfaces.
Regards,
Phil.

Hi Phil,
CDP is disabled by default on (physical) serial interfaces configured for frame-relay encapsulation. That is also the case on multipoint frame-relay interfaces. That is standard IOS behaviour. I think it's due to the fact that these interface types do not inherently support multicast.
Hope that helps - pls rate the post if it does.
Paresh

Benifits of point to point over multipoint on frame relay

Can anyone tell me what the above is ?

This is a big area of discussion and difficult to summarise. There are pro's and con's for configuring frame-relay on p2p, p2m and on the physical interface. It really depends on your design requirements. P2P as the name suggests just has 2 devices connected while P2M can be hub and spoke or full/partial mesh. routing protocols work in different ways depending on how the frame-relay is configured (see ospf network types and eigrp/rip split horizon). The choice of frame-relay interface also has implication on how multicast will work.
So to summarise, if you have many frame PVC's in a hub and spoke topology and use P2P you will end up with lots of subinterface which may be undesirable. P2M can get around this issue as the spoke will only need one interface, but there are other issues to think about if you use P2M.

Multicast chat program

Hi,
The problem I am having is when checking to see if two specific users are using the chat program as I want them to have a separate multicast session. The if statements work and the client sends the message. The server just doesn't seem to relay it back to the client in either case.
The code for the client part is below:
if (userName.startsWith ("Steve") || userName.startsWith ("David"))
MulticastSocket socket = new MulticastSocket (4447);
InetAddress address = InetAddress.getByName ("233.0.0.13");
          socket.joinGroup (address);
else
MulticastSocket socket = new MulticastSocket (4449);
InetAddress address = InetAddress.getByName ("232.0.0.13");
          socket.joinGroup (address);
And the server part:
if (received.startsWith ("Steve") || received.startsWith ("David"))
InetAddress group = InetAddress.getByName ("233.0.0.13");
packet = new DatagramPacket (buf, buf.length, group, 4447);
socket.send (packet);
else
InetAddress group = InetAddress.getByName ("232.0.0.13");
packet = new DatagramPacket (buf, buf.length, group, 4449);
socket.send (packet);
Does anyone have any ideas??

Chat Client Full Code
public class MulticastChatClient extends MulticastChatClientGUI
public ButtonHandler bHandler;
     DatagramSocket socket;
     String ipAddress;
String userName;
String passWord;
String msgToBuf;
String logMsg= "";
     String checkBye;
     Boolean authenticatedUser;
     String deNullString (String s)
     //Function to get rid of garbage at the end of the buffer prior to
     //displaying it on the screen and saving to file.
          String result = "";
          int i = 0;
          while (s.charAt(i) != '\0')
               result = result + s.charAt(i);
               i ++;
          return result;
     public MulticastChatClient (String title)
          super (title);
          bHandler = new ButtonHandler();
     sendButton.addActionListener( bHandler );
     try
               socket = new DatagramSocket ();
          catch (IOException e)
private class ButtonHandler implements ActionListener
     public void actionPerformed (ActionEvent event) //throws IOException
               // Get a datagram socket
               try
                    byte[] buf = new byte[128];
                    InetAddress address = InetAddress.getByName (ipAddress);
                    //Put username before the message the user sends
                    msgToBuf=userName + " Says >> ";
                    //Populate buffer with text in the txArea
                    msgToBuf=msgToBuf + txArea.getText();
                    buf = msgToBuf.getBytes();
     //Open up port 4448 and prepare to send the packet
                    DatagramPacket packet = new DatagramPacket (buf, buf.length, address, 4448);
                    System.out.println ("About to send packet");
                    //Send the packet to the server
                    socket.send(packet);
                    System.out.println ("Packet sent");
catch (IOException e)
                    //Error handling
          System.err.println("Couldn't get I/O for the connection to the server");
     System.exit(1);
     public void run () throws IOException
     //Welcome user, ask for their name
          userName = JOptionPane.showInputDialog(null,"Please enter your name...",
          "Welcome To Chat V1.0",JOptionPane.QUESTION_MESSAGE);
          //Password verification
          //Promt user to enter password
          passWord = JOptionPane.showInputDialog(null,"Please enter password...",
          "User Authentication",JOptionPane.QUESTION_MESSAGE);
          if(passWord.equals ("letmein"))
               //Correct password
               authenticatedUser = true;
          else
               //Wrong password
               authenticatedUser = false;
               //Inform the user and close the application
               JOptionPane.showMessageDialog(null, "Wrong Password, Chat program ended",
               "Authenticaion Failure",JOptionPane.INFORMATION_MESSAGE);
               System.exit(1);
          //User To Enter IP Address
          ipAddress = JOptionPane.showInputDialog(null, "Thanks " userName "... Please Enter Server IP",
          "Connection Details",JOptionPane.QUESTION_MESSAGE);
          // set up connection to multicast server
if (userName.startsWith ("Steve") || userName.startsWith ("David"))
MulticastSocket socket = new MulticastSocket (4447);
InetAddress address = InetAddress.getByName ("233.0.0.13");
          socket.joinGroup (address);
else
MulticastSocket socket = new MulticastSocket (4449);
InetAddress address = InetAddress.getByName ("232.0.0.13");
          socket.joinGroup (address);
          while (true)
               // send request
               byte[] buf = new byte[128];
               DatagramPacket packet = new DatagramPacket (buf, buf.length);
               socket.receive (packet);
               System.out.println ("Received packet");
               // display response
               String received = new String (packet.getData());
               System.out.println ("Remote packet: " + received);
               logMsg = logMsg + "\n" + deNullString (received);
               checkBye = txArea.getText();
                    if (checkBye.equals ("Bye"))
                         try
                         //Create log file ClientMsg.log, outFile is used to operate on it
                         BufferedWriter outFile = new BufferedWriter (new FileWriter ("ClientMsg.log"));
                         outFile.write (logMsg);
                         outFile.close();
                         catch (IOException i){}
                    //Tell user the program is about to close
                    JOptionPane.showMessageDialog(null, "You terminated connection, Chat program ended",
                    "Session Info",JOptionPane.INFORMATION_MESSAGE);
                    System.exit(0);
     rxArea.setText (rxArea.getText() + "\n" + deNullString (received));
Chat Server Full Code:
public class MulticastChatServer
public static void main(String[] args) throws java.io.IOException
          //Open up socket and listen on port 4448
          DatagramSocket socket = new DatagramSocket (4448);
          DatagramPacket packet;
          //Variable to hold all messages
          String logMsg="";
          System.out.println ("Starting Multicast Chat Server");
          //Loop forever
while (true)
try
                    //Setup a 128 Byte array
byte[] buf = new byte[128];
// receive packet
          packet = new DatagramPacket (buf, buf.length);
          socket.receive (packet);
          InetAddress address = packet.getAddress ();
          int port = packet.getPort ();
          //Convert buffer into a string
          String received = new String (packet.getData());
          //Add the IP address to the packet received
          //received = "(" + address + ") " + received;
          //Print received message on the console
                    System.out.println (received);
                    //Put the data into the buffer
                    buf = received.getBytes ();
                    //Write message to the message log variable
                    logMsg = logMsg + "\n" + received;
                         try
                              //Create log file ClientMsg.log, outFile is used to operate on it
                              BufferedWriter outFile = new BufferedWriter (new FileWriter ("ServerMsg.log"));
                              //Write the contents of logMsg to the file
                              outFile.write (logMsg);
                              //Close the file
                              outFile.close();
                         catch (IOException i){}
          // multicast it
          if (received.startsWith ("Steve") || received.startsWith ("David"))
          System.out.println ("met");
          InetAddress group = InetAddress.getByName ("233.0.0.13");
packet = new DatagramPacket (buf, buf.length, group, 4447);
socket.send (packet);
System.out.println ("met2");
          else
InetAddress group = InetAddress.getByName ("232.0.0.13");
packet = new DatagramPacket (buf, buf.length, group, 4449);
socket.send (packet);
               catch (IOException e)
e.printStackTrace();
}

Multicast packets on trunks

I have two switches connected via ISL trunks. Multicast packets can't get from one switch to the other even though the source and destination are on the same VLAN and is trunked. Shouldn't the switch just pass it on like other layer 2 frames?

The difference is that EIGRP speakers have signaled their intent to listen to multicast traffic. So IGMP Snooping functionality relays that multicast traffic to them.
See
http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008059a9df.shtml
for several solutions to this issue.
Yet another reason to not like NLB....
Michael

NetBoot across subnets with a bootpd relay

Hello Apple Community!
I've got 4 subnets at my school, each with various Macs around campus. I have a Mavericks server on each subnet currently, each with their own NetBoot images. It's a pain to keep everything updated. I can get a single client Mac (pre-2011) to boot across subnets using the bless command, but that's not really a viable solution for us to run a bless command on each client every single time we want to netboot. So far, the solution has been just to have dedicated netboot servers on each subnet, but I know there has to be a better way.
This article (OS X Server: How to use NetBoot across subnets - Apple Support) describes three different methods for netbooting across subnets, but two of them are not really viable for us. Those involve reconfiguring the network to allow BootP data to pass across subnets or configuring one server with multiple network connections, one for each subnet. However, option #2 describes configuring a bootpd relay. Based on my reading, this sounds like exactly what I need. However, I can't find any good documentation to walk me through setting it up.
I've thoroughly read the bootpd man page, which has had me editing the /etc/bootpd.plist on multiple servers. This hasn't gotten me very far. My clients still don't see the remote NetBoot server. It seems like the relay is supposed to redirect broadcasts from the remote Netboot server, through a local NetBoot server to the client. But I have no idea how to make this work.
Could someone please give me more guidance on what I'm supposed to be doing here? I'd like to host a single NetBoot server and have any client on any subnet be able to option-boot to see the NetBoot startup options (I have multiple NetBoot images, from Apple Service Toolkit to DeployStudio and Mavericks/Yosemite installers in between). Even if I could get it to just netboot to one default source (AST), I could deal with that. I'm also happy to host multiple NetBoot servers, but with all my NetBoot images in one location. I'm stumped in this multiple subnet environment and I need help. Please help.

Thanks again for your feedback. I had forgotten I left the "tftp://" on the IP address. Though, I've tried that multiple ways, starting with IP only. Also, per the bootpd man page (https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/ man8/bootpd.8.html), <allow/> and <deny/> are lists for MAC address allowances and when nothing is defined everything goes through. These are there by default, though I will remove them and see what happens. Also, according to the man page, bootp_enabled enables on all connections when a boolean is set rather than an array. Though I will still change this also and see what happens. The array that comes after the netboot_disabled key is auto-generated by NetInstall when you turn the service on in Server.app.
Essentially, that plist comes from a fresh activation of NetInstall. I deleted the previous .plist, rebooted the server and when I turned on NetInstall, that's what was created, plus my bootp modifications.
All that said, you said that you assumed I started the relay with the 'debug & logging' options enabled. I haven't started the relay in any active sense. So far, I've just been modifying this .plist, and rebooting a bunch of times, but that's where I seem to get lost. Is there a way to actively "start" the relay? I'd love to look at these 'debug & logging' options. As for the 'Startup Disk' prefs on the client Mac, they do not show any significant change. Basically, they just don't see the remote server as a startup option. I have not gleaned any pertinent info from console, though I'm not sure I know what I'm looking for.
On a side note, I had a wild hair to try something different. I set my local subnet's server to look at a NetBootSP0 folder that was actually a symlink to a NetBootSP0 folder that was mounted as a file share from the remote NetBoot server. This really looked like it might work. When you boot the client, it saw the startup volumes from the remote server. However, upon boot, it doesn't seem to make the connection and winds up booting back to the internal hard drive. It was worth a try...

Disabling Multicast in Solaris 10

Hi,
I have been searching the internet all morning trying to figure out how to disable solaris 10 multicast. I have no need for it. The best information I could find was to modify the script /lib/svc/method/net-svc and comment out the adding of a route point for multicast near the end of the script.
I thought that hand modifying the methods of SMF was a big no no in solaris 10. Is there a better way to disable multicast?
For instance, if I do an ifconfig -a I see that all of my intefaces have the MULTICAST flag set. Is there a way in ifconfig to disable that flag?
I have seen people put ifconfig options into their /etc/hostname.interface file. I think if I can find the correct ficonfig option I can disable the multicast flag during system boot and that should disable multicast.
Any comments/suggestions would be welcome.
Eric

Now that I have done more research I guess I do not have to turn off the multicasting.
This problem appeared because during snoop sessions I see MANY of the following messages:
? -> (multicast) ETHER Type = 022C ... 53 bytes
I assumed that one of my machines was doing the multicast. However, I shut down all but one machine and then I removed the multicast route from the route table and the messages still appear. I think that either my cisco switch or cisco router is doing the multicast.
So I guess I will not turn off the multicast on the machines.
Does it make sense that the router and/or switch is sending out the multicasts?

Multicast relay

Similar Messages

Maybe you are looking for