Basically you just have to configure your interface on your PC to have the IP-Address 192.168.1.2 (or any other address within 192.168.1.0/24) and then you either can access the Viking’s HTTP or telnet server via 192.168.1.1.

With the web interface running on the HTTP server you can configure basic things like switching your bridging modem into a router. The basic configurations options you have for every DSL router. Anyway more interesting is the telnet interface. With the help of it you can get many more informations about your DSL connection. I found a preliminary command reference for the Viking chip set family which seems to contains many commands you can use to get some more informations out of your modem/router/bridge.


martin@kovalski:~$ telnet 192.168.1.1
Trying 192.168.1.1...
Connected to 192.168.1.1.
Escape character is '^]'.

UpIntrlvd UpFast DownIntrlvd DownFast
AS0(kbps): - - - -
AS1(kbps): - - - -
LS0(kbps): - - - -
LS1(kbps): - - - -
RValue : - - - -
$


Anyway… now that you are able to get some informations out of your DSL modem/router. I actually like my OpenWrt based router…. damn…

…. writing this I just realized that this whole problem might not be related to my broadband provide – you remember, I just wanted to figure out why my connection was so slow before I tried to mess around with my modem – but to the not configured QOS settings of my so beloved OpenWrt router. Before I went to Dortmund my router got a little software update. Check, confirmed. QOS disabled.

… now that I have my whole bandwidth back… what was the point… right: I love my OpenWrt router. So I like to keep the bridge configuration but want to be able to access the DSL modem/router/bridge from within my local network behind my OpenWrt router. Therefore I have to adjust the firewall configuration a little. First make sure, that your modem and your router are not in the same subnet. I decided to configure my router to be 192.168.2.1/24 and the modem to stay as 192.168.1.1/24.

Now, the adjustment of the router’s firewall:


martin@kovalski:~$ ssh root@192.168.2.1
root@192.168.2.1's password:

_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
KAMIKAZE (7.09) -----------------------------------
* 10 oz Vodka Shake well with ice and strain
* 10 oz Triple sec mixture into 10 shot glasses.
* 10 oz lime juice Salute!
---------------------------------------------------
root@SRB178:~# ifconfig eth0.1 192.168.1.2 up
root@SRB178:~# iptables -t nat -A postrouting_rule -o eth0.1 -d 192.168.1.1/24 -j MASQUERADE
root@SRB178:~# iptables -A forwarding_rule -i br-lan -o eth0.1 -p tcp --dport 80 -d 192.168.1.1 -j ACCEPT
root@SRB178:~# iptables -A forwarding_rule -i br-lan -o eth0.1 -p tcp --dport 23 -d 192.168.1.1 -j ACCEPT


First configure your WAN interface. Then the firewall: The first rule is to masquerade the traffic from 192.168.2.0/24 as 192.168.1.2. The modem/router does not know anything about the 192.168.2.0/24 network. It will receive the requests out of the network but does not know where to send them back.
The other two rules are to allow the forwarding of traffic from the internal network to the modem/router on port 80 (http) and 23 (telnet).

If you want to get the informations easier than manually telnet into the modem and send the commands you can also use the fancy DSL-Modem Tool. There are several versions of this tool for different modems, but basically they all seem to use telnet to gather the informations.

By the way, the user name and password for accessing my modem were:
User: alice@13184 password: hnto$mgmt@lice
This is the default configuration of my broadband provider Alice.

kthxbye.