scaryAardvark wrote:I'm keen to understand the exact changes you've made and the exact config you are using. Would you be kind enough to summarise the changes you had to make either to the source code in trunk or to the configuration on the router itself either via the web interface or config files/scripts.
The thing is that each ISP has different settings.
I'll try and run you through a checklist so we can narrow down the problem.
1. I assume that you have an ADSL line not ISDN. (Let me know if otherwise). If so, we have to make sure you have the dsl modules installed with the correct firmware. Type in:
opkg list-installed | grep dsl
You should get
kmod-ltq-dsl-ar9 - 3.2.13+3.24.4.4-3
kmod-ltq-dsl-firmware-a-ar9 - 3.24.4.4-3
ltq-dsl-app - 3.24.4.4-1
Make sure it is kmod-ltq-dsl-firmware-a-ar9 not kmod-ltq-dsl-firmware-b-ar9. B is for isdn lines.
2. Even if you have the 'a' firmware it still tries to use 'b' firmware. This is a bug ( https://dev.openwrt.org/ticket/11240 ), I think. So you have to change the network config file.
There are two ways to do this.
2.a. Either edit the /etc/config/network file directly using an editor. Change
config adsl-device 'adsl'
option fwannex 'b'
option annex 'b2p'
config adsl-device 'adsl'
option fwannex 'a'
option annex 'a2p'
2.b. Or use uci
uci set network.adsl.fwannex=a
uci set network.adsl.annex=a2p
uci commit network
Then reboot the rooter with
(SOMEONE PLEASE CHECK MY UCI INSTRUCTIONS, I've never really used uci properly.)
3. We now need to check that the ADSL modem is syncing with you ADSL line. It's easiest to create a script to do this. Run:
To create the file. Copy and paste the following script (the whole thing, not line-by-line).
#!/bin/sh
echo "$@" > /tmp/pipe/dsl_cpe0_cmd && cat /tmp/pipe/dsl_cpe0_ack
(credits go to eselle)
Hit enter, then ctrl-c to save the script.
Then make the script runnable:
Now we can run the script to query the modem for the line status information. Run:
This gets the downstream line information. You should see something like
nReturn=0 nChannel=0 nDirection=1 ActualDataRate=5106150 PreviousDataRate=0 ActualInterleaveDelay=800 ActualImpulseNoiseProtection=20
If you only see nReturn with a negative number, it means there is a problem.
4. Hopefully your ADSL line is up. New we need configure the way the router sends data over the line. This is entirely dependent on your ISP. Let us know which ISP + package you have and someone will try and help you. Or you can try entering the settings yourself.
Lastly, I also saw:
scaryAardvark wrote:When I initially put my changes in I noticed that I had a "ppp" process running which looked like it had the configuration on the command line however after making a few more changes to try and get it working I can't see this process running at all, even after a reboot.
In the likely event that your ISP uses PPPoE or PPPoA, then yes, I think that this may be a problem as you need pppd to handle the ppp link. There was a thread about about pppd not running on boot https://forum.openwrt.org/viewtopic.php?id=34132 .
However, this was fixed several months ago, and by the looks of you other posts you compiled openwrt in the last two weeks, so this should not be a problem.
I can't say to much on pppd as I don't use it myself, but I think it is first best to establish whether you ADSL connection needs it or not. The best was to do this is to find out your ISP + package to get you connection type.
However, I do remember trying both settings then booting up my old router and checking it's config. Thats how I knew it was VCMUX.