Wireless Router Default Settings [Login & Password]

Often times we buy new routers and shy away from reading the manuals. Even when read for the first, the manuals get lost and when the reset button is accidentally pushed, the search for the router default settings (login & password) becomes very difficult. I thought it will be helpful to write down some of these information here. There are lots of routers on the market but I am only listing the ones I have personally worked with. I’ll be adding to the list as more router settings are discovered.

 
Brand Name Model Router default URL Login Name Password
 3Com http://192.168.1.1 admin admin
 D-Link 713P http://192.168.0.1 admin <blank>
 Linksys WRT54AG, WAP54G http://192.168.1.1 <blank> admin
 Linksys WRT54G, WRT54GS,
WRT54GL, WRV54G
http://192.168.1.1 admin admin
 Netgear http://192.168.0.1 admin password
 TP-Link http://192.168.1.1 admin admin
 US Robotic http://192.168.123.254 admin admin
 US Robotic http://192.168.123.254 admin <blank>
 US Robotic http://192.168.123.254 root 12345
 US Robotic http://192.168.123.254 <blank> 12345

 

I hope this helps someone 😉


Posted in DD-WRT, LinkSys, Networking, WRT54GLv1.1 and tagged , , , , by with comments disabled.

Running Two Instances of OpenVPN on Two Seperate Ports 1194 (UDP) & 443 (TCP)

First and foremost, it has to be stated that I am not the author of the original article on this topic. The original article can be found here.

Now, why repeat the same thing here?

Well, on June 10th, 2009, I wrote a reply on this post while in search of a solution for exactly the same purpose as RickNY (The original Author). Back then, I was able to setup my OpenVPN with the help found on various forums. For some reason, I had to change my configurations… which required a different setup. Stupid enough, I made no backup or maybe I did but couldn’t find one, when I needed exactly the same configuration again.

Knowing fully well that I was part of such a discussion before somewhere, I had to google for sometime before I was able to find the the above address again. This time I knew I had to write a backup on my blog.

If you’re seeing this for the first time, just go ahead and try it. I hope it solves your problem. If you’ve seen this somewhere before, please forgive me for the repetition 😉

Enough of the explanation…!

Why two instances of OpenVPN?

First of all, I have a full-time and part-time Job as a system engineer. In both of my offices, I always have to go through proxies to browse the internet.

Secondly, I have a small private business that requires my attention as well. To achieve this goals, I need to be able to channel my private activities securely through the proxies no matter the protocol been used.

The best solution would be to run double instances of OpenVPN on my private office gateway.

Requirements:

1.) A compatible router running DD-WRT v24-sp2 (I have WRT54GL v1.1)

2.)
LAN Network: 192.168.1.0
VPN Network: 10.32.71.0 (TCP) & 10.71.71.0 (UDP)
Setup keys, etc…

*) Lots of Coffee, Beer, Cigarettes and whatever might cool your temper when something goes wrong.

STEP 1

In GUI on the router, setup OpenVPN Daemon:
 
port 443
proto tcp-server
dev tun0
cipher AES-256-CBC
comp-lzo
dh /tmp/openvpn/dh.pem
ca /tmp/openvpn/ca.crt
cert /tmp/openvpn/cert.pem
key /tmp/openvpn/key.pem
tls-auth /tmp/openvpn/ta.key 0
server 10.32.71.0 255.255.255.0
client-to-client
keepalive 10 120
push “route 192.168.1.0 255.255.255.0”
push “redirect-gateway”
push “dhcp-option DNS 208.67.222.222”
push “dhcp-option DNS 208.67.220.220”
persist-key
persist-tun
verb 5

STEP 2:

Create the first of two configuration files for the client on your windows PC (I never tried this on any other OS).

Let’s call this file “Client1-tcp.ovpn

remote my.openvpn-server.address.com 443
client
proto tcp-client
dev tun0
comp-lzo
resolv-retry infinite
nobind
float
persist-key
persist-tun
ns-cert-type server
verb 3
cipher AES-256-CBC
ca ca.crt
cert client1.crt
key client1.key
tls-auth ta.key 1
ping 10
ping-restart 60
pull

STEP 3:

To limit debugging to either client1-tcp.ovpn or client2-udp.ovpn, I advice testing the connections with client1-tcp.ovpn before continuing…

If successfull, go ahead and create the second client file. Otherwise debug client1-tcp.ovpn first.

Likewise, we have to name this file “Client2-udp.ovpn

remote my.openvpn-server.address 1194
client

proto udp
dev tun0
comp-lzo
resolv-retry infinite
nobind
float
persist-key
persist-tun
ns-cert-type server
verb 3
cipher AES-256-CBC
ca ca.crt
cert client1.crt
key client1.key
tls-auth ta.key 1
ping 10
ping-restart 60
pull

STEP 4:

Entered the following in the “Startup” command window to create the 2nd instance..

Yo may need to adjust the sleep commands to account for the openvpn directory to be created and populated with my keys from the GUI..:

================== Begin Startup =====================

# Move to writable directory and create scripts
cd /tmp
ln -s /usr/sbin/openvpn /tmp/openvpn-udp

# Config
echo “
proto udp
port 1194
dev tun1
cipher AES-256-CBC
comp-lzo
dh /tmp/openvpn/dh.pem
ca /tmp/openvpn/ca.crt
cert /tmp/openvpn/cert.pem
key /tmp/openvpn/key.pem
tls-auth /tmp/openvpn/ta.key 0
server 10.71.71.0 255.255.255.0
client-to-client
keepalive 10 120
push “route 192.168.1.0 255.255.255.0″
push “redirect-gateway”
push “dhcp-option DNS 208.67.222.222″
push “dhcp-option DNS 208.67.220.220″
persist-key
persist-tun
verb 5
daemon
” > openvpn-udp.conf

# Create interfaces
/tmp/myvpn –mktun –dev tun1

# Initiate the tunnel
sleep 5
/tmp/openvpn-udp –daemon –config openvpn-udp.conf

# TCP OpenVPN Startup
sleep 15
cd /tmp/openvpn/
openvpn –daemon –config openvpn.conf

=================== End Startup ======================

One more step to go…

STEP 5:

Entered the following in the “Firewall” command window to create the iptables for your openvpn-server

================= Start Firewall =================

iptables -I INPUT -p tcp –dport 443 -j ACCEPT

iptables -I INPUT -p udp –dport 1194 -j ACCEPT

iptables -I FORWARD -i br0 -o tun0 -j ACCEPT

iptables -I FORWARD -i tun0 -o br0 -j ACCEPT

iptables -I FORWARD 1 –source 10.32.71.0/24 -j ACCEPT

iptables -I FORWARD 1 –source 10.71.71.0/24 -j ACCEPT

ip neigh change 192.168.1.254 lladdr ff:ff:ff:ff:ff:ff nud permanent dev br0

ip neigh add 192.168.1.254 lladdr ff:ff:ff:ff:ff:ff nud permanent dev br0

================== End Firewall ==================

The two last lines on the firewall configuration are optional.

These two lines allows you to wake up devices on your network remotely.

Note:

If you use Windows 7 and above, remember to start your OpenVPN GUI with elevated access (just enable “Run as Administrator“).

Otherwise, all traffic won’t be redirected through your network gateway. This is a common problem with this kind of configuration.

That’s it! I hope it helps someone like me…

Hey! no matter the amount of bugs you might get… don’t blame me. Everything in life is risk 😉
Remember Tom Jones? The very best in life is always free!!! Enjoy!


Posted in DD-WRT, LinkSys, Networking, WRT54GLv1.1 and tagged , , , , , by with 1 comment.