@Hank21 it doesn't actually. The 169.x.x.x IP that is discussed in the other topic is a virtual IP and also used as APIPA. The IP I'm referring to is an actual IP-address belonging to an organisation in Tampa, Florida while I'm in the Netherlands and didn't add any routing-rules which would add such an IP-address.

Yes, I have set-up multiple VLANs with ACLs, no advanced options on them like Option 60 for example. I also have one VPN server profile, using OpenVPN. My controller software version is 5.0.30 running on an OC200 with firmware version 1.14.3 Build 20220112 Rel.64116. Last weekend I've updated the router to 1.2.0.

  @NHendriks I think it is still the "virtual" IP for multi-VLAN routing. The trick is, if you connect the Router's WAN port to another router's(let's call it Router B) LAN local network (Router B without Internet), and try tracert(trace route) the Router B's IP address , you will still see this "IP"  shown as the hops. It can't be the real IP since there is no Internet only in local network. 

@NHendriks but if it's a "virtual IP" shouldn't it be in the proper subnet as designated by IANA (talking about the APIPA-range) and not some random IP-address of a community in another part of the world? I'm connected directly to the network terminator of my ISP. I do have a second router connected via WAN as a 4G back-up connection on WAN/LAN1.

@Somnus I still think that's a weird way of doing it. There are plenty of private IP-addresses that TP-Link could've picked but instead they pick some public ones which might cause some IP-conflicts in the process because that's how networking works. There are millions of non-public IP's to choose from and yet, TP-Link chooses some public IP. I find that hard to believe.

  Hello @NHendriks ,

i agree with you. That's no private adress. You are right  with the school community.

I personally would delete the route, change my routers password and check what is happening the next view days.

If there is se tup a Network under Lan according to this ip, i would also delete that.

Greatings

A couple of months have passed but still no solution. The software upgrades didn't help with this issue either. I have no rules or something set-up for data to go this IP-address and TP-Link fails to come with a proper answer. Very disappointed..