Messages

1

General Discussion / Re: DHCP-relay-clients don't get IP from Opnsense 22.1 DHCP server

« on: April 15, 2022, 09:20:29 pm »

Yes that is the future plan. As soon as I get my hands on a managed 24 port switch. And when I get opnsense totally up with wireguard and everything. Baby steps. All in time.

Sent from my POCOPHONE F1 using Tapatalk

2

General Discussion / Re: DHCP-relay clients don't get IP from Opnsense 22.1 DHCP server

« on: April 15, 2022, 02:06:07 pm »

Thank you for helping me out during this trial and error fase. It's working in production now with version 21.7.6.
Just have to remember not to update

About my IP subnet and numbering. The third # in is the type of device (IoT, Network, Surveillance, Guests). The fourth # in line is 001-099 is base floor of the house, 100-149 is first floor and 200-249 is second floor. Sadly I don't have more floors

3

General Discussion / Re: AP's don't get IP from Opnsense DHCP server

« on: April 14, 2022, 09:38:22 pm »

I started drawing. But that would take me years to do. Don't have the skills.

It's simple. I've made a new (test) setup at home. The only devices in it are:
- MAC
- Switch (Mikrotik)
- AP (TP-Link)
- Phone (Android)
- Router (NanoPi with opnsense)
I started this setup with a factory default config of opnsense (aka 192.168.1.1 as router, wan not connected).
I changed nothing, and neither the switch nor the AP got an IP from the DHCP server.

So my conclusion is that there is something wrong with opnsense. Not with the hardware. Because if I boot the NanoPi with the openwrt software everything works out of the box.

UPDATE: I downgraded from opnsense 22.1 to 21.7.6 and in my test setup it looks like it's working. I will test tomorrow in my production setup.

4

General Discussion / Re: AP's don't get IP from Opnsense DHCP server

« on: April 14, 2022, 08:11:55 pm »

Thank you again for thinking with me. The subnet and range I will explain later, it's not important right now.
The switch I have is an unmanaged TP-Link switch. So no vlans there since it's layer 2. The unifi AP's I have defaulted many times already. I must say I haven't tested it without the switch in between because the nanopi only has 1 lan port.

The odd part is that the same setup works out of the box when I install openwrt on the nanopi. So that tells me opnsense is missing out on something openwrt clearly can do better. The problem is that I don't like openwrt at all. I find the UI very disturbingly bad.

UPDATE: the problem is way bigger then just AP's. Just made a test setup with only my Mac an old managed switch (mikrotik) and the opnsense router (nanopi). But the managed switch isn't getting an IP either. Though with the switch DHCP relay works for other devices connected. With the AP (in test setup still not getting an IP) the relay doesn't work either.

UPDATE2: Fun fact about the nanopi, you can easily put in a different SD card and boot with a different setup. So I picked up another SD card flashed 22.1 on it and booted. Changed nothing and this was the outcome in the DHCP log:

Code: [Select]

2022-02-13T06:33:02 Informational dhcpd DHCPOFFER on 192.168.1.100 to 6c:3b:6b:c4:56:8a (Switch) via re0
2022-02-13T06:33:02 Informational dhcpd DHCPDISCOVER from 6c:3b:6b:c4:56:8a (Switch) via re0
2022-02-13T06:33:02 Informational dhcpd DHCPOFFER on 192.168.1.101 to 14:eb:b6:e0:b4:c2 (EAP620-HD-14-EB-B6-E0-B4-C2) via re0
2022-02-13T06:33:02 Informational dhcpd DHCPDISCOVER from 14:eb:b6:e0:b4:c2 (EAP620-HD-14-EB-B6-E0-B4-C2) via re0

5

General Discussion / Re: AP's don't get IP from Opnsense DHCP server

« on: April 14, 2022, 08:56:41 am »

Thank you for your time and effort to help me.

Herewith the screenshots of the opnsense config so far. I choose 10.0.0.0/16 as my range just because it is easy to remember and my ISP modem/router already uses 192.168.1.1, so otherwise that would maybe give problems.

The TP-link config I have disconnected again. But it was set to dynamic IP (DHCP client). TP-link has a static fallback address which was the one I used to manage the AP (setting my laptop in the same range with a static IP to make it work).

UPDATE: On the NanoPi R4S it's possible to install OpenWRT (not my choice of software though). But if I install that and run it. All AP's get an IP. So the problem is really Opnsense related.

6

General Discussion / Re: AP's don't get IP from Opnsense DHCP server

« on: April 13, 2022, 10:30:56 pm »

It's exactly like you discribed. But I'm not toying with vlans. It's a very simple setup. And all my 20 other devices are getting ip's. Only the AP's don't. And devices connected through an AP.

Sent from my POCOPHONE F1 using Tapatalk

7

General Discussion / DHCP-relay-clients don't get IP from Opnsense 22.1 DHCP server

« on: April 13, 2022, 11:50:04 am »

I'm new here, and to opnsense. So please bare with me. I just replaced my Ubiquity edgerouter with a NanoPi R4S with opnsense 22.1 on it. It works like a charm, except my for my wifi.
My wifi is run by two Unifi AP's but the problem is that they don't get an IP from the DHCP server. So because of that I can't adopt them in my unifi controller and can't get them to work.
My DHCP log:

Code: [Select]

2022-04-13T11:45:07 Informational dhcpd DHCPOFFER on 10.0.0.153 to f0:9f:c2:20:d3:b6 via re0
2022-04-13T11:45:06 Informational dhcpd DHCPDISCOVER from f0:9f:c2:20:d3:b6 via re0
And that is where it ends. no ACK. Now I have searched everywhere for a sollution. But can't find any. My DHCP server is set to default. I have tried 1 AP with a static IP mapping and the other dynamic. But both have the same outcome. Can anybody help me please? Thank you in advance!

UPDATE: I've borrowed an TP-link EAP 620HD from a friend. But it has the same issue. No IP is given by the DHCP server. Do these devices need any other settings in opnsense?

UPDATE2: The TP-Link AP I can give a static IP. It still does not appear in the lease list of opnsense. And it still won't relay traffic. I can reach it via my browser and manage the AP. But if I try to connect a phone through the AP, the phone won't get an IP from opnsense.