Skip to main content

Unable to Send Video Stream from VLC through Cisco Router

Today, while working on a multicast lab on Cisco Router. I build a lab to send multicast stream from one end to other end via VLC. I found that, while checking router with "show ip mroute" command , receiver PC was successful registering with Rendezvous Point Server to receive required multicast traffic but the Multicast source (Sender) was not registering with RP.
Upon a day's troubleshooting, i found in the packet capture that VLC Sender is sending multicast traffic with TTL Value 1, this is default behavior of VLC player and which will definitely be discarded by first receiving hop.
So I have to increase the TTL value little higher so that the multicast packets can traverse to some hops and reach the receiver.
To change the TTL value of the packet for sending multicast stream from VLC, you can change the default settings as per give below path and snap.

I also tried this in GNS3 and was working fine.

Go to Tools > Preferences >  Select ALL radio button at left bottom > Expand Stream Output >  Click Access output > Increase the TTL Value as per your network requirement or at least to 10


Note:- Restart VLC player after changing these settings. 

Comments

Popular posts from this blog

How to import Putty Saved Connections to mRemoteNG

Just started using mRemoteNG and its being very cool to connect to different remote connection with different protocols e.g Window Remote Desktop, VNC to Linux, SSH, HTTP connection etc. from a single application. As new user I configured some remote desktop connection which was quite easy to figure out. But when I wanted to add SSH connections, it came in my mind to import all of the saved connections in the putty. But I couldn't figure it out how can it be done, though it was quite easy and here are the steps. Open your mRemoteNG Create a folder if you want segregation of multiple networks Create a new connection Enter the IP address of remote server under connection in Config pane Under the config pane, select protocol " SSH version 2 ".  Once you select protocol to SSH version 2 you are given option to import putty sessions, as shown in the snap below. In the above snap, I have imported CSR-AWS session from my saved sessions in Putty.

Understanding PKI The Complete Process Explained

The Complete Public Key Infrastructure (PKI) Process: From Key Generation to Certificate Verification Public Key Infrastructure (PKI) is the backbone of secure communication on the internet. It ensures that sensitive data exchanged between clients and servers remains private and authentic. This blog post will guide you through the entire PKI process, from generating keys to verifying certificates and ensuring they haven't been revoked. 1. Key Pair Generation The first step in PKI is generating a public-private key pair using an asymmetric cryptographic algorithm, such as RSA or ECDSA: The private key is securely stored on the server and never shared. The public key is included in the certificate and shared with the Certificate Authority (CA) during the certificate request process. This key pair enables encryption and decryption, which are essential for secure communication. 2. Creating a Certificate Signing Request (CSR) The server creates a Certificate Signing Request (CSR) to...

BGP Soft Reconfiguration vs. Route Refresh: Key Differences and Best Practices

In BGP (Border Gateway Protocol), managing route updates and reapplying new policies can sometimes be challenging, especially if you want to avoid resetting the BGP session. Two methods allow you to update routing policies without tearing down the session: BGP Soft Reconfiguration and BGP Route Refresh . While both methods serve the same purpose, they work differently and have distinct impacts on your router's resources. This post explains the key differences between Soft Reconfiguration and Route Refresh , when to use each, and why Route Refresh is preferred in most modern networks. 1. What is BGP Soft Reconfiguration? BGP Soft Reconfiguration is an older method of applying new policies (like route maps, filters, or prefix lists) without resetting the BGP session. It works by storing a local copy of all the routes received from a BGP neighbor before applying inbound policies. This local route copy allows the router to reprocess the routes when a policy change occurs. How So...