Not able to get HA in IP range of vlan subnet

Hi

I have a Odroid N2+ together with Ubiquiti router.
For my iot devices I created a separate vlan.

My Odroid is connected via a cable. But my router keeps assigning an ip adress in my default network range.
When I manually assign an ip adress in my router HA will not take it.(HA network configurated automatic)
Sometimes it is unreachable and sometimes it keeps working on the ip adress assigned by the dhcp server of my default network.

Already tried to set a static ip in HA and the router, without succes :sleepy:

Range of my default network 192.168.1.x
Vlan is 192.168.30.x

Somebody who knows how to get out of this?

Check what the netmask is set to in HA. The default was a stupid value and may not have been fixed yet.

Settings → System → Network → (your adapter) → IPv4

There I have 255.255.255.0

Seems ok? I not a networking pro…

1 Like

No. You are using the second octet. So 255.255.0.0

Eh not necessarily. @tom_l

The ‘second octet’ defines the network op only needs to define that if they’re creating a class b segment which in home use is HIGHLY unlikely There’s something else going on. If they can’t REACH that network due to routing/firewall rules however?

Op what happens if you manually assign the ip/net ask you want in HA on box without using dhcp?

Something tells me you are encountering some kind of routing issue. Also it’ll be helpful to know ALL the networks in play here and how you intend them to connect to one another.

1 Like

Sorry that should have been 255.255.224.0 look at the range their VLAN is in.

Next. question is what is your gateway ip set to?

@tom_l the gateway of the vlan. 192.168.30.1

Stupid question: You are checking the IPv4 address in the HA System menu, and not from the HA command line?
(…as the HA OS host OS includes a router to internal to HA only container IPv4 LANs. After a quick check, the internal IPv4s are 172.30.0.0 so NO - remembered the .30 was in there somewhere!)

As has been mentioned, you might not have a “Class B” VLAN segment (broadcast 255.255.0.0/16) , but CIDR which means you need understand the real VLAN network mask (i.e. how many bits in the IPv4 address space are network, likely between /16 and /24) from the Ubiquity network GUI.

Plug the network mask into a CIDR calculator to get all the VLAN IPv4 values…
https://www.ipaddressguide.com/cidr

The other option is to move the HA LAN port to the main default VLAN, and set up routing rules between the VLANs with the IoT VLAN / SSID (say) barred from Internet access to prevent updates. This gets complicated quickly as IoT uses a lot of multicast for mDNS (e.g Matter) which Ubiquity can broadcast but it needs to be enabled.

(I only play a CCIE on conference calls! :slight_smile: :mage:)

1 Like

:rofl::rofl::rofl: I uninstall my MCSE on weekends. :wink:

Agreed. I think this is a subnet / DHCP issue. Someone needs to diagram the intended configuration. :wink:

2 Likes

Iot network

Main network

Great - that defines two distinct networks what’s routing between them? That’s Unifi gear. Is that a UDM or?

If you’re using Unifi’s stuff, have you upgraded to Network 9

How have you setup DHCP to give out those addresses? Is it on a separate VLAN? Isolated segment?

So that makes this is the most interesting place in your network config for those two networks: (Settings > networks > pick one)

1 Like

@Pieres If connected via cable, have you configured your physical port to be assigned to NIOT27 network instead of default? Navigate to ubiquiti device your odroid is connected to, select port manager (on pc web ui you find it in the right menu, in mobile app - click on the port where odroid connects to), then select physical port where it is connected to and make sure that “Native VLAN / Network” is set to NIOT27.
By default, it is always default and other vlans are only allowed in trunk.

To me, seems like this is the only issue. Your DHCP seems to work just fine, as you already have 17 leased IPs in that network. I assume you use that for wireless (distinct wifi network for iot devices, assigned to NIOT27 network)

image

image

@stomko thanks a lot. That fixed the problem. :pray: