WDS-settings depending on something else than nvram-variables....?
|Reported by:||frater||Owned by:||somebody|
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?