-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No DHCP in VLAN subnets when GeoIP filtering is enabled #8
Comments
The reference to pve-edge-kernel is incorrect, I did not update the link to refer to this project. As for the DHCP issue, I suspect that it is related to the firmware version 1.8.6 you are running. For example, there might be a small chance that the kernel for 1.9.0 is not compatible with firmware version 1.8.6. I am currently on 1.9.3 and cannot reproduce the issue. Does |
First of all: It works now! :) In the log I see that there is a problem with GeoIP filtering and therefore all DHCP servers are stopped. With enabled GeoIP filtering:
With disabled GeoIP filtering:
Thanks for this great project. 👍 |
Great to hear! I wonder why iptables-restore fails when enabling GeoIP filtering though. I suspect it may be related to some changes Ubiquiti did to the netfilter implementation from 1.8.6 to 1.9.0. |
I have multiple subnets and VLAN that the UDMP manages.
UDMP is running with firmware 1.8.6
My subnets:
192.168.1.0/24 Management (no VLAN)
10.0.10.0/24 Main VLAN 10
10.0.20.0/24 IOT VLAN 20
After booting the custom kernel everything works.
Traffic between subnets and Internet works.
IPTV works.
The only thing that does not work is the DHCP address assignment in the subnets with VLAN.
The clients do not get an IP address.
Clients from the subnet without VLAN get an IP address.
After restoring the stock kernel it works.
I use:
udm-kernel-tools_1.0.0_arm64.deb
udm-kernel-4.1.37-edge1_4.1.37-edge1-1_arm64.deb
What I don't understand, what do I need to do with the packages from pve-edge-kernel?
Any ideas what the problem with DHCP could be?
The text was updated successfully, but these errors were encountered: