Posted: Mon Nov 14, 2016 16:44 Post subject: patched module for ARM/ NetGear R6400
Hello, I've found maxter's patched module working on my router, but I would need it for VLAN ID 423. Could you someone provide me with patched version extended to 512 VLANs for ARM based (K3)routers? I am completely unable to make my setup to even start compiling, so making my own patched version is out of question, I did not found a working guide how to compile latest sources for my R6400 NetGear, so your help would be really appreciated.
Hi, I am using a WRT1900ACS and I need to use the VLAN 1074. So far, I can input it, but in practice it doesn't really work. I can never get an IP from the FTTH provider (JAZZTEL) in Spain.
Some other users mentioned me they moved to other firwares since DD-WRT is always causing this issue. The very high tag values are ignored or just don't work.
Is there any reported issue in this sense by anyone else before? Anything I have to do to make it work?
This is the Broadcom Forum. Your unit is a Marwel Based. Post in the Marwell Forum. Also the 15 vlan limit is not in Marwell units.
Use swconfig to configure the switch.
Sorry for the mistake, I just saw the topic when I searched but I didn't notice the forum. Anyway, I have exactly the same problem with my WRT54GS, which is Broadcom based.
Posted: Wed May 10, 2017 7:42 Post subject: Re: Patched module for ARM/ Asus RT87U
maxter wrote:
Hi all,
first of all thank for this thread this saved me lot of time gave me lot of inside info of vlan ddwrt. So here is my contribution.
I am from Dubai my ISP is Etislat, recently I moved to new apartment and new FTTH connection. previously I didnt have any issue with Vlan VID, for new setup I have to give VID 30 for PPPoE link. I read the whole thread and managed to recompile the kernel module for my device ( asus ac87u / Linux 4.4 ) with switch robo patched for 32 instead of 16. Everything is working fine when combined with the below jffs + startup script
Topic created 6 years ago but it is still valid. Recently I moved to the flat with an Orange fiber. They use VLAN 832 for the Internet. My R7000 with Kong's firmware only gave me choice of 16 vlans.
Solution was to compile the modules against linux 4.4.80 and use vconfig to configure.
Topic created 6 years ago but it is still valid. Recently I moved to the flat with an Orange fiber. They use VLAN 832 for the Internet. My R7000 with Kong's firmware only gave me choice of 16 vlans.
Solution was to compile the modules against linux 4.4.80 and use vconfig to configure.
Does anyone know if the modules that were posted by hanskloss are "generic" or if they were r7000 specific? I have an R8000 and would like to compile this with higher vlan support because my ISP uses VLANID 201 for internet.
If we know that these modules should work, I can figure out how to compile from source myself, as I supported an AOSP rom for many years.
Does anyone know if the modules that were posted by hanskloss are "generic" or if they were r7000 specific? I have an R8000 and would like to compile this with higher vlan support because my ISP uses VLANID 201 for internet.
If we know that these modules should work, I can figure out how to compile from source myself, as I supported an AOSP rom for many years.
I think they should work for your router too as they both use the same switch chip. And hanskloss already posted a module with all the VLANs so I think you don't need to compile anything yourself.
On the other hand I'm really having no luck with my WRT54GL. I would need support for up to 4K VLAN IDs but none of the patched modules in this thread are made for my version (r27858) of DD-WRT. I've been trying to compile it myself but without luck.
I downloaded the entire source for DD-WRT and I believe I need to use the linux.v24_2 (Is this right for my router?). But the problem is that after editing the switch-robo.c and running "make modules" the .ko file is not created, all I get is a switch-robo.o file. Can someone please help me patch this?
Does anyone know if the modules that were posted by hanskloss are "generic" or if they were r7000 specific? I have an R8000 and would like to compile this with higher vlan support because my ISP uses VLANID 201 for internet.
You don't need to do this at all since support for vlans up to 4096 were added already:
Try build 36168 if you need to use VAP(s); otherwise 36247 is fine. Do NOT use build 36242, at least for k3.10 routers.
sasodoma wrote:
On the other hand I'm really having no luck with my WRT54GL.
Search around for a pre-compiled version for k2.4 in the forums (or even this thread); there shouldn't have been changes in it to break the API. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Posted: Tue Jul 10, 2018 15:47 Post subject: Patched module for WRT54GL
jwh7 wrote:
Search around for a pre-compiled version for k2.4 in the forums (or even this thread); there shouldn't have been changes in it to break the API.
I've looked all over the forum and couldn't find one for k2.4. But now I figured out that the file switch-robo.o which I kept getting is in fact the module. I thought that I need the .ko file since all the other modules in this thread were .ko files but I guess k2.4 is different or something has changed since those were compiled. Anyway I wish I would've tried the .o file before spending 2 days trying to get a .ko file out of the compiler, but at least it works now so that's great.
EDIT: I attached the file in case someone else might need it but on my WRT54GL the /proc/switch/eth0/vlan/ is only populated up to 1687. I've seen this mentioned on page 6 by users checho and orca_nbk but we all found a different number of VLANs were populated. I will try to figure out what the problem is because I need the VLAN 3999.
Posted: Tue Jul 10, 2018 20:24 Post subject: Re: Patched module for WRT54GL
sasodoma wrote:
EDIT: I attached the file in case someone else might need it but on my WRT54GL the /proc/switch/eth0/vlan/ is only populated up to 1687. I've seen this mentioned on page 6 by users checho and orca_nbk but we all found a different number of VLANs were populated. I will try to figure out what the problem is because I need the VLAN 3999.
I recall there was a procedure to compile with a particular offset to get the needed value/range. I've never needed to use this stuff though.
There may just be. Today I've added an if statement in the part of the switch-core.c module that populates the vlan directory. I made it so that it populates the first 16 VLANs and then skips until 3500. That way I was able to bypass the 1687 limit and get the 3999 that I needed. But sadly that didn't work out. As soon as did this:
echo "2t 3t 5t" > 3999/ports (I was in the eth0/vlan directory) the SSH interface froze and I didn't even get a newline. Turns out that the switch stopped working, I couldn't connect through any of the ports but WLAN still works. I also tried compiling a robo module with only 512 VLANs and using the original core but nothing worked. If I echo to say VLAN 10 then it works and the port is trunked properly but anything above 15 just crashes instantly. I also tried a build from 2010 with the same results. I think a post by phuzi0n on page 6 may contain some hints. I will keep researching.
I did it! I was able to tag VLAN 3999 on all the ports. Here is the procedure:
I compiled the switch-robo module to populate all the VLANs up to 4096. This created a problem where it only populated them up to about 1700. The /proc/switch/eth0/vlan/ directory is for some reason limited in the number of entries. So, I also recompiled the switch-core module and instructed it to first populate VLANs 1-16 and then skip to 3500 and populate to the end. This enabled me to get the 3999 VLAN that I needed. I attached both of the modules.
The next step was figuring out how to use this VLAN without the switch locking up. I think that orca_nbk has already figured this out in his blog post that he linked on page 6, but the blog is down now. The clue for me was phuzi0n’s answer to that, where he mentioned groups of 16. Also this is how Tomato handles the VLANs with their offsets. In order to get it work you need to use VLAN IDs that are in the same group. The first group is 0-15, the second is 16-31, and so on (to find the first ID in the group simply divide the required VLAN ID by 16, round it down and multiply with 16 again). To get all my VLANs in the same group I had to move the vlan0 (LAN, br0) to vlan3984 and vlan1 (WAN) to vlan3985. To do this I just clean the 0/ports and 1/ports in the /proc/switch/eth0/vlans/ and echo their port settings to 3984/ports and 3985/ports. I also echo my settings for the 3999 VLAN in their respective directory.
After this all that remains is using vconfig to remove vlan0 and vlan1, add the new VLANs and use brctl to put the default VLAN back into br0 and my new VLAN into br1 (created beforehand in the GUI). Note that I don’t need the WAN port so in my case I never recreate its VLAN and I assign its port to the default VLAN. If you need the WAN port you should remove it from the default VLAN an configure the WAN vlan to be vlan3985 (or whatever your WAN VLAN will be).
Does anyone know if the modules that were posted by hanskloss are "generic" or if they were r7000 specific? I have an R8000 and would like to compile this with higher vlan support because my ISP uses VLANID 201 for internet.
You don't need to do this at all since support for vlans up to 4096 were added already:
Try build 36168 if you need to use VAP(s); otherwise 36247 is fine. Do NOT use build 36242, at least for k3.10 routers.
What do you mean by "You don't need to do this at all since support for vlans up to 4096 were added already"?
Can we now setup a VLAN with a VID of 100 via the GUI in the last DD-WRT builds?
(I have an Asus RT-AC66U (Broadcom BCM53125 switch), with DD-WRT build 36995)
Is it the role of the Networking > VLAN Tagging section in the GUI?
I need to setup a VLAN 100 to allow 2 ISP boxes to communicate, I've read the topic, but I still don't know how to do
