DHCP Issues with Tagged port

I’ve not been able to work this out, it seemed to be working fine when I had one WAN port configured, then it appears to have all stopped working when I introduced another WAN2 port using LAN3 port.

DHCP stopped working for all interfaces and packet loss rose.

I have one LAN port configured as a tagged interface, with two new vlans interfaces, eth0.171, eth0.171

It seems that I can’t use DHCP Server on any interface now. Do I need to remove the LAN3 port from br-lan ? Or have my policy based routing rules introduced a new issue.

packet trace shows requests, and invalid packets, I suspect this is because the eth interface is recieving a tagge packet and cannot parse it.

The odd thing is that if I connect a standalone PC directly to another port on br-lan, DHCP no longer works as well.

I see no DHCP replies when I run a packet trace on the RUTX11.

tcpdump: data link type LINUX_SLL2
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on any, link-type LINUX_SLL2 (Linux cooked v2), snapshot length 262144 bytes
15:26:55.224348 eth0  B   IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from bc:24:11:32:bd:24, length 300
15:26:55.224396 wlan0-1 Out IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from bc:24:11:32:bd:24, length 300
15:26:55.224435 wlan1-2 Out IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from bc:24:11:32:bd:24, length 300
15:26:55.224348 br-lan B   IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from bc:24:11:32:bd:24, length 300
15:26:55.613556 eth0  B   IP14 (invalid)
15:26:55.613556 eth0.171 B   IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from bc:24:11:11:ef:5e, length 298
15:26:56.132761 eth0  B   IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from bc:24:11:32:bd:24, length 294
15:26:56.132814 wlan0-1 Out IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from bc:24:11:32:bd:24, length 294
15:26:56.132856 wlan1-2 Out IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from bc:24:11:32:bd:24, length 294
15:26:56.132761 br-lan B   IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from bc:24:11:32:bd:24, length 294
15:27:02.475300 eth0  B   IP14 (invalid)
15:27:02.475300 eth0.171 B   IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from bc:24:11:11:ef:5e, length 300
15:27:04.178534 eth0  B   IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from bc:24:11:32:bd:24, length 300
15:27:04.178643 wlan0-1 Out IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from bc:24:11:32:bd:24, length 300
15:27:04.178694 wlan1-2 Out IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from bc:24:11:32:bd:24, length 300
15:27:04.178534 br-lan B   IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from bc:24:11:32:bd:24, length 300

Any help appreciated.

Thanks.

Ok I think I solved this one. I had to setup each interface on the private network side to be under the Listen interfaces. Once this was done, each interface gateway responded to the DHCP request with a reply fronm it’s own network.

Hope this assist someone else if they come across the same issues.

Thank you for sharing your solution, Dan!

I’ll mark your comment as the solution so others see it as well!

Regards,

M.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.