That doesn't make sense. You say the rules work when executed interactively, but not w/ firewall script. The only difference between the scripts (startup, firewall, etc.) is simply the timing of their execution. It doesn't change the functionality. Perhaps the system needs the full path to the executables.
For example. This command:
is executed without problems through telenet but it is not working when I try to execute it through the web ("Run Commands" button, Startup, Firewall, etc.)
For the rest of commands, I have no problem to execute them through the web. ("Run Commands" button, Startup, Firewall, etc.)
That's why I believe that the issue is with the insmod command. I'm lost....
There is no init.d here that I can use? (or autoexec.bat jejeje )
There’s a difference between “executed without problems”, and working. One of the idiosyncrasies of insmod on dd-wrt is that if the module isn’t found or can’t be loaded, it doesn’t report an error. I assume the dd-wrt developers removed the error reporting, as they do w/ many common utilities, to save space.
So I was initially under the impression that when you said it was “working”, that you actually got the results you expected (and not just that it didn’t report any errors). Because if that’s the case, then it makes no sense that it wouldn’t work w/ the firewall script. OTOH, if it’s not actually working, telnet or otherwise, then it probably never loaded the modules in the first place.
Thank you eibgrad. Sorry for not being clear.
When I say working, I mean that the modules were loaded and the rules added. I determine if it works or not checking the modules loaded after the reboot.
Let me try to simplify the problem.
If I execute this command from telnet:
The module is loaded and I can use it fine.
If I put the command in the web and I click "Run Commands" it also work fine (module loaded and working fine).
However, If I save the command into the startup and/or firewall, the module is not loaded after the router is rebooted.
I have to do it manually..
Wow, this thing is fussy. You attempt to load too soon, don’t specify the path, don’t load in the right order, and it just won’t load! Anyway, the following approach finally worked for me (in the startup script)
Thank you eibgrad!!! You are awesome!!! It is working perfectly.
Thank you a lot for your help. My network is working again