• Get involved.
    We want your input!
    Apply for Membership and join the conversations about everything related to broadcasting.

    After we receive your registration, a moderator will review it. After your registration is approved, you will be permitted to post.
    If you use a disposable or false email address, your registration will be rejected.

    After your membership is approved, please take a minute to tell us a little bit about yourself.
    https://www.radiodiscussions.com/forums/introduce-yourself.1088/

    Thanks in advance and have fun!
    RadioDiscussions Administrators

Starlink STL using APT IP Codecs--Static IP Issue

A

AMJUNKIE

Our FM 100 kW transmitter is in a Communications Desert. We use APT IP Codecs for STL, which we love. APT has connections for 2 WAN's, and we want to switch one of those WANS from HughesNet (with static IP) to new StarLink (without static IP).

I think the APT's are supposed to have a static IP assigned to each WAN port. What suggestions do folks have?

At the studio end, we have a new StarLink AND an ATT fiber with static IP if that helps.

Thank you, Dave
 
If the apt codecs allow, (im not too familiar with them) use a dyndns address from no ip. real cheap and really reliable. I use a no ip dyndns address for a 2 pairs of barix boxes im using they have been ultra reliable.
 
If you're using Starlink commercial which gives you private IP's it should work fine. I've not done it personally, but I've heard some are using the Starlink DHCP version with APT codecs. One just needs to make the DHCP connection, then look up the IP being used via your router and plug that into your APT at the other end.
If you want the IP/STL traffic to route between your AT&T fiber with static IP and Starlink as a backup, you'll need a good quality managed router with a special BGP table at each end written to make that route when needed. Some BGP tables can be written to switch if there is a predetermined number of dropped or missing packets. You also may want to consider a firewall at the transmitter end, and make sure the studio end isn't anywhere near your production or business network. That way if someone breaks into either your Starlink or AT&T path, they're less likely to wreck the business with malware or more recently, ransomware.
 
Thank you for your comments. We have basic StarLink, so no private IP provided by StarLink.

When you make the DHCP connection mentioned by Kelly A, and then you feed audio via StarLink 24/7/365, would you expect DHCP to stay assigned for years?
 
AMJUNKIE said:
Thank you for your comments. We have basic StarLink, so no private IP provided by StarLink.

When you make the DHCP connection mentioned by Kelly A, and then you feed audio via StarLink 24/7/365, would you expect DHCP to stay assigned for years?
Click to expand...
What I would do is set up a routing NAT between the Starlink modem and your APT codec. In other words; connect your DHCP Starlink modem to a router, then set up a NAT in the router so no matter what IP shows up on Starlink, your APT plugged into the router port sees the same IP address and Gateway on it's end.

libvirt: NAT forwarding (aka "virtual networks")

libvirt, virtualization, virtualization API
wiki.libvirt.org wiki.libvirt.org
Check out 'section 3.5.3.3 of the manual from WorldCast that also talks about using their UPnP feature with NAT.
 
Last edited:
Status
This thread has been closed due to inactivity. You can create a new thread to discuss this topic.


Back
Top Bottom