Hello, I have a TP-Link TL-WR740N v4 and I need to isolate a machine through a number 3 vlan on port 2. However, I am not successful. The machine doesn't get ip. I created the track 192.168.50.1/24 with the interface br2. Where can I miss the configuration?
Follow some exits:
Code:
swconfig dev eth1 show
Global attributes:
enable_vlan: 1
Port 0:
pvid: 1
link: port:0 link:up speed:1000baseT full-duplex txflow rxflow
Port 1:
pvid: 1
link: port:1 link:down
Port 2:
pvid: 3
link: port:2 link:up speed:100baseT full-duplex auto
Port 3:
pvid: 1
link: port:3 link:down
Port 4:
pvid: 1
link: port:4 link:down
VLAN 1:
vid: 1
ports: 0t 1 3 4
VLAN 3:
vid: 3
ports: 0t 2
You didn't mention if you set up a DCHP server for br2. You will need that unless you create a static IP on the machine plugged into port 2 of your router. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
You didn't mention if you set up a DCHP server for br2. You will need that unless you create a static IP on the machine plugged into port 2 of your router.
The dhcp was created in dhcpd with the network 192.168.50.1/24
Joined: 18 Mar 2014 Posts: 13693 Location: Netherlands
Posted: Wed Jul 10, 2024 17:38 Post subject:
You might have corrupted your bridge index.
wlan0.1 and br1 both have the same IP address that is wrong.
You should have kept wlan0.1 bridged and assign (=bridge) it to br1.
You might have corrupted your bridge index.
wlan0.1 and br1 both have the same IP address that is wrong.
You should have kept wlan0.1 bridged and assign (=bridge) it to br1.
wlan0.1 is bridged and should not have its own IP address.
and br0 does not need a VLAN tag.
and eth1 should be unbridged as you are using VLAN1 as LAN interface.
Your router is a special case, it has 2 CPU ports but only 1 port is connected to the switch.
So a mixture of 1 CPU port and 2 CPU ports see my signature
Finally, if everything works, you should check that the WAN port is working properly.
I see that nothing is connected to the WAN port.
There are routers where eth0 and eth1 are also swapped (to make the confusion complete)
Therefore it is important for me that you check that the WAN port is working. _________________ Quickstart guides:
You might have corrupted your bridge index.
wlan0.1 and br1 both have the same IP address that is wrong.
You should have kept wlan0.1 bridged and assign (=bridge) it to br1.
Well, thanks for the information so far. I reset starting from scratch. Following the suggested documentation, I focused on creating vlan number 3, on port 3, with connectivity on the wan port. In setup - Networking, I created the br2 network for the vlan3 interface.
At the moment I only have wlan0 wireless network and connectivity. Nothing connects by cable. When I disable the vlans, I return with network and connectivity on vlan1. Is there anything I can still do?
Below I will insert the outputs with the new settings:
Code:
1: lo: <LOOPBACK,MULTICAST,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP qlen 1000
link/ether e8:94:**:**:**:** brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP qlen 1000
link/ether e8:94:**:**:**:** brd ff:ff:ff:ff:ff:ff
5: vlan1@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP100> mtu 1500 qdisc noqueue master br0 state UP
link/ether e8:94:**:**:**:** brd ff:ff:ff:ff:ff:ff
6: vlan2@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP100> mtu 1500 qdisc noqueue master br0 state UP
link/ether e8:94:**:**:**:** brd ff:ff:ff:ff:ff:ff
7: vlan3@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP100> mtu 1500 qdisc noqueue master br1 state UP
link/ether e8:94:**:**:**:** brd ff:ff:ff:ff:ff:ff
8: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether e8:94:**:**:**:** brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 brd 192.168.1.255 scope global br0
valid_lft forever preferred_lft forever
9: br1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether e8:94:**:**:**:** brd ff:ff:ff:ff:ff:ff
inet 192.168.40.1/24 brd 192.168.40.255 scope global br1
valid_lft forever preferred_lft forever
10: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP
link/ether e8:94:**:**:**:** brd ff:ff:ff:ff:ff:ff
11: ppp0: <POINTOPOINT,MULTICAST,UP,LOWER_UP> mtu 1492 qdisc fq_codel state UNKNOWN qlen 3
link/ppp
inet 100.50.1.150 peer 16.64.0.1/32 brd 100.50.1.150 scope global ppp0
valid_lft forever preferred_lft forever
So a mixture of 1 CPU port and 2 CPU ports see my signature
Finally, if everything works, you should check that the WAN port is working properly.
I see that nothing is connected to the WAN port.
There are routers where eth0 and eth1 are also swapped (to make the confusion complete)
Therefore it is important for me that you check that the WAN port is working.
_________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
So a mixture of 1 CPU port and 2 CPU ports see my signature
Finally, if everything works, you should check that the WAN port is working properly.
I see that nothing is connected to the WAN port.
There are routers where eth0 and eth1 are also swapped (to make the confusion complete)
Therefore it is important for me that you check that the WAN port is working.
Thanks for remember. I did the update, but I still have the same difficulty creating the vlan.
Screenshot 2024-07-11 at 13-26-33 DD-WRT (build 57200) - Router Status.png
confirm that everything works and I will report it to the developer
Unfortunately it didn't work. Layman's question. I have three mac on the router. eth1, lan, and (wlan = wan) have the same mac. Is this right? Doesn't this create conflict?
