Author
Message
BassT DD-WRT Novice Joined: 01 Sep 2020 Posts: 36
Posted: Sat Mar 04, 2023 14:31 Post subject: [SOLVED] Trunk Port Setup (need help)
Hi all,
I need your help please, with trunk port setup.
First my Hardware setup:
FritzBox 7490 (Internet connected)
(Wan Port unused)
Netgear R7000 (Port1: Internet connected) (ddwrt-r49681)
Netgear R6400 (Port4: connected with R7000 on Port4) (ddwrt-r49681)
Netgear GS108Ev3 (Port1: connected to Port3 on R7000)
on R7000 there is VLAN10 with own DNS for services, VLAN30 for working and VLAN40 for guest Wifi
on R6400 there is VLAN20 (smarthome) also with Wifi
FritzBox IP: 192.168.0.1
R7000 IP: 192.168.0.10 (VLAN10: 192.168.10.1 - VLAN30: 192.168.30.1 - VLAN40: 192.168.40.1)
R6400 IP: 192.168.0.20 (VLAN20: 192.168.20.1)
GS108E IP: 192.168.0.50
Now I want a trunk port for R7000 <-> R6400 on Port4, and Trunk Port on R7000 <-> GS108E Port3 <-> Port1
so I can use all VLANs on all Devices.
First, is it possible to make this workable with GUI?
And if yes, how?
For now, all work, but not the trunk port.
Please help. I could send screenshots if it help
Last edited by BassT on Mon Apr 17, 2023 18:01; edited 1 time in total
Back to top
Sponsor
Per Yngve Berg DD-WRT Guru Joined: 13 Aug 2013 Posts: 6870 Location: Romerike, Norway
Posted: Sat Mar 04, 2023 18:46 Post subject:
The GUI should work on Broadcom.
Check the switch config with:
swconfig dev switch0 show
PS. Have you configured the correct port? Port number are usually in oposite direction than the label on the causing.
Back to top
BassT DD-WRT Novice Joined: 01 Sep 2020 Posts: 36
Posted: Sat Mar 04, 2023 20:59 Post subject:
Per Yngve Berg wrote:
PS. Have you configured the correct port? Port number are usually in oposite direction than the label on the causing.
What does this mean exactly?
My problem is: if I tag the switch, I loose connection to the switch.
For now the switch had 192.168.10.50 and it is assigned to the vlan10 in switch config.
So it work but only in vlan10
if i tag it to vlan 10 and 1 and set ip to 192.168.0.50 I can't connect anymore, ...
also in
nvram show | grep vlan.*ports | sort
the port3 will not show the t?
Back to top
Per Yngve Berg DD-WRT Guru Joined: 13 Aug 2013 Posts: 6870 Location: Romerike, Norway
Posted: Sat Mar 04, 2023 21:40 Post subject:
Those nvram variables are no longer in use.
I aaked you to do a "swconfig dev switch0 show"
The switch must be configured using swconfig commands.
Back to top
BassT DD-WRT Novice Joined: 01 Sep 2020 Posts: 36
Posted: Sun Mar 05, 2023 8:46 Post subject:
Per Yngve Berg wrote:
I aaked you to do a "swconfig dev switch0 show"
Code:
DD-WRT v3.0-r49681 std (c) 2022 NewMedia-NET GmbH
Release: 08/13/22
Board: Netgear R7000
Zion login: root
Password:
==========================================================
___ ___ _ _____ ______ ____ ___
/ _ \/ _ \___| | /| / / _ \/_ __/ _ __|_ / / _ \
/ // / // /___/ |/ |/ / , _/ / / | |/ //_ <_/ // /
/____/____/ |__/|__/_/|_| /_/ |___/____(_)___/
DD-WRT v3.0
https://www.dd-wrt.com
==========================================================
BusyBox v1.35.0 (2022-08-13 08:30:56 +07) built-in shell (ash)
root@Zion:~# swconfig dev switch0 show
Global attributes:
enable_vlan: 1
ports: 0x01bf
reset_mib: ???
enable_jumbo: 0
allow_vid_4095: 0
Port 0:
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: 2
link: port:0 link:down
Port 1:
mib: TxOctets : 3098416
TxDropPkts : 0
TxBroadcastPkts : 249
TxMulticastPkts : 396
TxUnicastPkts : 18495
TxCollisions : 0
TxSingleCollision : 0
TxMultipleCollision : 0
TxDeferredTransmit : 0
TxLateCollision : 0
TxExcessiveCollision: 0
TxPausePkts : 0
RxOctets : 7808649
RxUndersizePkts : 0
RxPausePkts : 0
Pkts64Octets : 477
Pkts65to127Octets : 10539
Pkts128to255Octets : 4856
Pkts256to511Octets : 399
Pkts512to1023Octets : 774
Pkts1024to1522Octets: 3700
RxOversizePkts : 0
RxJabbers : 0
RxAlignmentErrors : 0
RxFCSErrors : 0
RxGoodOctets : 7808649
RxDropPkts : 0
RxUnicastPkts : 20456
RxMulticastPkts : 143
RxBroadcastPkts : 146
RxSAChanges : 1
RxFragments : 0
RxJumboPkts : 0
RxSymbolErrors : 0
RxDiscarded : 0
disable: ???
pvid: 1
link: port:1 link:up speed:1000baseT full-duplex auto
Port 2:
mib: TxOctets : 40026416
TxDropPkts : 0
TxBroadcastPkts : 255
TxMulticastPkts : 39
TxUnicastPkts : 146120
TxCollisions : 0
TxSingleCollision : 0
TxMultipleCollision : 0
TxDeferredTransmit : 0
TxLateCollision : 0
TxExcessiveCollision: 0
TxPausePkts : 0
RxOctets : 400962103
RxUndersizePkts : 0
RxPausePkts : 0
Pkts64Octets : 334
Pkts65to127Octets : 49090
Pkts128to255Octets : 4767
Pkts256to511Octets : 743
Pkts512to1023Octets : 1696
Pkts1024to1522Octets: 260195
RxOversizePkts : 0
RxJabbers : 0
RxAlignmentErrors : 0
RxFCSErrors : 0
RxGoodOctets : 400962103
RxDropPkts : 0
RxUnicastPkts : 316719
RxMulticastPkts : 0
RxBroadcastPkts : 106
RxSAChanges : 7310
RxFragments : 0
RxJumboPkts : 0
RxSymbolErrors : 0
RxDiscarded : 0
disable: ???
pvid: 10
link: port:2 link:up speed:1000baseT full-duplex auto
Port 3:
mib: TxOctets : 155754
TxDropPkts : 0
TxBroadcastPkts : 551
TxMulticastPkts : 500
TxUnicastPkts : 139
TxCollisions : 0
TxSingleCollision : 0
TxMultipleCollision : 0
TxDeferredTransmit : 0
TxLateCollision : 0
TxExcessiveCollision: 0
TxPausePkts : 0
RxOctets : 13756
RxUndersizePkts : 0
RxPausePkts : 0
Pkts64Octets : 102
Pkts65to127Octets : 21
Pkts128to255Octets : 30
Pkts256to511Octets : 0
Pkts512to1023Octets : 0
Pkts1024to1522Octets: 0
RxOversizePkts : 0
RxJabbers : 0
RxAlignmentErrors : 0
RxFCSErrors : 0
RxGoodOctets : 13756
RxDropPkts : 0
RxUnicastPkts : 12
RxMulticastPkts : 39
RxBroadcastPkts : 102
RxSAChanges : 55
RxFragments : 0
RxJumboPkts : 0
RxSymbolErrors : 0
RxDiscarded : 0
disable: ???
pvid: 0
link: port:3 link:up speed:1000baseT full-duplex auto
Port 4:
mib: TxOctets : 4720917
TxDropPkts : 0
TxBroadcastPkts : 372
TxMulticastPkts : 462
TxUnicastPkts : 31116
TxCollisions : 0
TxSingleCollision : 0
TxMultipleCollision : 0
TxDeferredTransmit : 0
TxLateCollision : 0
TxExcessiveCollision: 0
TxPausePkts : 0
RxOctets : 16824002
RxUndersizePkts : 0
RxPausePkts : 0
Pkts64Octets : 229
Pkts65to127Octets : 17912
Pkts128to255Octets : 5934
Pkts256to511Octets : 580
Pkts512to1023Octets : 565
Pkts1024to1522Octets: 9132
RxOversizePkts : 0
RxJabbers : 0
RxAlignmentErrors : 0
RxFCSErrors : 0
RxGoodOctets : 16824002
RxDropPkts : 0
RxUnicastPkts : 34254
RxMulticastPkts : 77
RxBroadcastPkts : 21
RxSAChanges : 369
RxFragments : 0
RxJumboPkts : 0
RxSymbolErrors : 0
RxDiscarded : 0
disable: ???
pvid: 1
link: port:4 link:up speed:1000baseT full-duplex auto
Port 5:
mib: TxOctets : 423581122
TxDropPkts : 0
TxBroadcastPkts : 375
TxMulticastPkts : 259
TxUnicastPkts : 354855
TxCollisions : 0
TxSingleCollision : 0
TxMultipleCollision : 0
TxDeferredTransmit : 0
TxLateCollision : 0
TxExcessiveCollision: 0
TxPausePkts : 0
RxOctets : 44925368
RxUndersizePkts : 0
RxPausePkts : 0
Pkts64Octets : 1287
Pkts65to127Octets : 137568
Pkts128to255Octets : 17334
Pkts256to511Octets : 2036
Pkts512to1023Octets : 2940
Pkts1024to1522Octets: 18882
RxOversizePkts : 0
RxJabbers : 0
RxAlignmentErrors : 0
RxFCSErrors : 0
RxGoodOctets : 44925368
RxDropPkts : 0
RxUnicastPkts : 179065
RxMulticastPkts : 495
RxBroadcastPkts : 487
RxSAChanges : 33305
RxFragments : 0
RxJumboPkts : 0
RxSymbolErrors : 0
RxDiscarded : 500
disable: ???
pvid: 0
link: port:5 link:up speed:1000baseT full-duplex
VLAN 1:
ports: 1 3t 4 5t
VLAN 2:
ports: 0 5t
VLAN 10:
ports: 2 3t 5t
[/code]
Back to top
Per Yngve Berg DD-WRT Guru Joined: 13 Aug 2013 Posts: 6870 Location: Romerike, Norway
Posted: Sun Mar 05, 2023 11:12 Post subject:
Looks good.
The ports: WAN VLAN1 VLAN10 TRUNK VLAN1
You can check that the port goes down when unplugging.
This will work when the GS108E is configured accordingly.
Back to top
BassT DD-WRT Novice Joined: 01 Sep 2020 Posts: 36
Posted: Sun Mar 05, 2023 12:45 Post subject:
Per Yngve Berg wrote: Looks good.
You can check that the port goes down when unplugging.
This will work when the GS108E is configured accordingly.
Yes, the port goes down.
OK, is it normal, that i cant acces to the gs108e gui anymore? Ore there any options to make it also workable?
Will not try to configure the switch correctly
EDIT:
also, I'm wondering, why is port3 pvid: 0?
should it not be 1?
EDIT2:
Yea, VLAN10 on GS108E now work
but can't acces to the gui (was not a problem, but would be cool)
Now, trying to make the trunkport between the R7000 and R6400 workable
Back to top
Per Yngve Berg DD-WRT Guru Joined: 13 Aug 2013 Posts: 6870 Location: Romerike, Norway
Posted: Sun Mar 05, 2023 13:51 Post subject:
You have to be on the Management VLAN to access the GUI on the GS108E
Back to top
BassT DD-WRT Novice Joined: 01 Sep 2020 Posts: 36
Back to top
BassT DD-WRT Novice Joined: 01 Sep 2020 Posts: 36
Posted: Thu Apr 06, 2023 15:07 Post subject: New start ;)
Hi @ll,
now I am again on my trunk setup.
I managed the trunk port (both port 4) between the two ddwrt routers working.
But: now a lot of devices from VLAN20 (managed in R6400 with own dhcp) are listed in R7000. Some other are listed in fritzbox, ...
How to fix this?
Overview:
Description:
Filesize:
244.63 KB
Viewed:
1184 Time(s)
Description:
Filesize:
223.89 KB
Viewed:
1184 Time(s)
Description:
Filesize:
114.56 KB
Viewed:
1184 Time(s)
Back to top
Per Yngve Berg DD-WRT Guru Joined: 13 Aug 2013 Posts: 6870 Location: Romerike, Norway
Posted: Thu Apr 06, 2023 17:10 Post subject:
When you have several dhcp servers on the same vlan, a client will get an address from the one that answer first.
The list may come from the arp table. The router have communicated with the device and have it's MAC address recorded.
Back to top
BassT DD-WRT Novice Joined: 01 Sep 2020 Posts: 36
Posted: Thu Apr 06, 2023 17:52 Post subject:
Per Yngve Berg wrote: When you have several dhcp servers on the same vlan, a client will get an address from the one that answer first.
The list may come from the arp table. The router have communicated with the device and have it's MAC address recorded.
OK, but, the DHCP for VLAN20 is on R6400 who also manage the Wifi for this VLAN.
the R7000 manage VLAN 10/30 and 40.
So, for my understanding; the devices connect to the Wifi on R6400 and become their IP (Static managed) from there.
Strange is, that the devices were listed with thair static IP's on the R7000 (with *) because the devices are not listed in DHCP Table there, ...
EDIT: There is only one DHCP per VLAN;
R7000 had DHCP for VLAN10/30/40
R6400 had DHCP for VLAN20
also the CLients had static IP's set in the Router, who manage the VLAN, ...
I think I need more input about Trunkport.
I figured out, if I set the br0 off in Routers, the VLAN seems to work better, but I loose the R6400 management and also monitoring for it, ...
Description:
Filesize:
340.59 KB
Viewed:
1157 Time(s)
Back to top
BassT DD-WRT Novice Joined: 01 Sep 2020 Posts: 36
Posted: Mon Apr 17, 2023 18:00 Post subject: [SOLVED]
I found the solution by myself, after days of trying, and thinking
On Router 2 there is VLAN20
On Router 1 there is VLAN10 / 30 /40
after setup the trunkport, the VLAN will be there automatically on the other Router (assigned to br0)
Solution:
assign on Router 2 VLAN10 / 30 / 40 to "none"
assign on Router 1 VLAN20 to "none"
Now all work, ... and the clients don't become a Router 0 IP anymore.
Back to top