in phuzi0n's other post his mentioned echoing it to the tmp directory also (which is how I found it in the first place)... you have /etc/ listed, maybe you need to echo it into /tmp/pptpd/ip-up
Good catch. FYI /etc isn't writable, it's part of the squashfs. Your ip-up script can be stored wherever you want (JFFS, a USB drive, etc.) as long as you update your PPTP config to point to it. I think you'll also need to chmod it to make it executable but I don't actually use PPTP so I'm just going off what I know about it and linux in general. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
I can't get the command to work automatically from the Cron window in the GUI.
The funny thing is:
echo -n 'iptables -I FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu' >> /tmp/pptpd/ip-up
works perfectly from the console. It's not to hard to enter this line when te router is rebooted but is has to work somehow automatically.
Like I said, read the cron wiki because you need to use the full path to commands you use or modify the PATH variable if you want to use cron. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
Hmm, no it doesn't. I did not had the time to look in the DDWRT Cron wiki and test settings. Maybe today, if I find anything I will post is here. Untill then, still interested in suggestions.
i think its better to run it as an start up script, better than a cron job.
Yes! Thanks to lightman I tried to put the script once again in the commands as startup script. This time it works! The previous time I tried this option I used the /etc instead of the /tmp folder location... that aint gonna work After that I did not try this option again and began focussing on the cron job part.
For everyone that needs to fix this problem do the following (it's the only thing needed, at least in my experience):
1) In the DDWRT GUI go to "Administration"
2) Click "commands"
3) Paste this code in the white command box (-n means newline):
and i was amazed about it, yesterday i updated my Linksys E2000 with the latest EKO build for this unit
DD-WRT v24-sp2 (12/19/10) mega - build 15943M NEWD-2 K2.6 Eko
it seems to be fixed already in this build, ive never edited the script before
you don't need to kill the PPTP daemon after editing the ip-up script?
did you tested the VPN after the reboot with the startup script?
can we ask to add this to the newer firmware build? if yes, how to do?
Hmm... looks like I yelled a bit too early. The rule is indeed in the file, but I have no internet connection over the VPN... do you know how to restart the PPTP deamon?
It is strange though.. when you manually add the line in the ip-up script, there is no restart of the deamon needed... why is it needed when it automatically is inserted...?