View Single Post
Old 02-15-2013, 09:59 PM   #8
twobob
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr
twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.
 
twobob's Avatar
 
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
Quote:
Originally Posted by knc1 View Post
That will be the first firewall hole-punching button.
To allow port 22 and fire up the ssh server with the correct options.

But you can use Wifi on your own home network, it is just the "free" public hotspots that do not (yet) work.

If you want to do it by hand:
iptables -t filter -I wlan-in -dport:22 -j ACCEPT
Or something like that, I may have the 'destination port' option typo'd - man page will show how to write it.

Without specifying a rule number to instert at, it inserts as Rule #1 - which is just the place is should go in the wlan-in chain.

Duh...
That was not an accident.
Also - notice you don't need a script - you can code that in the menu.json 'action:' field.
twobob is offline   Reply With Quote