Flex 6600 defaults back to IP 172.30.1.1 although 192.168.0.33 set as static.

Frank ON9CC

Hi community,

I've noticed an odd thing with the configuration of the IP address of my Flex 6600. I had set it up with a static IP address 192.168.0.33 in my router and in the Flex. Also had port forwarding (TCP 4994 & UPD 4993) to that IP address setup in my router. All working without issues for many months. My contest buddy uses the Flex from remote (with SmartSDR or Maestro), hence this setup.

Today checking my router I noticed that the IP address of the flex was not 192.168.0.33 but it is 172.30.1.1 instead. So I checked numerous things:

• flex is still with 192.168.0.33 in the router setup for fixed IP, but looking at the connected list it states 172.30.1.1. (with the comment: "Static, Device side"
  
• Looking at the radio config in SmartSDR, I have it setup as fixed IP address. Changing to DHCP, makes no difference.
  
• rebooted the Flex, even making it powerless
  
• rebooted the internet router
  
• reset the internet router back to factory settings (had a back-up of the settings made back in January which I restored after the factory reset)
• MAC address is correct
  

Looking at SmartSDR (using v3.9.19), Radio setup>Network, it is set at DHCP and it says Network IP address 192.168.0.33 which is correct.

But here is the real strange thing. Looking at my router overview of what is connected, the Flex is shown as connected as 192.168.0.33 DURING BOOTING (up or down) ONLY. So as long as the green ON/OFF switch on the Flex is blinking, my router shows the correct FIX IP address and also a small logo for FIX IP and Port Forwarding. However, as soon as the Flex is fully booted and the ON/OFF switch remains green, the IP address changes to 172.30.1.1 and the 2 small logo’s (for FIX IP and Port Forwarding) disappear. Some goes as soon as I swith of the Flex and it is booting down. During booting down, the correct IP address is shown.

We’ve been checking if this has any effect on the remote operations, but that seems not the case. However we just can’t get our heads around this IP address issue. Anyone has any idea how to solve this and keep the correct IP address?

Thanks in advance for any help.

73 Frank ON9CC

Eric-KE5DTO

The radio uses the 172.30.1.1 address internally. I'm surprised to see that making it to your router as I wouldn't think this would escape the box. The IP itself is not a problem and is required for proper operation (internal communication).

Erik Carling EI4KF

I know nothing for certain. 172.30.1.1 looks like the gateway address of an internal service network, maybe SmartLink. Since you have port forwarding rules, I wonder if you also have UPnP enabled as well. If so try turning that off. Since the router appears to be trusting a UPnP announcement over the DHCP/static lease, disabling UPnP (in the router's network/security settings) should stop it from being told to reassign the displayed IP. This assumes you have it enabled, if not then sorry simply ignore, just a thought.

Frank ON9CC

Hi Erik,

Thanks for your response! I just checked the router settings, but UPnP is switched OFF.

73 Frank

Erik Carling EI4KF

Hi Frank, I think you should state here your make / type of Router in case someone has the same. Some routers have more than one UPnP setting eg 'Allow UPnP to configure port forwarding automatically' and 'Transmit status information via UPnP'. Letting the Community know what you have may help with generating ideas. Assuming the issue is due to router configuration which it might not be, but cannot hurt to know the hardware.

Frank ON9CC

I'm using a Siligence TCG300 modem. Provider is Orange (Belgium).

Erik Carling EI4KF

OK so that is Orange Belgium ISP supplied and fairly basic. I wonder if it is something to do with SmartLink itself. Maybe Flex themselves would know or Mike VA3MW as he's the man for Flex SL and networking. You could ask or he might reply here for you.

Mike-VA3MW

My only guess is that the radio's DHCP request is being honoured by some sort of DHCP server that uses that block of private addresses.

I would make 100% sure you aren't running 2 DHCP servers on the same subnet.

You need to solve this part before doing anything else.

Mike-VA3MW

@Eric-KE5DTO thanks for that as I wasn't aware.

Frank ON9CC

Thanks all for your comments/ideas so far. I will check for those 2 DHCP servers on the subnet. Have a Mesh network (TP Link Deco's) for wireless communication inside the house. I think that is on another subnet. But will do some checks and report my findings.