WDS-settings depending on something else than nvram-variables....?

[frater]

I wrote a script to restore my NVRAM-variables and did some extensive testing with diff to see if there is any difference before and after the restore. The only thing I need to get my config working is to disable the WDS-link and enable it again.

A few months ago I had about the same when I tried to create a custom firmware for my WAN-connection in which I put my WDS-parameters in defaults.c. In the interface it looked alright, but I had to disable the WDS and put it again in LAN to get it working.

It's quite easy to put the blame on my restore-script, but doesn't it ring a bell? Is there some extra handling needed other than what's based on nvram-variables?

[BrainSlayer]

its a complex topic. you really run best if you just compare the nvram show output before and after you hit apply. but trust me, we will make it better in future. we have to live with some old code in the tree which is not easy to understand sometimes. but as far as its working, its hard to decide to change everything since this introduces new bugs almost. to study which parameters are required for wds, its best if you study the wlconf.c sourcecode. it does all the wireless control stuff

[frater]

It's really only WDS and the only thing I have to do to get it to work is put that WDS-entry to "disable" and put it on "LAN" again. No parameters have been changed in the end.

BTW.. did you see my ticket about a new command to fetch the default value of an nvram-variable? It could be usefull in my script.