Jeffrey Young
Very Senior Member
Well, if you need to pass VLAN 100 and 105, you probably need to tag VLAN 105 on the WAN port as well (eth0). try creating another tagged interface, this time on eth0 (the wan) and add it to the bridge.
Well, if you need to pass VLAN 100 and 105, you probably need to tag VLAN 105 on the WAN port as well (eth0). try creating another tagged interface, this time on eth0 (the wan) and add it to the bridge.
ip link add link eth0 name eth0.105 type vlan id 105
ip link set dev eth0.105 up
brctl addif br101 eth0.105
Looks right.Hum, not sure these are the correct commands?
Code:ip link add link eth0 name eth0.105 type vlan id 105 ip link set dev eth0.105 up brctl addif br101 eth0.105
Thanks
Looks right.
user@ASUSWRT:/tmp/home/root# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.fc34978b2170 yes eth3
eth4
eth5
eth6
eth7
wl0.2
br101 8000.107b44e290c2 yes eth0.105
eth0.v0
eth1.v0
eth2.100
eth2.v0
Sorry. It was a shot to begin with. I don't have anything similar to setup to test.
Perhaps the ISP Router is also doing some authentication as well that you are unaware of.
IP a
does not work with Merlin. Maybe entware has a more complete version of the ip
command.If it is not closed source, it should be in the source code. But I don't know where to start looking.Is there a way to see the code that is behind the ASUS configuration for the "vodafone Portugal" profile?
You're referring to the roboconfig commands you used in post 7?
If so, I noted in that post, eth0 is being tagged with VLAN 101 and 105 as opposed to 100 and 105. Same with eth2 (physical lan port 3). Maybe you need to adjust the VLAN from 100 to 101.
No, it was a tool specific to the older router's chip sets. Setting vlans up in the newer routers via thewould i be able to install robocfg through entware? going to try that but don't really have an idea of what i'm doing (just hope i dont brick the router! lo)
ip
tool is pretty much the same thing.No, it was a tool specific to the older router's chip sets. Setting vlans up in the newer routers via theip
tool is pretty much the same thing.
vconfig add eth0 101
vconfig add eth0 105
ifconfig vlan101 up
ifconfig vlan105 up
robocfg vlan 100 ports "0t 3t 8t"
robocfg vlan 101 ports "0t 4t 8t"
robocfg vlan 105 ports "0t 3t 8t"
Now that the VLAN's are created, we just need to create the trunk port on the router:
filipe@RT-AC66U:/tmp/home/root# robocfg vlan 1 ports "1 2 3 8t"
filipe@RT-AC66U:/tmp/home/root# robocfg vlan 100 ports "0t 4t 8t"
filipe@RT-AC66U:/tmp/home/root# robocfg vlan 101 ports "0t 4t 8t"
filipe@RT-AC66U:/tmp/home/root# robocfg vlan 105 ports "0t 4t 8t"
So first we are removing the port 4 from the default VLAN1.
Then we are adding the VLANs 100, 101 and 105 to the ports "0t 4t 8t". Essentially we are telling the router to duplicate the trunked network on the WAN port 0 to the LAN port 4 in addition to itself via port 8.
This port 8 is a special port (called the CPU internal port). If you want the router to interact with any of the network traffic on the ports, it needs to be "plugged into" the CPU internal port. If omitted, the router will pass along the traffic from one external port to another and otherwise not pay attention to it.
ip
brctl addbr br101
brctl stp br101 on
brctl setfd br101 2
brctl delif br0 eth4
Yep, you can do the same thing withip
First, not sure about the old routers, but if the mapping between the internal names and the physical ports are the same as with the newer routers, port 4 actually refers to physical LAN port 1. i.e. eth4 is marked LAN port 1 on the router and eth1 is marked as LAN port 4 on the router.
So, if you want to just skip the LAN IPTV setup in the GUI altogether, you can build your own bridge (br101) as such
Bash:brctl addbr br101 brctl stp br101 on brctl setfd br101 2
Now assuming you want everything on physical port 1, which is eth4, then remove eth4 from the main bridge (br0)
Diff:brctl delif br0 eth4
Then, using the examples above, create vlan tagged interfaces for eth0 and eth4 for VLAN 100, 101, and 105. Bring them up and add them to your new bridge.
You may also have to bring the bridge up as well
What I don't know is if the ISP is expecting the router to do any DHCP client work on the new bridge? Does the bridge need a static IP address (assigned by the ISP)? If so, you may have to assign the IP address to the new bridge that the ISP assigned to you. One thing is for sure, setting up the bridge is just one step. If the new bridge is using DHCP, then we are going to have to setup DNSMASQ as well. If static, we need to assign an address to the new bridge.
You can probably make this work, but we will need more information.
vconfig add eth0 101
vconfig add eth0 105
ifconfig vlan101 up
ifconfig vlan105 up
robocfg vlan 100 ports "0t 8t"
robocfg vlan 101 ports "0t 4t 8t"
robocfg vlan 105 ports "0t 3t 8t"
robocfg vlan 100 ports "0t 3t 8t"
ip link add link eth2 name eth2.100 type vlan id 100
ip link set dev eth2.100 up
brctl addif br101 eth2.100
OK, to just add the internet to physical port three (eth2), you would;
Code:ip link add link eth2 name eth2.100 type vlan id 100 ip link set dev eth2.100 up brctl addif br101 eth2.100
Sorry that I can't be of any more help. I understand what is going on now. Bell does something similar here as well. Just that Bell allows for bridging. I think just some experimenting on your part may be all that is required. Maybe also considering using a tool like wireshark to see what exactly is going on. It might reveal something.
Anyway, I am interested to know if you ever get it working. I wish I had the setup required to mimic what you need. If you do get it going, post your setup. Others may be interested.
vport : Enable/disable/query Switch for VLAN port mapping
An alternative to robocfg on HND platform seems to be vlanctl. However, after several hours of searching, trying and error, I believe vlanctl can only create tagged VLAN, which unfortunately can’t satisfy my need.
ethtool
is a Linux tool for query or control network driver and hardware settings. It is pretty standard. The vlanctl
has shown up in a number of post. This one in particular. vlanctl
seemed to be the up and coming star until it was figured out tagging interfaces with the ip
tool was a lot easier.ip
tool. Works just fine.Hello,Thank you for all your help with it, and I'll definitely post the solution once I find it.
I found this post here in the forum by @.TT. that details the sintax for the ethctl which seems to be the new Broadcom tool to achieve what was previously done with robocfg.
More specifically, I think the command to tag specific interfaces is probably the vport:
But I'm still clueless about how to do this.
I see that @Gingernut is trying to achieve something similar with a script a couple posts down, not sure if he did manage to find out the correct commands?
Further digging led me to this other post where the author has a mapping of the interface to the physical port:
View attachment 53971
In that posts he also mentions another tool vlanctl:
Not sure if that would be enough for me? I did find this other post with syntax of vlanctl and in this page there are some usage commands examples using the vlanctl tool.
I also found this vlantest tool as part of the Merlin source code.
Finally, I also found this thread here in the forum that deals with VLAN's in the new Broadcom chipsets. I think @LeandroBR did manage to get it working.
I think the solution to my problem is in the posts above. I'm going to go through it and find a solution for this. And of course, I'll post it here once I figure it out.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!