NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Atem Mini Pro given 169.xx IP
I have an Atem Mini Pro connected via ethernet to an Orbi Satellite but given a 169 IP address.
Apologies in advance for my lack of understanding of networking. I am not very technical but below is the my set up and any checks I have done.
SET UP:
- Virgin Hub 3.0 in Bridge Mode
- Orbi Router (wired) to Virgin Hub in Router Mode providing IP etc.
- 2 x Orbi Satellites (1 downstairs and 1 in the office).
- These satellites are connected to main router wirelessly
Office:
- iMac connected via ethernet to Orbi Satellite - WORKS great.
- Atem Mini Pro via ethernet to Orbi Satellite - Not working. Given 169.xx IP.
Things I have tried:
- Put ethernet cable from Atem in to my iMac. My iMac still gets connectivity.
- Put ethernet cable from iMac to my Atem and Atem still doens't get connectivity - still given 169 IP.
- I have tried connecting the Atem to the router instead of the satellite - still given 169 IP
- I have unplugged my iMac from ethernet and turned on Wifi. I then plugged ethernet cable from Atem to my iMac, turned on internet sharing via Wifi using ethernet and the Atem finally gets a correct IP address of 192.xxx (but won't direct in to the satellite)
- I have rebooted the router - still no change
I have no idea why it's been given a 169 IP address when there is no problem with the cables or satellite is working fine and would really appreciate some help here if you can.
I have exhuasted my technical level so please, if any help advise me how / where I need to go to do what you suggest. It would be appreciated.
Thanks
9 Replies
northern1984 wrote:I have an Atem Mini Pro connected via ethernet to an Orbi Satellite but given a 169 IP address.
I have no idea why it's been given a 169 IP address when there is no problem with the cables or satellite is working fine and would really appreciate some help here if you can.
IP addresses starting with 169 are known as "Link-Local" addresses that are created by the device itself when it cannot reach a DHCP server.https://en.wikipedia.org/wiki/Link-local_address
Since the ethernet cables are good, my guess is that the Orbi may have Access Control enabled and will not allow new devices to connect.
p.s. I found the Atem Mini Pro user manual not particularly helpful in terms of how to connect to the network. For example, I did not find a section that describes how to put the device into DHCP vs. Static IP mode. (I quickly got confused between the Mini and the Streaming Bridge.You have both?)
CrimpOn Thanks for taking the time to respond. I have checked my Orbi router settings and I have 'Access Control' turned off.
Atem (from Blackmagic) is really hard to understand. I have the Atem Mini Pro which is a Switcher. The Streaming Bridge connects to the Atem Mini and allows an external source to 'stream' there feed in to it so think 'remote guest' on a Facebook / YouTube live stream
I have since:
- Turned off DHCP -> Saved profile -> Turned it back on -> saved -> rebooted router.
Cheers
northern1984 wrote:I have since:
- Turned off DHCP -> Saved profile -> Turned it back on -> saved -> rebooted router.
Cheers
Did this result in a connection?
If not, it might be a good idea to power off the Atem (or even 'reset' it?)
I am frustrated these days because my Windows 10 laptop fails to get an IP address when it 'wakes up'.
i.e. If I turn it on and it's connected to the router, it picks up the correct IP every time.
If I close the lid, and then later open the lid, wake it up, and log in, it does not get an IP.
I have recorded the LAN traffic in both situations. When powered on, laptop requests an IP, Orbi offers an IP, laptop accepts IP. Just as it is supposed to.
When I 'wake it up', the laptop keeps requesting an IP, Orbi offers IP, laptop requests IP, Orbi offers IP..... forever.
I can open the Windows control panel and use the Troubleshooter to "fix" the ethernet connection, but it's a pain.
My money is on something wrong with the Atem.
An alternative is to set a Static IP on the Atem. No DHCP that way.
Would not wonder if this link-local IP address is configured as a static IP - this the device does not use DHCP (when I remember right is active with the IP on 0.0.0.0.). Sorry, these are devices we dont get in our hands avery day. You could also challenge Blackmagic Design FMI.
schumaku Yes I am also challenging blackmagic so trying to resolve this both ends and see if its a Netgear or Atem problem
