Joined: 16 Nov 2015 Posts: 2047 Location: London,UK
Posted: Tue Dec 26, 2017 18:52 Post subject:
i had a believe m multiport is stripped of or it has very limited use as it does not work with different ports
than 443,53,80... try with one rule per port spelled,
yep i know many rules needed... _________________ Atheros
TP-Link WR740Nv4 .......DD-WRT 33986 BS (AP,NAT,AD Blocking,Firewall)
TP-Link WR1043NDv2 ------DD-WRT 36154 BS (AP,PPPoE,NAT,AD Blocking,AP Isolation,Firewall)
TP-Link WR1043NDv2 ------DD-WRT 36410 BS (AP,NAT,AD Blocking,Firewall,No Wi-Fi)
TP-Link WR1043NDv2.......... Gargoyle OS 1.10 (AP,NAT,QoS,Quotas)
Netgear R7800 ------------DD-WRT 36500M Kong (AP,NAT,AD-Blocking,AP Isolation, Firewall,DNSCrypt x2)
Netgear R7000 ---------DD-WRT 36410 Kong (AP,NAT,AD-Blocking,AP Isolation, Firewall,DNSCrypt x4)
Netgear ProSAFE-GS105Ev2 ....(LAN Switch)
Actually my major issue now is I'm having DNS issues on all my wired devices.
I have port 1 on the R7000 going to a netgear 16 port unmanaged switch, everything is plugged into the switch so ports 2,3,4 are unused on the R7000.
As soon as I check the tagged box and then tag port 1 to vlan1 and vlan3 I start having DNS issues.
All wired/wireless devices are getting the proper vlan1 subnet as is all wireless devices on vlan3, when on wifi both vlan1 and vlan3 devices have no issues with DNS. It's only wired devices that have DNS issues.
What makes this weirder my APs are plugged into the 16 port switch so wireless should also have DNS issues but they do not.
well I bought a managed switch which i'd rather return if I can get away without it. As I'm struggling to understand how to set it up correctly with DDWRT. Most tutorials use the same brand router, switch and AP but with DDWRT it a bit challenging without proper documentation.
Anyways how am I suppose to tag vlan3 but not tag vlan1 on port 1 or any other port for that matter?
A bit more in dept explanation of my setup, note I do not have any managed switches on the network.
Bold is the items in the basement
Modem > R7000 > switch > Ground floor > Switch > AP and other devices
Modem > R7000 > switch > 2nd floor > Room 1 > AP
Modem > R7000 > switch > 2nd floor > Room 2 > Switch > AP and other devices.
using ports 2,3,4 will not help in this case (unless I'm missing the obvious?) as I want all my devices on the main lan, but want the APs to use Vlan1 for my main wifi and VLAN3 as my guest wifi. The APs work without issues on both VLANs its all other wired devices that start to have DNS issue yet get the proper subnet for VLAN1, I'm able to ping and do other things but all report DNS errors for whatever reason.
Now I'm even more confused after adding the managed switch. Prior I was able to get the proper subnet on all devices including the guest wifi but now even that is not working, everything is routed to vlan1.
Most of my devices are still on port 1 on the R7000 and using the 16 dumb switch.
R7000 port 2 is set too tagged and I checked marked vlan1 and vlan3, port 2 is plugged into port 1 on the managed switch.
Now on the managed switch, ports 2,3,4 are my APs. Vlan1 is untagged (default) for all ports, on vlan3 I set port 1 as untagged and ports 2,3,4 as tagged. Does port 1 need to be set as tagged as well?
The webui to assign vlans to ports might still be inoperable. I haven't checked it in years. ;o
The UI variables can be seen with 'nvram show | grep port.*vlans', but those don't work apparently. If you change an option in the UI, it's not reflected in the actual config, and must be done manually.
Those values affect the check box in the UI, but nothing else. It's just the vlan.*ports values which are effective. hehe
Essentially, you can't assign ports to vlans in the UI, and you can't tag them (or maybe you can tag them, but not assign them to vlans, can't recall). In any case, you can tag them via telnet as Mr. Berg illustrated.