nvram variable for VPN policy routed IPs

[Jack Yaz]

Am I right in thinking the below is a workaround for the 1000 char limit for routers on the HND platform?

VPN_IP_LIST=$(nvram get vpn_client1_clientlist)$(nvram get vpn_client1_clientlist1)$(nvram get vpn_client1_clientlist2)$(nvram get vpn_client1_clientlist3)$(nvram get vpn_client1_clientlist4)$(nvram get vpn_client1_clientlist5)

 

[ColinTaylor]

Looks like it (it's actually a 255 byte limit in this case):

nvram: implemented workarounds and safeguards for HND limiting non-Asus nvram additions to 255 chars max
https://github.com/RMerl/asuswrt-merlin.ng/commit/4d699116e5c0b98f14b85d18f11df191e54aef41

OpenVPN client: split policy rules accross 6 * 255 chars nvram entries, join then in vpnrouting.sh (HND only)

 

[RMerlin]

Variables that are unrecognized by the firmware are limited to 256 characters. Those are are known are limited to 1000 by Broadcom.

Since that variable was added by me to the firmware, it has the 256 characters limit.

 

[Jack Yaz]

Ok thanks. Don't know why that didn't come up when i searched but obviously I was using the wrong terms. Thanks, I'll update my script accordingly.