@ Frater - AsiaBlock

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3 ... 13, 14, 15, 16  Next
Author Message
frater
DD-WRT Guru


Joined: 07 Jun 2006
Posts: 2777

PostPosted: Thu Nov 04, 2010 18:41    Post subject: Reply with quote
cedriclille wrote:

Where am I wrong ... Is Frater somewhere out there ??
Yes... here I am;-)
cedriclille wrote:

My goals are :

- access asterisk outside from my Lan but only from France (I modified S95asiablock with "noAsia="fr")
I created worldblock for exactly this purpose. It will do the reverse of asiablock and it will whitelist countries and block the rest
cedriclille wrote:

- try to block bruteforce Asterisk hacks with limiting connections attempts to 3/mn.
I've created stophammer for this. It will even completely block those hammering clients entirely if they keep on hammering
cedriclille wrote:
This morning I had a brute force attack from UK [213.174.xxx.xxx] ...
This will not happen then.

If you use the 'stophammer' script a few things will happen. Both the INPUT & FORWARD chain will get their tcp connections protected by syn_flood. You can manually add some other protocols/ports in rc_firewall.

A cronjob will check your log every 20 minutes and it will add IP's that persist into the syn_flood chain. These IP's will then get their packets dropped without making an entry in the log if they enter the syn_flood chain.

You can check the firewalls a they all get a symbolic link in /tmp/etc/config/

Try this:

Code:
service stophammer on
service stophammer start
service worldblock on
service worldblock start
service asiablock on
service asiablock start


rc_firewall
Code:
wanf=`get_wanface`
iptables -I INPUT 2 -p udp -i $wanf --dport 12000:13000 -j ACCEPT
iptables -I INPUT 2 -i $wanf -p udp -m multiport --dports 2727,5060 -j ACCEPT
iptables -I INPUT 2 -i $wanf -p udp -m multiport --dports 2727,5060 -j world
iptables -I INPUT 2 -i $wanf -p udp -m multiport --dports 2727,5060 -j syn_flood

iptables -I FORWARD 1 -i $wanf -p tcp --dport 20:1024 -j asia


Your app (asterisk, ssh or other service) still needs to drop the connection so the hacker needs to create a new connection. If your app keeps the connection open and lets it hack away, these connection limit rules will work.

You will probably have more questions, but please implement this ruleset first....

Don't forget to change the country in worldblock to 'fr'

_________________
Asus RT16N + OTRW
Kingston 4GB USB-disk 128 MB swap + 1.4GB ext3 on /opt + 2 GB ext3 on /mnt
Copperjet 1616 modem in ZipB-config
Asterisk, pixelserv & Pound running on router
Another Asus RT16N as WDS-bridge

DD-WRT v24-sp2 vpn (c) 2010 NewMedia-NET GmbH
Release: 12/16/10 (SVN revision: 15758M)
Sponsor
cedriclille
DD-WRT Novice


Joined: 23 Jan 2008
Posts: 24

PostPosted: Sun Nov 21, 2010 17:45    Post subject: Reply with quote
Thanks Eko & Masterman for your answer.

I wasn't ablse to answer the last few days but I saw that I still have hack attempts and I want to find a good solution.

@Eko :

I can't go further because even after reinstalling Optware the Right way, I don't have any "worldblock" service when I run the commande "service".

Moreover, I thought that Asterisk must be restarted after applying iptables rules with this command :
/opt/etc/init.d/S90asterisk restart.
This command was put on top of the iptables commands and saved into "FIREWALL STARTUP".

Is this the right place ? What's the difference between "Firewall startup" and [normal]"startup" '(are you allowed to store in FIREWALL STATUP" other things that iptables commands)???

Thanks for your answers, you're doing a good job !!
frater
DD-WRT Guru


Joined: 07 Jun 2006
Posts: 2777

PostPosted: Sun Nov 21, 2010 19:33    Post subject: Reply with quote
cedriclille wrote:
I can't go further because even after reinstalling Optware the Right way, I don't have any "worldblock" service when I run the commande "service".!!


I retested the install procedure by doing a virgin install on my WDS-bridge.
It seems there was a flaw in detecting the version of your DD-WRT.

I have corrected it and now it should be alright

I guess that's why no-one is giving feedback on my stophammer, fixtables and worldblock scripts.....

_________________
Asus RT16N + OTRW
Kingston 4GB USB-disk 128 MB swap + 1.4GB ext3 on /opt + 2 GB ext3 on /mnt
Copperjet 1616 modem in ZipB-config
Asterisk, pixelserv & Pound running on router
Another Asus RT16N as WDS-bridge

DD-WRT v24-sp2 vpn (c) 2010 NewMedia-NET GmbH
Release: 12/16/10 (SVN revision: 15758M)
Masterman
DD-WRT Guru


Joined: 24 Aug 2009
Posts: 2070
Location: South Florida

PostPosted: Sun Nov 21, 2010 20:51    Post subject: Reply with quote
frater wrote:
cedriclille wrote:
I can't go further because even after reinstalling Optware the Right way, I don't have any "worldblock" service when I run the commande "service".!!


I retested the install procedure by doing a virgin install on my WDS-bridge.
It seems there was a flaw in detecting the version of your DD-WRT.

I have corrected it and now it should be alright

I guess that's why no-one is giving feedback on my stophammer, fixtables and worldblock scripts.....


Worldblock is impractical for the U.S users, unless you are using it for one protocol only.

Stophammer works great, but sometimes it just floods the logs with garbage.

Your new fixtables script with the INVALID state at the beginning of the INPUT chain still has me confused..

_________________
Optware, the Right Way
Asus RT-AC68U
Asus RT-N66U
Asus RT-N10
Asus RT-N12
Asus RT-N16 x5
Asus WL520gU
Engenious ECB350
Linksys WRT600Nv1.1
Linksys WRT610Nv1
Linksys E2000
Netgear WNDR3300
SonicWall NSA220W
SonicWall TZ215W
SonicWall TZ205W
SonicWall TZ105W
frater
DD-WRT Guru


Joined: 07 Jun 2006
Posts: 2777

PostPosted: Sun Nov 21, 2010 21:20    Post subject: Reply with quote
Masterman wrote:
Your new fixtables script with the INVALID state at the beginning of the INPUT chain still has me confused..

Before traffic enters the INPUT or FORWARD chain it will have a state.

When traffic enters the INPUT chain all RELATED and ESTABLISHED connections are accepted.
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT

This leaves us with NEW and INVALID connections.
INVALID connections are connections of which netfilter couldn't establish its state (RELATED,ESTABLISHED or NEW). We drop all of those INVALID connections
-A INPUT -m state --state INVALID -j logdrop

Which leaves us with the connections that are NEW and we don't know yet what we would should do with them.
These are the rest of the rules.....

If none of the excplicit rules are matched it will go to the last line and get DROPped with a LOG.
-A INPUT -j logdrop

_________________
Asus RT16N + OTRW
Kingston 4GB USB-disk 128 MB swap + 1.4GB ext3 on /opt + 2 GB ext3 on /mnt
Copperjet 1616 modem in ZipB-config
Asterisk, pixelserv & Pound running on router
Another Asus RT16N as WDS-bridge

DD-WRT v24-sp2 vpn (c) 2010 NewMedia-NET GmbH
Release: 12/16/10 (SVN revision: 15758M)
Masterman
DD-WRT Guru


Joined: 24 Aug 2009
Posts: 2070
Location: South Florida

PostPosted: Mon Nov 22, 2010 0:53    Post subject: Reply with quote
frater wrote:
Masterman wrote:
Your new fixtables script with the INVALID state at the beginning of the INPUT chain still has me confused..

Before traffic enters the INPUT or FORWARD chain it will have a state.

When traffic enters the INPUT chain all RELATED and ESTABLISHED connections are accepted.
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT

This leaves us with NEW and INVALID connections.
INVALID connections are connections of which netfilter couldn't establish its state (RELATED,ESTABLISHED or NEW). We drop all of those INVALID connections
-A INPUT -m state --state INVALID -j logdrop

Which leaves us with the connections that are NEW and we don't know yet what we would should do with them.
These are the rest of the rules.....

If none of the excplicit rules are matched it will go to the last line and get DROPped with a LOG.
-A INPUT -j logdrop


I now understand. Was wondering why my logs where "new" ;)

Code:
Nov 21 16:20:51 AsusTek authpriv.notice dropbear[9958]: pubkey auth succeeded for 'root' with key md5 xx:xx:xx:75:04:xx:cb:fa:c4:xx:7e:xx:5b:xx:xx:94 from 85.191.x.xxx:x860
Nov 21 16:24:54 AsusTek user.warn kernel: DROP IN=vlan2 OUT= MAC=00:26:18:85:25:ca:00:01:5c:24:73:41:08:00:45:00:00:28 SRC=74.122.180.181 DST=173.168.205.215 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=4356 DF PROTO=TCP SPT=80 DPT=53313 SEQ=3668158232 ACK=1244888570 WINDOW=99
Nov 21 16:24:55 AsusTek user.warn kernel: DROP IN=vlan2 OUT= MAC=00:26:18:85:25:ca:00:01:5c:24:73:41:08:00:45:00:00:28 SRC=74.122.180.181 DST=173.168.205.215 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=61403 DF PROTO=TCP SPT=80 DPT=53311 SEQ=1514505826 ACK=434290534 WINDOW=99
Nov 21 16:24:55 AsusTek user.warn kernel: DROP IN=vlan2 OUT= MAC=00:26:18:85:25:ca:00:01:5c:24:73:41:08:00:45:00:00:28 SRC=74.122.180.181 DST=173.168.205.215 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=27022 DF PROTO=TCP SPT=80 DPT=53309 SEQ=1904338755 ACK=2664420259 WINDOW=9
Nov 21 16:25:39 AsusTek user.warn kernel: DROP IN=vlan2 OUT= MAC=00:26:18:85:25:ca:00:01:5c:24:73:41:08:00:45:00:00:28 SRC=74.122.180.181 DST=173.168.205.215 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=42448 DF PROTO=TCP SPT=80 DPT=53324 SEQ=336900326 ACK=598625562 WINDOW=606
Nov 21 16:25:40 AsusTek user.warn kernel: DROP IN=vlan2 OUT= MAC=00:26:18:85:25:ca:00:01:5c:24:73:41:08:00:45:00:00:28 SRC=74.122.180.181 DST=173.168.205.215 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=50717 DF PROTO=TCP SPT=80 DPT=53325 SEQ=3655043047 ACK=4260329313 WINDOW=6
Nov 21 16:25:40 AsusTek user.warn kernel: DROP IN=vlan2 OUT= MAC=00:26:18:85:25:ca:00:01:5c:24:73:41:08:00:45:00:00:28 SRC=74.122.180.181 DST=173.168.205.215 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=28455 DF PROTO=TCP SPT=80 DPT=53326 SEQ=1481781317 ACK=113009172 WINDOW=60
Nov 21 16:25:55 AsusTek user.warn kernel: DROP IN=vlan2 OUT= MAC=00:26:18:85:25:ca:00:01:5c:24:73:41:08:00:45:00:05:54 SRC=68.142.123.254 DST=173.168.205.215 LEN=1364 TOS=0x00 PREC=0x00 TTL=56 ID=37946 DF PROTO=TCP SPT=80 DPT=52329 SEQ=2160611851 ACK=2075018798 WINDOW=
Nov 21 16:25:55 AsusTek user.warn kernel: DROP IN=vlan2 OUT= MAC=00:26:18:85:25:ca:00:01:5c:24:73:41:08:00:45:00:05:54 SRC=68.142.123.254 DST=173.168.205.215 LEN=1364 TOS=0x00 PREC=0x00 TTL=56 ID=37947 DF PROTO=TCP SPT=80 DPT=52329 SEQ=2160613175 ACK=2075018798 WINDOW=
Nov 21 16:25:55 AsusTek user.warn kernel: DROP IN=vlan2 OUT= MAC=00:26:18:85:25:ca:00:01:5c:24:73:41:08:00:45:00:05:54 SRC=68.142.123.254 DST=173.168.205.215 LEN=1364 TOS=0x00 PREC=0x00 TTL=56 ID=50203 DF PROTO=TCP SPT=80 DPT=52329 SEQ=2160885919 ACK=2075018798 WINDOW=
Nov 21 16:25:55 AsusTek user.warn kernel: DROP IN=vlan2 OUT= MAC=00:26:18:85:25:ca:00:01:5c:24:73:41:08:00:45:00:05:54 SRC=68.142.123.254 DST=173.168.205.215 LEN=1364 TOS=0x00 PREC=0x00 TTL=56 ID=59192 DF PROTO=TCP SPT=80 DPT=52329 SEQ=2161083195 ACK=2075018798 WINDOW=
Nov 21 16:25:55 AsusTek user.warn kernel: DROP IN=vlan2 OUT= MAC=00:26:18:85:25:ca:00:01:5c:24:73:41:08:00:45:00:05:54 SRC=68.142.123.254 DST=173.168.205.215 LEN=1364 TOS=0x00 PREC=0x00 TTL=56 ID=59193 DF PROTO=TCP SPT=80 DPT=52329 SEQ=2161084519 ACK=2075018798 WINDOW=
Nov 21 16:25:56 AsusTek user.warn kernel: DROP IN=vlan2 OUT= MAC=00:26:18:85:25:ca:00:01:5c:24:73:41:08:00:45:00:05:54 SRC=68.142.123.254 DST=173.168.205.215 LEN=1364 TOS=0x00 PREC=0x00 TTL=56 ID=4341 DF PROTO=TCP SPT=80 DPT=52329 SEQ=2161325487 ACK=2075018798 WINDOW=1
Nov 21 16:25:56 AsusTek user.warn kernel: DROP IN=vlan2 OUT= MAC=00:26:18:85:25:ca:00:01:5c:24:73:41:08:00:45:00:05:54 SRC=68.142.123.254 DST=173.168.205.215 LEN=1364 TOS=0x00 PREC=0x00 TTL=56 ID=15292 DF PROTO=TCP SPT=80 DPT=52329 SEQ=2161530707 ACK=2075018798 WINDOW=
Nov 21 16:25:56 AsusTek user.warn kernel: DROP IN=vlan2 OUT= MAC=00:26:18:85:25:ca:00:01:5c:24:73:41:08:00:45:00:05:54 SRC=68.142.123.254 DST=173.168.205.215 LEN=1364 TOS=0x00 PREC=0x00 TTL=56 ID=15293 DF PROTO=TCP SPT=80 DPT=52329 SEQ=2161532031 ACK=2075018798 WINDOW=
Nov 21 16:25:56 AsusTek user.warn kernel: DROP IN=vlan2 OUT= MAC=00:26:18:85:25:ca:00:01:5c:24:73:41:08:00:45:00:05:54 SRC=68.142.123.254 DST=173.168.205.215 LEN=1364 TOS=0x00 PREC=0x00 TTL=56 ID=26293 DF PROTO=TCP SPT=80 DPT=52329 SEQ=2161714743 ACK=2075018798 WINDOW=
Nov 21 16:28:27 AsusTek user.warn kernel: DROP IN=vlan2 OUT= MAC=00:26:18:85:25:ca:00:01:5c:24:73:41:08:00:45:00:00:28 SRC=74.122.180.181 DST=173.168.205.215 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=48211 DF PROTO=TCP SPT=80 DPT=53424 SEQ=2101238232 ACK=1788014355 WINDOW=6

_________________
Optware, the Right Way
Asus RT-AC68U
Asus RT-N66U
Asus RT-N10
Asus RT-N12
Asus RT-N16 x5
Asus WL520gU
Engenious ECB350
Linksys WRT600Nv1.1
Linksys WRT610Nv1
Linksys E2000
Netgear WNDR3300
SonicWall NSA220W
SonicWall TZ215W
SonicWall TZ205W
SonicWall TZ105W
cedriclille
DD-WRT Novice


Joined: 23 Jan 2008
Posts: 24

PostPosted: Mon Nov 22, 2010 9:38    Post subject: Reply with quote
@frater : Thank you, after reinstalling Optware, I now have S95worldblock.

So I put in S95worldblock :
ISO_spam=""
ISO_ham="fr"

And in S95asiablcok :
ISO_spam="af cn in pk my kh li vn kr ph"
ISO_ham="fr"

I don't really understand the difference between worldblock & asiablock. Why should I whitelist "fr" twice ???

@eko : I don't see asterisk reboot command anymore ? Do we need it or not ?

I like to whitelist one (or some) IP from Fring which allows us to use our 3G phone with asterisk (GSM providers block normal SIP protocol).

when I use the netstat (netstat -ena) command while call in progress I don't see any extenal address ...
Is there a way to see this remote IP address (Of course I did turn off all asiablock, wordblock and so one and the call was established for my test;) )...

And last question (for now) : where to whitelist this address, once I got the right ip.


Many thanks!!
frater
DD-WRT Guru


Joined: 07 Jun 2006
Posts: 2777

PostPosted: Mon Nov 22, 2010 17:58    Post subject: Reply with quote
cedriclille wrote:
I don't really understand the difference between worldblock & asiablock. Why should I whitelist "fr" twice ???

You don't

The worldblock is the opposite of asiablock.

With asiablock you can accept the world, but block specific countries / regions.
With worldblock you block the world and whitelist specific countries.

But there's more to asiablock than this simple explanation. Because blocking all these Asian countries would make a list of at least 3000 rules I needed some optimization.
I'm taking several huge /8 /7 and even /6 networkblocks and I block these. Only the Chinese, Indian... so on IP's that are not in this subnet will get a special rule.
This way I'm able to bring down the amount of rules to a bit more than 300.
To make sure that at least your own country is not in these blocked IP's you should put them in hamISO.

This approach has one big downside and that's our dear old Australian and New Zealand friends. These countries were given IP-blocks within these Asian countries. A shame really, because if you whitelist these countries the amount of rules will go up sky high....
I didn't take time to optimize this.


so you will have 2 chains you can use at will.
If you drive traffic down the 'asia' chain it will only come back if the IP is not coming from Asia.

If you drive traffice down the 'world' chain it will only come back if it's from France (in your case).

In /opt/etc/asia.spam you can add some extra IP's that otherwise would not be blocked.
In /opt/etc/asia.ham you can add some extra IP's that otherwise would be blocked.

The same goes for /opt/etc/world.ham and /opt/etc/world.spam.

So you probably don't need to add France as a whitelisted country in asiablock, but you need to run the script to see this. I know that there are some US IP's within those Asian-subnets.

BTW.... The approach I took is an original idea of mine. I took this as a base of that idea http://www.cyberciti.biz/faq/block-entier-country-using-iptables/, but there's more to it. It's bringing down the amount of rules which makes it usable.

_________________
Asus RT16N + OTRW
Kingston 4GB USB-disk 128 MB swap + 1.4GB ext3 on /opt + 2 GB ext3 on /mnt
Copperjet 1616 modem in ZipB-config
Asterisk, pixelserv & Pound running on router
Another Asus RT16N as WDS-bridge

DD-WRT v24-sp2 vpn (c) 2010 NewMedia-NET GmbH
Release: 12/16/10 (SVN revision: 15758M)
Masterman
DD-WRT Guru


Joined: 24 Aug 2009
Posts: 2070
Location: South Florida

PostPosted: Mon Nov 22, 2010 19:56    Post subject: Reply with quote
frater, check your PM's. I think fixtables may have a problem with my current rc_firewall. I can't reach you via Skype for some reason either..
_________________
Optware, the Right Way
Asus RT-AC68U
Asus RT-N66U
Asus RT-N10
Asus RT-N12
Asus RT-N16 x5
Asus WL520gU
Engenious ECB350
Linksys WRT600Nv1.1
Linksys WRT610Nv1
Linksys E2000
Netgear WNDR3300
SonicWall NSA220W
SonicWall TZ215W
SonicWall TZ205W
SonicWall TZ105W
cedriclille
DD-WRT Novice


Joined: 23 Jan 2008
Posts: 24

PostPosted: Wed Nov 24, 2010 10:18    Post subject: Reply with quote
@frater : Thank you, I can see clearly now and I undesertand that we can make fine tuning now !

Once again, thank you for your grat job!

You didn't answer : Do we still have to reload Asterisk after applying the rc_firewall rules?

And as I know there are some Asterisk users her : I have a strange heavy CPU usage (100%) only for INCOMING calls from a particular SIP provider :
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=43787&postdays=0&postorder=asc&start=180

Thank you
frater
DD-WRT Guru


Joined: 07 Jun 2006
Posts: 2777

PostPosted: Wed Nov 24, 2010 16:55    Post subject: Reply with quote
cedriclille wrote:
You didn't answer : Do we still have to reload Asterisk after applying the rc_firewall rules?

No

_________________
Asus RT16N + OTRW
Kingston 4GB USB-disk 128 MB swap + 1.4GB ext3 on /opt + 2 GB ext3 on /mnt
Copperjet 1616 modem in ZipB-config
Asterisk, pixelserv & Pound running on router
Another Asus RT16N as WDS-bridge

DD-WRT v24-sp2 vpn (c) 2010 NewMedia-NET GmbH
Release: 12/16/10 (SVN revision: 15758M)
cedriclille
DD-WRT Novice


Joined: 23 Jan 2008
Posts: 24

PostPosted: Fri Dec 03, 2010 16:26    Post subject: Reply with quote
@ frater : thanks !

Everything is set up the way you told me.

I'm going to test and report if something is wrong.

I made a first test and Fring was blocked (unable to login to asterisk). With the passthrough (ip in asia.ham) it was ok : so all seem to work fine :)

Can we put an IP range in asia.ham ?? Fring doesn't always have the same ip ... ?


Last edited by cedriclille on Sat Dec 04, 2010 11:29; edited 1 time in total
frater
DD-WRT Guru


Joined: 07 Jun 2006
Posts: 2777

PostPosted: Sat Dec 04, 2010 11:03    Post subject: Re: mobile phones Reply with quote
tong123 wrote:
[网址能源橡胶手镯[/网址]
所以这是非常受欢迎的,因为它是引入用户。

So you installed asiablock and none of your websites work? Laughing

_________________
Asus RT16N + OTRW
Kingston 4GB USB-disk 128 MB swap + 1.4GB ext3 on /opt + 2 GB ext3 on /mnt
Copperjet 1616 modem in ZipB-config
Asterisk, pixelserv & Pound running on router
Another Asus RT16N as WDS-bridge

DD-WRT v24-sp2 vpn (c) 2010 NewMedia-NET GmbH
Release: 12/16/10 (SVN revision: 15758M)
routvol
DD-WRT User


Joined: 02 Feb 2009
Posts: 87

PostPosted: Sun Dec 26, 2010 19:09    Post subject: Reply with quote
hi there

i am not sure but does asiablock/worldblock also work for network devices other than dd-wrt??

my setup is as follows:
internet <-> dd-wrt router <-> dns323 nas

i am currently running a ftp/ssh service on the nas with port forwarding from dd-wrt.
i want to block the world from using/abusing the ftp/ssh.

is this possible? do i need to install worldblock to the nas device as well (as to add iptable configuration, ..)?
does worldblock usually only work on the system where it is installed?

thx
cheers
frater
DD-WRT Guru


Joined: 07 Jun 2006
Posts: 2777

PostPosted: Sun Dec 26, 2010 21:36    Post subject: Reply with quote
Because DD-WRT is your router, all traffic will go through your DD-WRT.

asiablock & worldblock's use is flexible. If you don't add something in the FORWARD or INPUT chain, it will not do anything.

The INPUT chain is for protecting services on DD-WRT. The FORWARD-chain is for protecting services on your LAN.

If you want to protect SSH & FTP on your NAS you need to add this line to rc_firewall

Code:
wanf=`get_wanface`
iptables -I FORWARD 1 -i $wanf -p tcp --dport 20:23 -j world


If you translate ports like 2222 to 22, you still need to use 22 in that line. 'dport' means 'destination port' and the destination is your LAN-device.

_________________
Asus RT16N + OTRW
Kingston 4GB USB-disk 128 MB swap + 1.4GB ext3 on /opt + 2 GB ext3 on /mnt
Copperjet 1616 modem in ZipB-config
Asterisk, pixelserv & Pound running on router
Another Asus RT16N as WDS-bridge

DD-WRT v24-sp2 vpn (c) 2010 NewMedia-NET GmbH
Release: 12/16/10 (SVN revision: 15758M)
Goto page Previous  1, 2, 3 ... 13, 14, 15, 16  Next Display posts from previous:    Page 14 of 16
Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum