{"id":104,"date":"2008-10-09T23:38:42","date_gmt":"2008-10-09T21:38:42","guid":{"rendered":"http:\/\/www.evilgenius.de\/?p=104"},"modified":"2018-07-02T18:28:01","modified_gmt":"2018-07-02T16:28:01","slug":"configuring-your-dsl-modem-through-your-router","status":"publish","type":"post","link":"https:\/\/www.evilgenius.de\/?p=104","title":{"rendered":"Configuring your DSL modem through your router"},"content":{"rendered":"

I unplugged my modem last week before I went to Dortmund for some days and plugged it back in last Sunday when I came back. Since then my DSL broadband access is pretty slow. Like 1 Mbit\/s downstream, should be around 16 Mbit\/s. Therefore I messed a little bit around with my configuration and found out that my DSL Modem – Siemens C2-010-I<\/em>, is actually Viking II Plus<\/a> and not a modem but a moden\/router\/bridge. My provider configured the Viking as a bridge, therefore it looked like a usual DSL modem.<\/p>\n

<\/p>\n

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

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.<\/p>\n


\nmartin@kovalski:~$ telnet 192.168.1.1
\nTrying 192.168.1.1...
\nConnected to 192.168.1.1.
\nEscape character is '^]'.<\/p>\n

******************
\n Welcome
\n ******************<\/p>\n

Software Release R100B01.0B_HN_20060406
\nCopyright (c) 2001-2004<\/p>\n

login: alice@13184
\npassword:
\nLogin Successful
\n$help
\nCommand Description
\n------- -----------
\nalias To Alias a command
\napply Apply configuration\/image file
\ncommit Commit the active config to the flash
\ncreate Create a new entry of specified type
\ndelete Delete the specified entry
\ndownload Download a file on to the Device
\nexit To exit the CLI shell
\nget Display info for the search
\nhelp Provides help
\nlist List files
\nmodify Modify information for specified entry
\npasswd To modify user password
\nping The normal ping command
\nprompt Change the user prompt
\nreboot Reboot the device
\nremove Remove file
\nreset Reset info for the specified entry
\nsize ATM Sizing Information
\ntraceroute The normal traceroute command
\ntrigger To set trigger
\nunalias To undefine previously defined alias
\nverbose Switch ON\/OFF the verbose mode
\n$get dsl stats curr<\/p>\n

No. of 15 Min. Valid Data Intervals : 6
\nNo. of 15 Min. Invalid Data Intervals : 0
\nCurrent 15 Min. Elapsed Time (MM:SS) : 6:56
\nCurrent 15 Min. Errored Seconds : 0
\nCurrent 15 Min. Sev Errored Seconds : 0
\nCurrent 15 Min. Unavailable Seconds : 0
\nCurrent Day Elapsed Time (HH:MM:SS) : 1:51:56
\nCurrent Day Errored Seconds : 0
\nCurrent Day Sev Errored Seconds : 0
\nCurrent Day Unavailable Seconds : 38
\nPrevious Day Monitored Time (HH:MM:SS) : 0:0:0
\nPrevious Day Errored Seconds : 0
\nPrevious Day Sev Errored Seconds : 0
\nPrevious Day Unavailable Seconds : 0
\n$get dsl params<\/p>\n

Vendor ID : 0039
\nRevision Number : E.37.2.8
\nSerial number : 123456789abcdx
\nSelf Test : Passed Framing Structure : Unknown
\nStandard : ADSL2\/2+ Trellis Coding : -
\nLocal Tx. Power(dB) : 12.6 Remote Tx.Power(dB) : 0.0
\nLocal Line Atten(dB) : 18.5 Remote Line Atten(dB) : 11.5
\nLocal SNR Margin(dB) : 12.5 Remote SNR Margin(dB) : 6.5
\nTx Line Rate(kbps) : 0 Rx Line Rate(kbps) : 0
\nUp SValue : - Down SValue : -
\nUp DValue : - Down DValue : -
\nData Boost : - Max Att. DnS LR(kbps) : 0 <\/p>\n

UpIntrlvd UpFast DownIntrlvd DownFast
\nAS0(kbps): - - - -
\nAS1(kbps): - - - -
\nLS0(kbps): - - - -
\nLS1(kbps): - - - -
\nRValue : - - - -
\n$
\n<\/code><\/p>\n

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

…. 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.<\/p>\n

… 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<\/code> and the modem to stay as 192.168.1.1\/24<\/code>.<\/p>\n

Now, the adjustment of the router’s firewall:<\/p>\n


\nmartin@kovalski:~$ ssh root@192.168.2.1
\nroot@192.168.2.1's password: <\/p>\n

BusyBox v1.4.2 (2008-10-01 22:05:02 CEST) Built-in shell (ash)
\nEnter 'help' for a list of built-in commands.<\/p>\n

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

First configure your WAN interface. Then the firewall: The first rule is to masquerade the traffic from 192.168.2.0\/24<\/code> as 192.168.1.2<\/code>. The modem\/router does not know anything about the 192.168.2.0\/24<\/code> network. It will receive the requests out of the network but does not know where to send them back.
\nThe 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).<\/p>\n

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<\/a>. There are several versions of this tool for different modems, but basically they all seem to use telnet to gather the informations.<\/p>\n

By the way, the user name and password for accessing my modem were:
\nUser: alice@13184<\/code> password: hnto$mgmt@lice<\/code>
\nThis is the default configuration of my broadband provider Alice<\/a>.<\/p>\n

kthxbye.<\/p>\n","protected":false},"excerpt":{"rendered":"

I unplugged my modem last week before I went to Dortmund for some days and plugged it back in last Sunday when I came back. Since then my DSL broadband access is pretty slow. Like 1 Mbit\/s downstream, should be around 16 Mbit\/s. Therefore I messed a little bit around with my configuration and found … Continue reading Configuring your DSL modem through your router<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10,16],"tags":[],"class_list":["post-104","post","type-post","status-publish","format-standard","hentry","category-hacking","category-kthxbye"],"_links":{"self":[{"href":"https:\/\/www.evilgenius.de\/index.php?rest_route=\/wp\/v2\/posts\/104","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.evilgenius.de\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.evilgenius.de\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.evilgenius.de\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.evilgenius.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=104"}],"version-history":[{"count":8,"href":"https:\/\/www.evilgenius.de\/index.php?rest_route=\/wp\/v2\/posts\/104\/revisions"}],"predecessor-version":[{"id":238,"href":"https:\/\/www.evilgenius.de\/index.php?rest_route=\/wp\/v2\/posts\/104\/revisions\/238"}],"wp:attachment":[{"href":"https:\/\/www.evilgenius.de\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=104"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.evilgenius.de\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=104"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.evilgenius.de\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=104"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}