For anyone stumbling onto this page looking for the same thing, the syntax is:
iptables -t mangle -A POSTROUTING -o usb0 -j TTL --ttl-set 65
This will change the TTL of all packets being routed through the usb attached android phone to 65.
This works perfectly.
If anyone is happening upon this thread here is what I did:
- install merlin
- download the right one from the website
- extract it
- go to your router.asus.com page
- in administration>firmware upgrade, upload your file and flash
- enable etend the ttl value and spoof lan ttl value in usb modem settings on your router.asus.com page
- enable ssh at administration>system in router.asus.com
- ssh in (I used router.asus.com) and my password
- run chmod a+rx /jffs/scripts/*
- navigate to jffs/scripts
- type nano firewall-start
- edit the script to be:
#!/bin/sh
iptables -t mangle -A POSTROUTING -o -usb0 -j TTL --ttl-set 65
- ctrl+x and save it
- reboot the router
I also set up tasker on my phone to turn on usb tethering, I used the power/usb in the state list then used secure settings to turn on usb tethering. Working like a charm.
I used SSH to send "iptables -t mangle -A POSTROUTING -o -usb0 -j TTL --ttl-set 65" and my tethered USB phone went from 5 to full 20-30mbps speed on speedtest.net! YAE!This works perfectly.
If anyone is happening upon this thread here is what I did:
- install merlin
- download the right one from the website
- extract it
- go to your router.asus.com page
- in administration>firmware upgrade, upload your file and flash
- enable etend the ttl value and spoof lan ttl value in usb modem settings on your router.asus.com page
- enable ssh at administration>system in router.asus.com
- ssh in (I used router.asus.com) and my password
- run chmod a+rx /jffs/scripts/*
- navigate to jffs/scripts
- type nano firewall-start
- edit the script to be:
#!/bin/sh
iptables -t mangle -A POSTROUTING -o -usb0 -j TTL --ttl-set 65
- ctrl+x and save it
- reboot the router
I also set up tasker on my phone to turn on usb tethering, I used the power/usb in the state list then used secure settings to turn on usb tethering. Working like a charm.
You are correct, that was a typo. BTW that wasn't my script it was @Clinton Cochrane's.WAIT! I think ColinTaylor justhad a typo in his script?? I could not get my speed back up with his:
iptables -t mangle -A POSTROUTING -o -usb0 -j TTL --ttl-set 65
So I tried the previous in the thread one:
iptables -t mangle -A POSTROUTING -o usb0 -j TTL --ttl-set 65
And got faster speed again!
Correct.Am I correct that it either works or it does not? If works, we get what is available, otherwise we get normal tethered value, right? Ie., I do not need to try to 'tweak' the value of 65 to get a faster speed, right?
THANKS!!!!!! I am SOOOOOO Happy with how this is working!!!
One last question please? Some of the writeups say you need a different TTL value to prevent some websites not loading... In the hour I have played so far, I have found 4-5 sits that say "not available." I wonder if this is just normal or if it is related to my opening up my tether speed? Time will tell, but Any ideas?
No. User scripts like firewall-start are part of Merlin's firmware. They will not work with stock Asus firmware.Since the factory RT-68U firmkware does not include a "format JFFS partician, will my simply adding the subdirectory scripts under the already present /JFFS directory be work? I assume the firmware looks for a file named firewall-start in such a directory, and if found, runs it automatically when required? If so, I will be good after power failures or reboots...
That wasn't me. Again, that was @Clinton Cochrane.PS: You had in 2019 listed adding another program to force your phone to turn on USB tethering: forgive me as you probably know now that is no longer required? For anyone who does not, there is a setting in android phones now to automatically turn on USB tethering as soon as any USB cable is plugged in: if you don't know yet, it is under your phones settings->system->advanced->developer options. You gain access to developer options by asking 4 or 5 (I dont reccall exact number) times. If you need help turning on developer options, duckduckgo it.
Sorry.Please answer the previous questions.
That's normal. You won't see a TTL of 64 or 65 returned by ping.I am getting TLS in the 50's instead of 65/64 according to pings from router and laptop to ask.com/microsoft.com.
C:\Users\Colin>ping www.ask.com
Pinging askmedia.map.fastly.net [151.101.62.114] with 32 bytes of data:
Reply from 151.101.62.114: bytes=32 time=12ms TTL=58
Reply from 151.101.62.114: bytes=32 time=13ms TTL=58
Reply from 151.101.62.114: bytes=32 time=10ms TTL=58
Reply from 151.101.62.114: bytes=32 time=10ms TTL=58
No other issue! Just trying to get the TTL to 65That's normal. You won't see a TTL of 64 or 65 returned by ping.
Code:C:\Users\Colin>ping www.ask.com Pinging askmedia.map.fastly.net [151.101.62.114] with 32 bytes of data: Reply from 151.101.62.114: bytes=32 time=12ms TTL=58 Reply from 151.101.62.114: bytes=32 time=13ms TTL=58 Reply from 151.101.62.114: bytes=32 time=10ms TTL=58 Reply from 151.101.62.114: bytes=32 time=10ms TTL=58
So apart from the TTL value what is the actual issue?
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!