... I'm about to follow the instructions and am pretty sure I understand the steps. My question on Step 3 is… it reads that one manually runs this line yes? Has anyone automated this last step? I assume (bad word) that one can add this to a shell startup script? Or??
Just wanted to triple check with anyone so I don’t go digging another rabbit hole.
If I can resurrect this thread for a moment… about to follow the instructions and am pretty sure I understand the steps. My question on Step 3 is… it reads that one manually runs this line yes? Has anyone automated this last step? I assume (bad word) that one can add this to a shell startup script? Or??
Just wanted to triple check with anyone so I don’t go digging another rabbit hole.
nvram set pppoe_wan_ifname=eth0.201
(and to make it permanent issue)
nvram commit
or just add nvram set pppoe_wan_ifname=eth0.201 to start up script... i guess...
make sure you use the correct WAN interface have a look at PYB script its easy and working solution... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
If I can resurrect this thread for a moment… about to follow the instructions and am pretty sure I understand the steps. My question on Step 3 is… it reads that one manually runs this line yes? Has anyone automated this last step? I assume (bad word) that one can add this to a shell startup script? Or??
Just wanted to triple check with anyone so I don’t go digging another rabbit hole.
nvram set pppoe_wan_ifname=eth0.201
(and to make it permanent issue)
nvram commit
or just add nvram set pppoe_wan_ifname=eth0.201 to start up script... i guess...
make sure you use the correct WAN interface have a look at PYB script its easy and working solution...
Got it. Understand. Except for one more question... what does PBY mean? I don't do this all the time... tx.
Joined: 18 Mar 2014 Posts: 12885 Location: Netherlands
Posted: Wed Sep 09, 2020 17:15 Post subject:
Not really it is about 8 posts above:
Quote:
There is an easy way:
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 vlan 2 set vid 201
swconfig dev switch0 vlan 2 set ports "0t 5"
swconfig dev switch0 set apply
Put it in the startup script. Keep WAN on default VLAN2
At least I think that is what they are pointing to
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 vlan 2 set vid 201
swconfig dev switch0 vlan 2 set ports "0t 5"
swconfig dev switch0 set apply
Put it in the startup script. Keep WAN on default VLAN2
At least I think that is what they are pointing to
But I am no VLAN expert
Ah, THAT is what is being referred to. It is in the thread. Jeez... I may be slow but I eventually will get it. I can leave my current set up the way it is as I am only suffering about 15% decrease in speed overall, on a 100mb service. But it irks me still to have an unnecessary piece of equipment in the mix and it simply bugs me. Probably end up spending way more time than it is worth fussing with it, but some of us are wired that way...
Joined: 13 Aug 2013 Posts: 6867 Location: Romerike, Norway
Posted: Wed Sep 09, 2020 17:26 Post subject:
Here is the corrected script. It's the WAN port 5 that shall be tagged, not the port going to the processor
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 vlan 2 set vid 201
swconfig dev switch0 vlan 2 set ports "0 5t"
swconfig dev switch0 set apply
Here is the corrected script. It's the WAN port 5 that shall be tagged, not the port going to the processor
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 vlan 2 set vid 201
swconfig dev switch0 vlan 2 set ports "0 5t"
swconfig dev switch0 set apply
Thank you. From the guru it appears. But now it raises a question. This is tagging port 5, so that port is the one that connects to the modem?
Again, I don't do this every day, but appreciate the education you and others present.
Here is the corrected script. It's the WAN port 5 that shall be tagged, not the port going to the processor
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 vlan 2 set vid 201
swconfig dev switch0 vlan 2 set ports "0 5t"
swconfig dev switch0 set apply
And not that this matters, but the reason I keep pressing on this is the device is a Linksys 3200ACM which has a bit more power to reach a bit further to some security cameras that the crummy Centurylink router (Zyxel 3000z) cannot. So there is a practical reason for getting this to work, but the main one is... because. Just because one can. As said, this paragraph does not matter other than what drives this. Thank you everyone who has responded.
Joined: 13 Aug 2013 Posts: 6867 Location: Romerike, Norway
Posted: Wed Sep 09, 2020 18:45 Post subject:
drhiii wrote:
And not that this matters, but the reason I keep pressing on this is the device is a Linksys 3200ACM which has a bit more power to reach a bit further to some security cameras that the crummy Centurylink router (Zyxel 3000z) cannot. So there is a practical reason for getting this to work, but the main one is... because. Just because one can. As said, this paragraph does not matter other than what drives this. Thank you everyone who has responded.
Wrong forum. That is a Marvel device. Nothing in this topic apply to you. You must post in the Marvel forum.
