Beginning Mult-WAN setup

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


Joined: 19 Apr 2021
Posts: 24

PostPosted: Sun May 23, 2021 0:34    Post subject: Beginning Mult-WAN setup Reply with quote
Hello,

Hardware and firmware:
Asus RT-AC88U
DD-WRT v3.0-r44715 (11/03/20)

I'm learning how to configure routers. So please forgive me if my questions are sometimes basic.

I trying to setup multi-WAN on my Asus RT-AC88U router. This router initially is configured with 1 WAN and 8 LAN ports.

By example, I'm learning to do this multi-WAN setup from the following links:
https://wiki.dd-wrt.com/wiki/index.php/Category:Dual_WAN
https://wiki.dd-wrt.com/wiki/index.php/DUAL_WAN_E2000_/_WRT320N
https://wiki.dd-wrt.com/wiki/index.php/Dual_WAN_with_failover
https://wiki.dd-wrt.com/wiki/index.php/Dual_WAN_with_one_as_standby_backup
https://wiki.dd-wrt.com/wiki/index.php/Dual%2C_Triple_%28and_probably_quad%29_WAN_with_multiple_active_WAN_links_and_source_routing
https://wiki.dd-wrt.com/wiki/index.php/Dual-WAN_for_simple_round-robin_load_equalization

Before making any other changes, I wanted to understand the starting configuration of my router.
Unfortunately, when I examine the nvram variables, I get inconsistent data:
Code:
vlan2ports=4 7u            # WAN = port 4 on vlan2 (WAN PORT NUMBER DOES NOT MATCH *BELOW*)
port0vlans=2               # WAN = port 0 on vlan2 (WAN PORT NUMBER DOES NOT MATCH *ABOVE*)
vlan1ports=0 1 2 3 5 7*    # 5 logical ports: 0, 1, 2, 3, 5 (SHOULD BE 8 LOGICAL PORTS, NOT 5 LOGICAL PORTS)
port5vlans=1 2 16          #vlan16 does not appear anywhere else

1) There should be a single WAN port, yet I'm shown two WAN ports: 4 and 0.
2) There should be 8 LAN ports, but I'm only shown 5.
3) What is vlan16? It doesn't appear under "ifconfig".

Below are the full outputs of these and other commands (along with my notes preceded by ">>"):
Code:
root@DD-WRT:~# nvram show | grep -i vlan.*ports
size: 39004 bytes (92068 left)
vlan2ports=4 7u
vlan1ports=0 1 2 3 5 7*

>> Physical port 4 = WAN Logical port (vlan2)
>> Physical port 0 = LAN Logical port 1 (vlan1)
>> Physical port 1 = LAN Logical port 2 (vlan1)
>> Physical port 2 = LAN Logical port 3 (vlan1)
>> Physical port 3 = LAN Logical port 4 (vlan1)
>> Physical port 5 = LAN Logical port 5 (vlan1)
>> Port 7 = logical bridge on every VLAN (vlan1 & vlan2)

Code:
root@DD-WRT:~# nvram show | grep -i port.*vlans
size: 39004 bytes (92068 left)
port5vlans=1 2 16
port3vlans=1
port1vlans=1
port4vlans=1
port2vlans=1
port0vlans=2

>> Port(s) 3, 1, 4, and 2 belong to vlan1
>> Port(s) 0(WAN) belong to vlan2
>> Port(s) 5 bridges vlan1 and vlan2 (what is vlan16?)

Code:
root@DD-WRT:~# nvram show | grep -i vlan.*hwname
size: 39004 bytes (92068 left)
vlan2hwname=et1
vlan1hwname=et1

>> vlan1 and vlan2 are part of interface "eth1"

Code:
root@DD-WRT:~# ifconfig
br0       Link encap:Ethernet  HWaddr <MAC>
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7801 errors:0 dropped:35 overruns:0 frame:0
          TX packets:10021 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:705094 (688.5 KiB)  TX bytes:10366785 (9.8 MiB)

eth0      Link encap:Ethernet  HWaddr <MAC>
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:16008 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15732 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:9867928 (9.4 MiB)  TX bytes:11020848 (10.5 MiB)
          Interrupt:180 Base address:0x5000

eth1      Link encap:Ethernet  HWaddr <MAC>
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:10 overruns:0 frame:0
          TX packets:73 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:12590 (12.2 KiB)

eth2      Link encap:Ethernet  HWaddr <MAC>
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:9 overruns:0 frame:0
          TX packets:73 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:12590 (12.2 KiB)

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING MULTICAST  MTU:65536  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:416 (416.0 B)  TX bytes:416 (416.0 B)

vlan1     Link encap:Ethernet  HWaddr <MAC>
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7774 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10021 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:703702 (687.2 KiB)  TX bytes:10366785 (9.8 MiB)

vlan2     Link encap:Ethernet  HWaddr <MAC>
          inet addr:<address> Bcast:<address> Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8229 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5711 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8811840 (8.4 MiB)  TX bytes:591135 (577.2 KiB)

>> vlan2 connects to WAN (inet addr)
>> Where is vlan16?

Why is my data inconsistent?
What am I doing wrong?
Any pointers appreciated.

Thank you.
Sponsor
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14102
Location: Texas, USA

PostPosted: Sun May 23, 2021 0:57    Post subject: Reply with quote
Port 7 is not your cpu port;
it's going to be either 5 or 8.
What were the default outputs of
Code:
nvram show | grep vlan.*ports | sort
nvram show | grep port.*vlans | sort
nvram show | grep vlan.*hwname | sort

before you even started?

NOTE: builds past 46446 do not use this method of vlan configuration anymore. The router database is not necessarily your friend, either.

https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/
https://dd-wrt.com/support/other-downloads/?path=betas/
ftp://ftp.dd-wrt.com/betas/

_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Per Yngve Berg
DD-WRT Guru


Joined: 13 Aug 2013
Posts: 6855
Location: Romerike, Norway

PostPosted: Sun May 23, 2021 9:55    Post subject: Reply with quote
This router have two switches BCM4709C0 and RTL8365MB

BCM4709C0:

Eight ports with full-line rate
Five 10/100/1000 PHY ports
RGMII/MII-lite interface (Here is the RTL switch connected)


RTL8365MB:

Single-chip 4+1-port 10/100/1000M non-blocking switch architecture
Embedded 4-port 10/100/1000Base-T PHY
Each port supports full duplex 10/100/1000M connectivity (half duplex only supported in 10/100M mode)
Extra Interface (Extension GMAC1) supports
Media Independent Interface (MII)
Reduced 10/100/1000M Media Independent Interface (RGMII)
Full-duplex and half-duplex operation with IEEE 802.3x flow control and backpressure
Supports 9216-byte jumbo packet length forwarding at wire speed


1) Update dd-wrt to a builds past 46446
2) Use swconfig list to identify the switches
3) Use swconfig to show the configuration of the switches
Probably swconfig dev switch0 show and swconfig dev switch1 show

Have fun.
resolv
DD-WRT Novice


Joined: 19 Apr 2021
Posts: 24

PostPosted: Sun May 23, 2021 17:14    Post subject: Reply with quote
Hello kernel-panic69,
Thank you for your response.

Quote:
What were the default outputs


My post contained the default outputs.
The configuration sequence I used for my post was:
1) "Restore Factory Defaults";
2) changed router name and password;
3) enabled SSHd to allow ssh login;
4) ssh login to the router;
5) list the outputs shown in my post.
(I wanted to understand my routers initial conditions *BEFORE* making any changes.)

Quote:
builds past 46446 do not use this method of vlan configuration anymore

Do you recommend that I try a later build?
I believe build 46733 is available for this router.
Also, is there documentation on how to configure vlans using firmware after 46446?

Thank you.
resolv
DD-WRT Novice


Joined: 19 Apr 2021
Posts: 24

PostPosted: Sun May 23, 2021 17:20    Post subject: Reply with quote
Hello Per Yngve Berg,
Quote:
1) Update dd-wrt to a builds past 46446
2) Use swconfig list to identify the switches
3) Use swconfig to show the configuration of the switches
Probably swconfig dev switch0 show and swconfig dev switch1 show

Thank you for the information and instructions. I'll do the upgrade that you recommend, and study the results.

Much appreciated.
resolv
DD-WRT Novice


Joined: 19 Apr 2021
Posts: 24

PostPosted: Mon May 24, 2021 7:25    Post subject: Reply with quote
Hello,

New Firmware: DD-WRT v3.0-r46733 std (05/21/21)
Hardware: Asus RT-AC88U

Thank you for the help. I've made some progress,
but I'm still unable to map 4 of the LANs to 4 of the switch ports.

As recommended, I installed a dd-wrt build past 46446:
Firmware: DD-WRT v3.0-r46733 std (05/21/21)

"swconfig list" reported one switch (not two switches):
Code:
Found: switch0 - bcm53011

To test if there was a second switch, I tried "swconfig dev switch1 help":
Code:
Failed to connect to the switch. Use the "list" command to see which switches are available.

So there is only one switch.

"swconfig dev switch0 help" reported 9 ports:
Code:
switch0: bcm53011(BCM53012), ports: 9 (cpu @ 5), 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): pvid (Primary VLAN ID)
        Attribute 3 (unknown): link (Get/Set port link information)

There is 1 switch with 9 ports. So far, so good.

Now the problems begin.

Using "swconfig dev switch0 help", I mapped the 8 wired LAN connections to the "switch0" ports
(plugged an Ethernet cable into each LAN and located changes to up/down states):
LAN-1 = port:3
LAN-2 = port:2
LAN-3 = port:1
LAN-4 = port:0
LAN-5 = <no port up/down change found>
LAN-6 = <no port up/down change found>
LAN-7 = <no port up/down change found>
LAN-8 = <no port up/down change found>
Problem: 4 of the LANs have no "switch0" port mapping.

Using the Web-GUI, I got similar results:
Setup->Switch Config
up/down shown: WAN, Port-1, Port-2, Port-3, Port-4
*NOT* shown: Port-5, Port-6, Port-7, Port-8

How do I determine the map for LAN-5, LAN-6, LAN-7, LAN-8 onto the switch0 ports?

Thank you for the help.
Per Yngve Berg
DD-WRT Guru


Joined: 13 Aug 2013
Posts: 6855
Location: Romerike, Norway

PostPosted: Mon May 24, 2021 8:16    Post subject: Reply with quote
Can you post

swconfig dev switch0 show
resolv
DD-WRT Novice


Joined: 19 Apr 2021
Posts: 24

PostPosted: Mon May 24, 2021 10:10    Post subject: Reply with quote
Hello Per Yngve Berg,

Below is the information you requested.
(LAN-8 is connected to the computer.)

Code:
root@DD-WRT:~# swconfig dev switch0 show
Global attributes:
        enable_vlan: 1
        ports: 0x01bf
        reset_mib: ???
        enable_jumbo: 0
        allow_vid_4095: 0
Port 0:
        mib: TxOctets            : 979477
TxDropPkts          : 0
TxBroadcastPkts     : 2
TxMulticastPkts     : 0
TxUnicastPkts       : 1698
TxCollisions        : 0
TxSingleCollision   : 0
TxMultipleCollision : 0
TxDeferredTransmit  : 0
TxLateCollision     : 0
TxExcessiveCollision: 0
TxPausePkts         : 0
RxOctets            : 198247
RxUndersizePkts     : 0
RxPausePkts         : 0
Pkts64Octets        : 8
Pkts65to127Octets   : 1366
Pkts128to255Octets  : 40
Pkts256to511Octets  : 212
Pkts512to1023Octets : 8
Pkts1024to1522Octets: 1
RxOversizePkts      : 0
RxJabbers           : 0
RxAlignmentErrors   : 0
RxFCSErrors         : 0
RxGoodOctets        : 198247
RxDropPkts          : 0
RxUnicastPkts       : 1631
RxMulticastPkts     : 3
RxBroadcastPkts     : 1
RxSAChanges         : 1
RxFragments         : 0
RxJumboPkts         : 0
RxSymbolErrors      : 0
RxDiscarded         : 0

        pvid: 1
        link: port:0 link:down
Port 1:
        mib: TxOctets            : 621391
TxDropPkts          : 0
TxBroadcastPkts     : 0
TxMulticastPkts     : 0
TxUnicastPkts       : 550
TxCollisions        : 0
TxSingleCollision   : 0
TxMultipleCollision : 0
TxDeferredTransmit  : 0
TxLateCollision     : 0
TxExcessiveCollision: 0
TxPausePkts         : 0
RxOctets            : 46116
RxUndersizePkts     : 0
RxPausePkts         : 0
Pkts64Octets        : 2
Pkts65to127Octets   : 445
Pkts128to255Octets  : 10
Pkts256to511Octets  : 30
Pkts512to1023Octets : 1
Pkts1024to1522Octets: 0
RxOversizePkts      : 0
RxJabbers           : 0
RxAlignmentErrors   : 0
RxFCSErrors         : 0
RxGoodOctets        : 46116
RxDropPkts          : 0
RxUnicastPkts       : 481
RxMulticastPkts     : 5
RxBroadcastPkts     : 2
RxSAChanges         : 1
RxFragments         : 0
RxJumboPkts         : 0
RxSymbolErrors      : 0
RxDiscarded         : 0

        pvid: 1
        link: port:1 link:down
Port 2:
        mib: TxOctets            : 622394
TxDropPkts          : 0
TxBroadcastPkts     : 0
TxMulticastPkts     : 0
TxUnicastPkts       : 555
TxCollisions        : 0
TxSingleCollision   : 0
TxMultipleCollision : 0
TxDeferredTransmit  : 0
TxLateCollision     : 0
TxExcessiveCollision: 0
TxPausePkts         : 0
RxOctets            : 44456
RxUndersizePkts     : 0
RxPausePkts         : 0
Pkts64Octets        : 0
Pkts65to127Octets   : 415
Pkts128to255Octets  : 9
Pkts256to511Octets  : 32
Pkts512to1023Octets : 1
Pkts1024to1522Octets: 0
RxOversizePkts      : 0
RxJabbers           : 0
RxAlignmentErrors   : 0
RxFCSErrors         : 0
RxGoodOctets        : 44456
RxDropPkts          : 0
RxUnicastPkts       : 451
RxMulticastPkts     : 4
RxBroadcastPkts     : 2
RxSAChanges         : 1
RxFragments         : 0
RxJumboPkts         : 0
RxSymbolErrors      : 0
RxDiscarded         : 0

        pvid: 1
        link: port:2 link:down
Port 3:
        mib: TxOctets            : 632558
TxDropPkts          : 0
TxBroadcastPkts     : 0
TxMulticastPkts     : 0
TxUnicastPkts       : 651
TxCollisions        : 0
TxSingleCollision   : 0
TxMultipleCollision : 0
TxDeferredTransmit  : 0
TxLateCollision     : 0
TxExcessiveCollision: 0
TxPausePkts         : 0
RxOctets            : 70303
RxUndersizePkts     : 0
RxPausePkts         : 0
Pkts64Octets        : 22
Pkts65to127Octets   : 572
Pkts128to255Octets  : 13
Pkts256to511Octets  : 63
Pkts512to1023Octets : 1
Pkts1024to1522Octets: 0
RxOversizePkts      : 0
RxJabbers           : 0
RxAlignmentErrors   : 0
RxFCSErrors         : 0
RxGoodOctets        : 70303
RxDropPkts          : 0
RxUnicastPkts       : 642
RxMulticastPkts     : 27
RxBroadcastPkts     : 2
RxSAChanges         : 1
RxFragments         : 0
RxJumboPkts         : 0
RxSymbolErrors      : 0
RxDiscarded         : 0

        pvid: 1
        link: port:3 link:down
Port 4:
        mib: TxOctets            : 924755
TxDropPkts          : 0
TxBroadcastPkts     : 70
TxMulticastPkts     : 0
TxUnicastPkts       : 7361
TxCollisions        : 0
TxSingleCollision   : 0
TxMultipleCollision : 0
TxDeferredTransmit  : 0
TxLateCollision     : 0
TxExcessiveCollision: 0
TxPausePkts         : 0
RxOctets            : 11414781
RxUndersizePkts     : 0
RxPausePkts         : 0
Pkts64Octets        : 876
Pkts65to127Octets   : 1953
Pkts128to255Octets  : 440
Pkts256to511Octets  : 481
Pkts512to1023Octets : 249
Pkts1024to1522Octets: 7169
RxOversizePkts      : 0
RxJabbers           : 0
RxAlignmentErrors   : 0
RxFCSErrors         : 0
RxGoodOctets        : 11414781
RxDropPkts          : 0
RxUnicastPkts       : 10756
RxMulticastPkts     : 405
RxBroadcastPkts     : 7
RxSAChanges         : 11
RxFragments         : 0
RxJumboPkts         : 0
RxSymbolErrors      : 0
RxDiscarded         : 0

        pvid: 2
        link: port:4 link:up speed:1000baseT full-duplex auto
Port 5:
        mib: TxOctets            : 15834012
TxDropPkts          : 0
TxBroadcastPkts     : 99
TxMulticastPkts     : 39
TxUnicastPkts       : 28765
TxCollisions        : 0
TxSingleCollision   : 0
TxMultipleCollision : 0
TxDeferredTransmit  : 0
TxLateCollision     : 0
TxExcessiveCollision: 0
TxPausePkts         : 0
RxOctets            : 3501309
RxUndersizePkts     : 0
RxPausePkts         : 0
Pkts64Octets        : 1527
Pkts65to127Octets   : 19326
Pkts128to255Octets  : 540
Pkts256to511Octets  : 3901
Pkts512to1023Octets : 425
Pkts1024to1522Octets: 77
RxOversizePkts      : 0
RxJabbers           : 0
RxAlignmentErrors   : 0
RxFCSErrors         : 0
RxGoodOctets        : 3501309
RxDropPkts          : 0
RxUnicastPkts       : 25278
RxMulticastPkts     : 502
RxBroadcastPkts     : 16
RxSAChanges         : 1
RxFragments         : 0
RxJumboPkts         : 0
RxSymbolErrors      : 0
RxDiscarded         : 0

        pvid: 1
        link: port:5 link:up speed:1000baseT full-duplex
Port 6:
        mib: ???
        pvid: 0
        link: port:6 link:down
Port 7:
        mib: TxOctets            : 15436036
TxDropPkts          : 0
TxBroadcastPkts     : 30
TxMulticastPkts     : 946
TxUnicastPkts       : 39241
TxCollisions        : 0
TxSingleCollision   : 0
TxMultipleCollision : 0
TxDeferredTransmit  : 0
TxLateCollision     : 0
TxExcessiveCollision: 0
TxPausePkts         : 0
RxOctets            : 19755435
RxUndersizePkts     : 0
RxPausePkts         : 0
Pkts64Octets        : 1756
Pkts65to127Octets   : 21603
Pkts128to255Octets  : 1235
Pkts256to511Octets  : 4162
Pkts512to1023Octets : 737
Pkts1024to1522Octets: 10251
RxOversizePkts      : 0
RxJabbers           : 0
RxAlignmentErrors   : 0
RxFCSErrors         : 0
RxGoodOctets        : 19755653
RxDropPkts          : 0
RxUnicastPkts       : 39583
RxMulticastPkts     : 0
RxBroadcastPkts     : 162
RxSAChanges         : 9759
RxFragments         : 0
RxJumboPkts         : 0
RxSymbolErrors      : 0
RxDiscarded         : 0

        pvid: 2
        link: port:7 link:up speed:1000baseT full-duplex auto
Port 8:
        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

        pvid: 0
        link: port:8 link:down
VLAN 1:
        ports: 0 1 2 3 5 7t
VLAN 2:
        ports: 4 7
root@DD-WRT:~#


Thank you for the help.
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 12814
Location: Netherlands

PostPosted: Mon May 24, 2021 10:27    Post subject: Reply with quote
I have persuaded BS to make a GUI for setting up VLAN's might be in the next build.

So rejoice (I hope)

@PYB, we will need your expertise in testing this Smile

_________________
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
Per Yngve Berg
DD-WRT Guru


Joined: 13 Aug 2013
Posts: 6855
Location: Romerike, Norway

PostPosted: Mon May 24, 2021 12:30    Post subject: Reply with quote
resolv wrote:
port5vlans=1 2 16 #vlan16 does not appear anywhere else


16 is the "Tagged" option in the GUI. It's on line 16. The portXvlans variables does not reflect your hardware, but only if the option is selected in the GUI.


Apparently the RTL switch with LAN 5-8 is connected to port 5

Port 7 is the CPU (router)
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14102
Location: Texas, USA

PostPosted: Mon May 24, 2021 15:47    Post subject: Reply with quote
^^^ I stand corrected, as I did not know of any routers that used port 7 for CPU.
_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
resolv
DD-WRT Novice


Joined: 19 Apr 2021
Posts: 24

PostPosted: Mon May 24, 2021 19:07    Post subject: Reply with quote
Hello egc,
Quote:
I have persuaded BS to make a GUI for setting up VLAN's might be in the next build.

Thank you for this information. I look forward to this addition.
Per Yngve Berg
DD-WRT Guru


Joined: 13 Aug 2013
Posts: 6855
Location: Romerike, Norway

PostPosted: Mon May 24, 2021 20:10    Post subject: Reply with quote
I have done some tests.

swconfig dev switch0 vlan 1 set ports "0 1 2 5 7t"
swconfig dev switch0 vlan 3 set ports "3 7t"
swconfig dev switch0 set apply
vconfig add eth0 3


I did now see vlan3 with ifconfig vlan3
It does also show up in Setup->Networking


Last edited by Per Yngve Berg on Mon May 24, 2021 20:11; edited 1 time in total
resolv
DD-WRT Novice


Joined: 19 Apr 2021
Posts: 24

PostPosted: Mon May 24, 2021 20:11    Post subject: Reply with quote
Hello Per Yngve Berg,
Thank you for analyzing my hardware.

I'm learning. If you don't mind, I have some questions.

* Question-1:
(Attached is an image of my Web-GUI showing the Tagged line 16.)
You stated: 16 is the "Tagged" option in the GUI. It's on line 16. The portXvlans variables does not reflect your hardware, but only if the option is selected in the GUI.
In the Web-GUI, there are no selected options in this "Tagged" line. Shouldn't something be selected for "16" to appear in "port5vlans=1 2 16", or have I misunderstood?

* Question-2:
You stated: Port 7 is the CPU (router).
I believe that you determined this CPU information from the following two nvram variables:
Code:
vlan2ports=4 7u
vlan1ports=0 1 2 3 5 7*

But "swconfig dev switch0 help" gives the "(cpu @ 5)":
Code:
switch0: bcm53011(BCM53012), ports: 9 (cpu @ 5), vlans: 4096

Which is correct, Port 7 or Port 5? What am I misunderstanding here?

* Question-3:
Is my WAN on "vlan2 Port 4" or "vlan2 Port 0"?
Code:
vlan2ports=4 7u            # WAN = port 4 on vlan2 (WAN PORT NUMBER DOES NOT MATCH *BELOW*)
port0vlans=2               # WAN = port 0 on vlan2 (WAN PORT NUMBER DOES NOT MATCH *ABOVE*)

Again, thank you for your time and the information.



Web-GUI.png
 Description:
DD-WRT v3.0-r46733 std (05/21/21)
 Filesize:  152.83 KB
 Viewed:  5709 Time(s)

Web-GUI.png


Per Yngve Berg
DD-WRT Guru


Joined: 13 Aug 2013
Posts: 6855
Location: Romerike, Norway

PostPosted: Mon May 24, 2021 20:25    Post subject: Reply with quote
1) Port 5 is not shown in the GUI. It was the CPU port on the wrt54g router and it is tagged.

2) I also saw that with port 5, but port 7 is the only port common between vlan 1 and vlan 2, so it must be the CPU.
Goto page 1, 2, 3  Next Display posts from previous:    Page 1 of 3
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