[SOLVED] Setup a tagged VLAN100 via the GUI or swconfig?

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Goto page 1, 2  Next
Author Message
FTP
DD-WRT User


Joined: 01 Jul 2012
Posts: 97

PostPosted: Thu Apr 28, 2022 17:07    Post subject: [SOLVED] Setup a tagged VLAN100 via the GUI or swconfig? Reply with quote
Hi,

I need a tagged VLAN 100 in between the 2 boxes of my ISP (in between the modem and the A/V box, through the DD-WRT router, an Asus RT-AC66U, hardware A2).

I managed to set it up in 2018 mainly thanks to quarkysg...
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=86919&postdays=0&postorder=asc&start=150

A simple command was doing the job and it worked fine for the last 4 years...
Code:
echo "0t 4t" > /proc/switch/eth0/vlan/100/ports

For information, the VLAN is created in between the hardware LAN port #4 (internal port #0 - because of the reverse numbering) and the WAN (internal port #4).

When I upgraded DD-WRT in Oct. 2020, everything was still working fine.
But I upgraded again DD-WRT today, the VLAN stopped working Sad

After some investigation, I saw that if I manually run the command I get this answer:
Quote:
sh: eval: line 0: can't create /proc/switch/eth0/vlan/100/ports: nonexistent directory

Obviously, the 4096 directories introduced in version 35244 have been removed...
https://wiki.dd-wrt.com/wiki/index.php/Switched_Ports#Broadcom_VLAN_limit

I also saw that the GUI of the Switch Config/VLAN page has been updated. For example, we can now create a VLAN 100 line.

But I found out that starting from version 46604 of May 2021, we're now supposed to use "swconfig" for everything not doable via the GUI...
https://wiki.dd-wrt.com/wiki/index.php/Switched_Ports

I'm not familiar with swconfig, so I first tried to fix my issue using the GUI.
The default configuration is the following:


Then I tried those 2 settings where I added a VLAN 100 line and played with the Tagged settings...



But both are not working. And for the 1st one where WAN is tagged, Internet is not accessible on the LAN and WiFI.

So any idea how to now setup my tagged VLAN100 via the GUI, or swconfig?

Thanks for your help! Smile


Last edited by FTP on Fri Apr 29, 2022 14:51; edited 4 times in total
Sponsor
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 12835
Location: Netherlands

PostPosted: Thu Apr 28, 2022 17:16    Post subject: Reply with quote
Try this:
First tag the wan port, safe and apply.

After the tagging you can check both vlan2 and vlan100

_________________
Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
FTP
DD-WRT User


Joined: 01 Jul 2012
Posts: 97

PostPosted: Thu Apr 28, 2022 17:23    Post subject: Reply with quote
egc wrote:
After the tagging you can check both vlan2 and vlan100

For the WAN column?

So WAN column:
- vlan2
- vlan100
- tagged

Port 4 column:
- vlan100
- tagged

Correct?
FTP
DD-WRT User


Joined: 01 Jul 2012
Posts: 97

PostPosted: Thu Apr 28, 2022 17:39    Post subject: Reply with quote
I tried what I understood from your answer...


It indeed created the VLAN100 and I could get the IPTV on the A/V box, but I lost Internet on the LAN and WiFI Confused

So we're getting close but it's not the right setting Smile
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 12835
Location: Netherlands

PostPosted: Fri Apr 29, 2022 8:15    Post subject: Reply with quote
I hope some of our VLAN experts will chime in (I am not)

But the problem could be that VLAN2 is also tagged and your ISP router cannot deal with that (which makes sense in this case)

So this must to be done manually with swconfig.

I will come back to you how to do that, nut I hope someone will chime in in the mean time

_________________
Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
FTP
DD-WRT User


Joined: 01 Jul 2012
Posts: 97

PostPosted: Fri Apr 29, 2022 8:38    Post subject: Reply with quote
egc wrote:
But the problem could be that VLAN2 is also tagged and your ISP router cannot deal with that (which makes sense in this case)

So this must to be done manually with swconfig.

Yep, that's unfortunately also what I think.
The GUI "Tagged" or not setting is not by VLAN. It looks like for all VLANs or none.

So I still hope we can do it via the GUI, but I'm afraid I may have to go via swconfig (which is not necessarily heavy to setup, but it's always easier when everything can be done via the GUI).

Thanks anyway egc. I appreciate your help as always! Smile

I also hope someone else will be able to help. The family IPTV is not working since the upgrade and I don't want to go back to the 44467. I already fixed all the issues related to the upgrade of OpenVPN, re-setup server and clients, so I don't want to spend time breaking everything.
FTP
DD-WRT User


Joined: 01 Jul 2012
Posts: 97

PostPosted: Fri Apr 29, 2022 9:22    Post subject: Reply with quote
Maybe something like that with swconfig? Rolling Eyes
I tried 2 configs based on answers in other threads but with no luck so far...
Code:
swconfig dev eth0 set enable_vlan 1
swconfig dev eth0 vlan 100 set ports "0t 4t"
swconfig dev eth0 set apply
vconfig add eth0 100
ifconfig vlan100 up


Code:
swconfig dev eth0 set enable_vlan 1
swconfig dev eth0 vlan 100 set ports "0t 4t"
swconfig dev eth0 set apply
vconfig add eth0 100
ifconfig eth0.100 192.168.0.1 netmask 255.255.255.0


Last edited by FTP on Fri Apr 29, 2022 9:38; edited 1 time in total
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 12835
Location: Netherlands

PostPosted: Fri Apr 29, 2022 9:31    Post subject: Reply with quote
FTP wrote:
Maybe something like that with swconfig? Rolling Eyes
Code:
swconfig dev eth0 set enable_vlan 1
swconfig dev eth0 vlan 100 set ports "0t 4t"
swconfig dev eth0 set apply
vconfig add eth0 100
ifconfig vlan100 up


For me it is also a bit of a guessing game as I knew how to do it with nvram (the old way) but not yet with swconfig.

As you already have made VLAN 100 in the GUI i would guess you only need to tag the WAN port and not make the interface etc.
swconfig list
will show how the switch is called usually switch0 but for you it might be different

You start with enabling swconfig:
swconfig dev switch0 set enable_vlan 1

Then tag port 0 (port 4 is already tagged but perhaps you should do it too?)
swconfig dev switch0 vlan 100 set ports "0t 5t"

Apply
swconfig dev switch0 set apply

If it works you have to place it in startup


Edit: usually you have to include the CPU port so if port 4 was not already tagged you do:
swconfig dev switch0 vlan 100 set ports "0t 4t 5t"

Edit 2: it overrides so indeed:
swconfig dev switch0 vlan 100 set ports "0t 4t 5t"

_________________
Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
FTP
DD-WRT User


Joined: 01 Jul 2012
Posts: 97

PostPosted: Fri Apr 29, 2022 9:51    Post subject: Reply with quote
egc wrote:
As you already have made VLAN 100 in the GUI i would guess you only need to tag the WAN port and not make the interface etc.

Well, I removed it to do the settings 100% via swconfig.
But why not mixing, I'm not against the idea.

egc wrote:
Then tag port 0 (port 4 is already tagged but perhaps you should do it too?)
swconfig dev switch0 vlan 100 set ports "0t 5t"

Like I said, it has worked 100% fine for 4 years with this command line:
Code:
echo "0t 4t" > /proc/switch/eth0/vlan/100/ports

And according to the explanations of quarkysg, for the Asus RT-AC66U A2, 0 to 3 are the LAN port in reverse numbering (0=port 4, 1=port 3, 2=port 2, 3=port 1) and 4 is the WAN port.
So "0t 4t" = LAN port 4 tagged with WAN port tagged...
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=86919&postdays=0&postorder=asc&start=150

So I'm not sure why you want to add port 5?

egc wrote:
swconfig list
will show how the switch is called usually switch0 but for you it might be different

Yep, switch0 ...
Quote:
Found: switch0 - bcm53125


But the following commands...
Code:
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 vlan 100 set ports "0t 4t"
swconfig dev switch0 set apply

...gave the message...
Quote:
swconfig list
swconfig dev [port |vlan ] (help|set |get |load |show)


I've also added again the VLAN100 line in the GUI + try to run the following commands, but with no success...
Code:
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 vlan 100 set ports "0t 4t"
swconfig dev switch0 set apply


Code:
swconfig dev eth0 set enable_vlan 1
swconfig dev eth0 vlan 100 set ports "0t 4t"
swconfig dev eth0 set apply

I also tried removing the VLAN100 line in the GUI and run the following commands woth "switch0" instead of "eth0" with still no luck...
Code:
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 vlan 100 set ports "0t 4t"
swconfig dev switch0 set apply
vconfig add switch0 100
ifconfig vlan100 up
FTP
DD-WRT User


Joined: 01 Jul 2012
Posts: 97

PostPosted: Fri Apr 29, 2022 10:55    Post subject: Reply with quote
FYI, the "swconfig dev switch0 show" command before adding any line in the GUI or executing any command gives this:
Code:
Global attributes:
   enable_vlan: 1
   ports: 0x011f
   reset_mib: ???
   enable_jumbo: 0
   allow_vid_4095: 0
Port 0:
   mib: TxOctets            : 299361
TxDropPkts          : 0
TxBroadcastPkts     : 3
TxMulticastPkts     : 0
TxUnicastPkts       : 1663
TxCollisions        : 0
TxSingleCollision   : 0
TxMultipleCollision : 0
TxDeferredTransmit  : 0
TxLateCollision     : 0
TxExcessiveCollision: 0
TxPausePkts         : 0
RxOctets            : 1521803
RxUndersizePkts     : 0
RxPausePkts         : 0
Pkts64Octets        : 494
Pkts65to127Octets   : 385
Pkts128to255Octets  : 166
Pkts256to511Octets  : 90
Pkts512to1023Octets : 78
Pkts1024to1522Octets: 895
RxOversizePkts      : 0
RxJabbers           : 0
RxAlignmentErrors   : 0
RxFCSErrors         : 0
RxGoodOctets        : 1521803
RxDropPkts          : 0
RxUnicastPkts       : 2075
RxMulticastPkts     : 0
RxBroadcastPkts     : 33
RxSAChanges         : 1
RxFragments         : 0
RxJumboPkts         : 0
RxSymbolErrors      : 0
RxDiscarded         : 33

   disable: ???
   pvid: 2
   link: port:0 link:up speed:1000baseT full-duplex auto
Port 1:
   mib: TxOctets            : 0
TxDropPkts          : 0
TxBroadcastPkts     : 0
TxMulticastPkts     : 0
TxUnicastPkts       : 0
TxCollisions        : 0
TxSingleCollision   : 0
TxMultipleCollision : 0
TxDeferredTransmit  : 0
TxLateCollision     : 0
TxExcessiveCollision: 0
TxPausePkts         : 0
RxOctets            : 0
RxUndersizePkts     : 0
RxPausePkts         : 0
Pkts64Octets        : 0
Pkts65to127Octets   : 0
Pkts128to255Octets  : 0
Pkts256to511Octets  : 0
Pkts512to1023Octets : 0
Pkts1024to1522Octets: 0
RxOversizePkts      : 0
RxJabbers           : 0
RxAlignmentErrors   : 0
RxFCSErrors         : 0
RxGoodOctets        : 0
RxDropPkts          : 0
RxUnicastPkts       : 0
RxMulticastPkts     : 0
RxBroadcastPkts     : 0
RxSAChanges         : 0
RxFragments         : 0
RxJumboPkts         : 0
RxSymbolErrors      : 0
RxDiscarded         : 0

   disable: ???
   pvid: 1
   link: port:1 link:down
Port 2:
   mib: TxOctets            : 1637508
TxDropPkts          : 0
TxBroadcastPkts     : 50
TxMulticastPkts     : 51
TxUnicastPkts       : 2285
TxCollisions        : 0
TxSingleCollision   : 0
TxMultipleCollision : 0
TxDeferredTransmit  : 0
TxLateCollision     : 0
TxExcessiveCollision: 0
TxPausePkts         : 0
RxOctets            : 415236
RxUndersizePkts     : 0
RxPausePkts         : 0
Pkts64Octets        : 890
Pkts65to127Octets   : 1440
Pkts128to255Octets  : 76
Pkts256to511Octets  : 172
Pkts512to1023Octets : 85
Pkts1024to1522Octets: 69
RxOversizePkts      : 0
RxJabbers           : 0
RxAlignmentErrors   : 0
RxFCSErrors         : 0
RxGoodOctets        : 415236
RxDropPkts          : 0
RxUnicastPkts       : 1881
RxMulticastPkts     : 634
RxBroadcastPkts     : 217
RxSAChanges         : 124
RxFragments         : 0
RxJumboPkts         : 0
RxSymbolErrors      : 0
RxDiscarded         : 0

   disable: ???
   pvid: 1
   link: port:2 link:up speed:1000baseT full-duplex auto
Port 3:
   mib: TxOctets            : 0
TxDropPkts          : 0
TxBroadcastPkts     : 0
TxMulticastPkts     : 0
TxUnicastPkts       : 0
TxCollisions        : 0
TxSingleCollision   : 0
TxMultipleCollision : 0
TxDeferredTransmit  : 0
TxLateCollision     : 0
TxExcessiveCollision: 0
TxPausePkts         : 0
RxOctets            : 0
RxUndersizePkts     : 0
RxPausePkts         : 0
Pkts64Octets        : 0
Pkts65to127Octets   : 0
Pkts128to255Octets  : 0
Pkts256to511Octets  : 0
Pkts512to1023Octets : 0
Pkts1024to1522Octets: 0
RxOversizePkts      : 0
RxJabbers           : 0
RxAlignmentErrors   : 0
RxFCSErrors         : 0
RxGoodOctets        : 0
RxDropPkts          : 0
RxUnicastPkts       : 0
RxMulticastPkts     : 0
RxBroadcastPkts     : 0
RxSAChanges         : 0
RxFragments         : 0
RxJumboPkts         : 0
RxSymbolErrors      : 0
RxDiscarded         : 0

   disable: ???
   pvid: 1
   link: port:3 link:down
Port 4:
   mib: TxOctets            : 160534
TxDropPkts          : 0
TxBroadcastPkts     : 254
TxMulticastPkts     : 641
TxUnicastPkts       : 116
TxCollisions        : 0
TxSingleCollision   : 0
TxMultipleCollision : 0
TxDeferredTransmit  : 0
TxLateCollision     : 0
TxExcessiveCollision: 0
TxPausePkts         : 0
RxOctets            : 60408
RxUndersizePkts     : 0
RxPausePkts         : 0
Pkts64Octets        : 20
Pkts65to127Octets   : 118
Pkts128to255Octets  : 18
Pkts256to511Octets  : 57
Pkts512to1023Octets : 18
Pkts1024to1522Octets: 12
RxOversizePkts      : 0
RxJabbers           : 0
RxAlignmentErrors   : 0
RxFCSErrors         : 0
RxGoodOctets        : 60408
RxDropPkts          : 0
RxUnicastPkts       : 162
RxMulticastPkts     : 44
RxBroadcastPkts     : 37
RxSAChanges         : 48
RxFragments         : 0
RxJumboPkts         : 0
RxSymbolErrors      : 0
RxDiscarded         : 24

   disable: ???
   pvid: 1
   link: port:4 link:up speed:1000baseT full-duplex auto
Port 5:
   mib: ???
   disable: ???
   pvid: 0
   link: port:5 link:down
Port 6:
   mib: ???
   disable: ???
   pvid: 0
   link: port:6 link:down
Port 7:
   mib: ???
   disable: ???
   pvid: 0
   link: port:7 link:down
Port 8:
   mib: TxOctets            : 1990873
TxDropPkts          : 0
TxBroadcastPkts     : 230
TxMulticastPkts     : 678
TxUnicastPkts       : 4011
TxCollisions        : 0
TxSingleCollision   : 0
TxMultipleCollision : 0
TxDeferredTransmit  : 0
TxLateCollision     : 0
TxExcessiveCollision: 0
TxPausePkts         : 0
RxOctets            : 1962540
RxUndersizePkts     : 0
RxPausePkts         : 0
Pkts64Octets        : 1056
Pkts65to127Octets   : 1330
Pkts128to255Octets  : 233
Pkts256to511Octets  : 208
Pkts512to1023Octets : 167
Pkts1024to1522Octets: 1030
RxOversizePkts      : 0
RxJabbers           : 0
RxAlignmentErrors   : 0
RxFCSErrors         : 0
RxGoodOctets        : 1962540
RxDropPkts          : 0
RxUnicastPkts       : 3956
RxMulticastPkts     : 7
RxBroadcastPkts     : 61
RxSAChanges         : 75
RxFragments         : 0
RxJumboPkts         : 0
RxSymbolErrors      : 0
RxDiscarded         : 21

   disable: ???
   pvid: 0
   link: port:8 link:up speed:1000baseT full-duplex
VLAN 1:
   ports: 1 2 3 4 8t
VLAN 2:
   ports: 0 8t

There's nothing on port 5, 6, 7 but the 2 default VLANs are both linked to port 8 tagged.
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 12835
Location: Netherlands

PostPosted: Fri Apr 29, 2022 11:04    Post subject: Reply with quote
OK port 8 is your CPU port so if you already have added vlan100 in the GUI then this might work (port 0 is the WAN port):

swconfig dev switch0 vlan 100 set ports "0t 4t 8t"

If you did not already removed port 4 from VLAN 1 then start with:
swconfig dev switch0 vlan 1 set ports "1 2 3 8t"

_________________
Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
FTP
DD-WRT User


Joined: 01 Jul 2012
Posts: 97

PostPosted: Fri Apr 29, 2022 11:08    Post subject: Reply with quote
FTP wrote:
egc wrote:
But the problem could be that VLAN2 is also tagged and your ISP router cannot deal with that (which makes sense in this case)

So this must to be done manually with swconfig.

Yep, that's unfortunately also what I think.
The GUI "Tagged" or not setting is not by VLAN. It looks like for all VLANs or none.

Confirmed!

If I set this configuration where port 0 and 4 are tagged...


...with "swconfig dev switch0 show" I get...
Code:
VLAN 1:
   ports: 1 2 3 4t 8t
VLAN 2:
   ports: 0t 8t
VLAN 100:
   ports: 0t 4t 8t

So port 0 and 4 are tagged for ALL VLANs and that's where I loose Internet access on the LAN and WiFi.

So mixing GUI and swconfig settings "may" not be easy as there's no way I can setup a VLAN100 in the GUI without tagging some ports of VLAN1 or VLAN2, or removing them from VLAN1 or VLAN2.

Indeed, if I add a VLAN100 without selecting any port, the line is saved but the VLAN100 is not created (according to "swconfig dev switch0 show").

And if I want to select at least one port for the VLAN100, I need to tick "tagged" and either it will tag the ports on VLAN1 or VLAN2, or... I will have to remove some ports from VLAN1 or VLAN2.

So it may be best to do everything with swconfig, leave VLAN1 & VLAN2 as is and just add the appropriate VLAN100 with swconfig Confused
FTP
DD-WRT User


Joined: 01 Jul 2012
Posts: 97

PostPosted: Fri Apr 29, 2022 12:42    Post subject: Reply with quote
egc wrote:
OK port 8 is your CPU port...

Yep, that's what I understand too.
Also, obviously swconfig works differently than the previous command using the directories.

With "echo "0t 4t" > /proc/switch/eth0/vlan/100/ports", 4 was the WAN port, 0 to 3 the LAN port in reverse numbering, it has been tested and confirmed by me and several persons, even on the forums. The association with the CPU (port 8 ) was also maybe done silently, like with the GUI, I don't know.

But with swconfig, obviously port 0 is the WAN (like on the GUI), 1 to 4 the LAN ports in the right order and 8 the CPU.
And we "may" have to associate ourself in the command the port 8 tagged when we create a VLAN. TBC.

Now, even knowing all that, I still have a problem.
I can't create the VLAN100 via the GUI for the reasons seen above and so far, I've not been able yet to create a single VLAN via the swconfig commands.

When I just use the first 3 lines...
Code:
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 vlan 100 set ports "0t 4t 8t"
swconfig dev switch0 set apply

...I get this message and nothing is created:
Quote:
swconfig list
swconfig dev [port |vlan ] (help|set |get |load |show)


And when I use the 5 lines (with vconfig and ifconfig), I don't have any message, but still, no VLAN is created:
Code:
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 vlan 100 set ports "0t 4t 8t"
swconfig dev switch0 set apply
vconfig add eth0 100
ifconfig vlan100 up


And I tried several variant according to what I found in other threads like:
Code:
vconfig add switch0 100
ifconfig vlan100 up

Code:
vconfig add eth0 100
ifconfig vlan100 up

Code:
vconfig add eth0 100
ifconfig eth0.100 192.168.0.1 netmask 255.255.255.0

Even though for this last case, I'm not sure witch IP address should I use Rolling Eyes

Some sources:
https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1226072#1226072
https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1142301#1142301
FTP
DD-WRT User


Joined: 01 Jul 2012
Posts: 97

PostPosted: Fri Apr 29, 2022 13:10    Post subject: Reply with quote
BTW, the "swconfig dev switch0 help":
Code:
switch0: bcm53125(BCM53125), ports: 9 (cpu @ 8), vlans: 4096
     --switch
   Attribute 1 (int): enable_vlan (Enable VLAN mode)
   Attribute 2 (string): ports (Available Ports (as bitmask))
   Attribute 3 (int): reset_mib (Reset MIB counters)
   Attribute 4 (int): enable_jumbo (Enable Jumbo Frames)
   Attribute 5 (int): allow_vid_4095 (Allow VID 4095)
   Attribute 6 (none): apply (Activate changes in the hardware)
   Attribute 7 (none): reset (Reset the switch)
     --vlan
   Attribute 1 (ports): ports (VLAN port mapping)
     --port
   Attribute 1 (string): mib (Get port's MIB counters)
   Attribute 2 (int): disable (Disable Port)
   Attribute 3 (int): pvid (Primary VLAN ID)
   Attribute 4 (unknown): link (Get/Set port link information)

It confirms CPU is port 8.
FTP
DD-WRT User


Joined: 01 Jul 2012
Posts: 97

PostPosted: Fri Apr 29, 2022 13:41    Post subject: Reply with quote
Ok, maybe fixed! Smile

I noticed those comments in the past...
HediSIX wrote:
I have tried this weekend but it looks like the commands are not recognised Shocked

I only get this message:
Code:
swconfig list
swconfig dev  [port |vlan ] (help|set  |get |load |show)

It's also what I get when I manually ran the 1st 3 lines via the GUI.

HediSIX wrote:
Hey I made it work !!
I used SSH and did not get the errors anymore. It looks like the Command page from the GUI does not work the same way…

So I tried via SSH.
The first 3 lines went smoothly, without any error or message, but the 4th one triggered this error:
Quote:
vconfig: ioctl error for add: File exists


But still, I had a look if the VLAN100 was already created, and... bingo, it was already there and working fine!
Code:
VLAN 1:
   ports: 1 2 3 4 8t
VLAN 2:
   ports: 0 8t
VLAN 100:
   ports: 0t 4t 8t

IPTV working, LAN and WiFi also Smile

So I thought, ok, I'll then have to run those commands via a script and not the NVRAM startup commands Rolling Eyes

BUT... I got tricked in fact.
It also worked via the NVRAM startup commands! Shocked

1/ in fact the message I got was not blocking the VLAN creation process and 2/ I also got tricked as it looks like the VLAN creation was not immediate. There was a little delay in between the command and the availability on the network, so I thought it was not working while after maybe 20/30s it was staring to work fine.

I now have rebooted the router 3 or 4 times and it's always the same behaviour, the VLAN100 is always created and available maybe 20/30s after the availability of Internet on the LAN. But at the end it works fine.


Arrow Now the last question I have is: are the last 2 lines really useless, as Per Yngve Berg always advised to add them...
Code:
vconfig add eth0 100
ifconfig eth0.100 192.168.0.1 netmask 255.255.255.0
Goto page 1, 2  Next Display posts from previous:    Page 1 of 2
Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum