Posted: Sat Aug 12, 2017 3:46 Post subject: VLAN trunks and Multiple DHCP
Brief history - Ran a WRT54G v2 with DD-WRT for a long time before it began to act up. Replaced it with a RT-N16 ASUS but never got around to putting DD-WRT on it.
Flash forward - I'm setting up a full cat6 setup and bought some Ubiquiti Unifi AP's and a Cloud Key controller. I want my kids and/or Guest WiFi to be on it's own vlan and separate subnet.
I'm running a Layer 3 Procurve switch behind my router, and all my vlans are setup there. What I need my RT-N16 to do is serve as a DHCP server to the other VLAN(s), since the switch is too old to act as a DHCP server itself (HP 2910AL-24G)
Rather than set up the different ports on the RT-N16 for each VLAN, I want all the ports to be 802.1q ports, with the extra VLAN's being tagged
This was the original output of the key cmds from NVRAM:
I trunked all 4 ports, but right now it is plugged into port 1.
I didn't see the need to drunk VLAN 1 because that's the native vlan, and the native vlan doesn't need a tag. Does DD-WRT treat trunking differently that i have to have every vlan tagged?
If i marked vlan1="4t" (ie, port 4 vlan 1 becomes tagged), it broke my PC. PC failed to grab DHCP. (Right now, I have my PC plugged into that port instead of the switch, as I want to get this dhcp thing lined up before i switch to the L3Switch. I switched it back to a non trunked port on VLAN 1.
I plugged my laptop into Port 3 (otherwise marked LAN2 on the chassis), and the laptop failed to grab DHCP. Instead, it grabbed an APIPA address (169.254...)
If i move the laptop to port 2 (LAN3 on chassis), it works fine.
I assume to do that, you have to set it to "unbridged"? I thought the interface may already have had an IP address as i had issued a startup command via TELNET :
I did what you said and I'm getting an IP address on the laptop now. However, I am not routing out to the internet, nor can I ping the vlan10 interface, even though i'm getting the DHCP.
Is my rc_firewall setup right?
Code:
iptables -I INPUT -i vlan10 -j ACCEPT
iptables -I FORWARD -i vlan10 -o br0 -m state --state NEW -j ACCEPT
iptables -I FORWARD -i vlan10 -o vlan+ -m state --state NEW -j ACCEPT
Thinking about blowing away nvram and starting over. there's probably something wrong with the IPTables. I can't even ping the gateway IP (192.168.10.1) from the laptop, even though it gives me a DHCP address.