Posted: Sun Aug 03, 2014 19:39 Post subject: WBMR-HP-G300H-EU to Annex B
Hello,
I have recently bought a WBMR-HP-G300H-EU (i.e. Annex A) modem, not noticing that my ISP uses the Annex B standard. I happily flashed DD-WRT on it, after reading that someone succeeded to do the converse (turn a -DE model into an Annex A). However, even with DD-WRT it fails to connect.
My ADSL settings are PPPoE, VPI/VCI=8/48, LLC, routed. The connection is officially ADSL2+ Annex B, the old modem identifies the connection as "G.dmt.bisplus"
The symptoms are that the WBRM detect the line capacities (upload/download speed, SNR, attenuation), but during all this the DSL LED stays off. There are some sporadic cases, when after a cold boot it flashes for a fraction of second. In fact twice it even got its time synced, I assume it was from the NTP server I entered. (At that time I didn't have the remote syslog enabled, so I don't know what happened exactly).
I enabled remote logging to diagnose the problem further, but I see nothing informative there. The only lines containing "dsl" are the these:
Code:
Jan 1 00:00:08 dd-wrt kernel: [ 6.590000] Infineon CPE API Driver version: DSL CPE API V3.24.4.4
Jan 1 00:00:29 dd-wrt kernel: [ 40.560000] [DSL_BSP_Showtime 916]: Datarate US intl = 0, fast = 544000
So I figured that it must be the PPPoE part that's failing. With "ppp" I have
Code:
Jan 1 00:00:08 10.0.0.138 kernel: [ 0.620000] PPP generic driver version 2.4.2
Jan 1 00:00:08 10.0.0.138 kernel: [ 0.620000] PPP BSD Compression module registered
Jan 1 00:00:08 10.0.0.138 kernel: [ 0.630000] PPP Deflate Compression module registered
Jan 1 00:00:08 10.0.0.138 kernel: [ 0.630000] PPP MPPE Compression module registered
Jan 1 00:00:09 10.0.0.138 syslog: ppp_redial : redial process successfully started
Jan 1 00:38:13 10.0.0.138 syslog: ppp_redial : redial process successfully started
Jan 1 00:00:09 dd-wrt syslog: ppp_redial : redial process successfully started
i.e. no messages from pppoe.
Other relevant messages appear to be:
Code:
Jan 1 00:05:30 10.0.0.138 syslog: br2684ctl : ATM: DSL Modem interface removed hanging, send SIGKILL
Jan 1 00:05:30 10.0.0.138 br2684ctl[4672]: Interface "nas0" created sucessfully
Jan 1 00:05:30 10.0.0.138 br2684ctl[4672]: Communicating over ATM 0.8.48, encapsulation: LLC
Jan 1 00:05:30 10.0.0.138 br2684ctl[4672]: Interface configured
Jan 1 00:05:30 10.0.0.138 syslog: ATM : DSL Modem interface created
Jan 1 00:05:30 10.0.0.138 br2684ctl[4680]: RFC 1483/2684 bridge daemon started
I'm quite stuck here. I have tried the following V24-preSP2 builds, and none of them worked: r21676, r21061, r24461
The following specific questions come into my mind:
1) Is really the firmware the only difference between the -EU and the -DE models?
2) What should I be seeing in the log while the DSL connection is being made?
3) Is there any way to increase verbosity in DD-WRT? I'd like to know if PPPoE is started at all, and if so, what happens to it.
What else should I try? I can send more logs if that would be useful.
I also have the same router, it is flashed with 24461.
If you go to Setup tab on web interface, PPPoE has "Advanced settings" check box. It offers Annex B among the others.
My ISP also requires username and password to succesfully connect. Google your ISP requirements for PPPoE _________________ Asus RT-AC66R Target:brcm47xx SubTarget:mips74k Packages:mipsel_74kc
Netgear R7000 Target:bcm53xx Packages:arm_cortex-a9
Thanks hanksloss for replying. I have double checked all DSL line and PPPoE settings with my ISP's support, and they seem to be correct.
I have tried all Annex B options from the advanced menu, but they all produce the same result. (With the Annex A option my line does not get detected at all, so the modem must be doing something when Annex B is selected).
Do you own a WBMR-HP-G300H-EU or a WBMR-HP-G300H-DE model? The former is sold as an Annex A, the latter as an Annex B model. Mine does not have this information printed neither on the device nor the box but on a sticker attached on the side of the box. (However, Buffalo support could tell me which one I had from the serial number.)
Actually, with the 24461 firmware I had some issues, e.g. ssh refused connections. With the other firmwares (r21676, r21061) I didn't have these problems. Is ssh working for you?
Hi
My model is just WBMR-HP-G300H. No other suffix is present on the box or label except "annex A" on technical summary.
My annex firmware is loaded from /usr/lib/firmware and both are present within dd-wrt image. I have the same behavior with DSL LED. It just flashing at first and never turns on.
I watched my interfaces. nas0 is created when DSL capabilities are detected, after successful PPPoE dialing another interface shows up, ppp0 (with an external IP address)
In my search for debug options, I used killall -9 to terminate couple of them and then started them manually:
Code:
root@WRTG300H:~# br2684ctl -v
br2684ctl: invalid option -- v
usage: br2684ctl [-b] [[-c number] [-e 0|1] [-s sndbuf] [-q qos] [-p 0|1] [-a [itf.]vpi.vci]*]*
-b = run in background (daemonize)
-c <num> = use interface nas<num>
-e 0|1 = encapsulation (0=LLC, 1=VC Mux)
-p 0|1 = payload type (0=routed,1=bridged)
-s <num> = set sndbuf (send buffer) size (default 8192)
-a [itf.]vpi.vci = ATM interface no, VPI, VCI
For pppd - debug, dump, kdebug 2 or 4 might produce some useful info
Hope it helps little bit. _________________ Asus RT-AC66R Target:brcm47xx SubTarget:mips74k Packages:mipsel_74kc
Netgear R7000 Target:bcm53xx Packages:arm_cortex-a9
Hi thanks for the info. It seems we indeed have the same modem -- it seems the -EU or -DE suffix is not printed in the device case. This gave me hope that the HW inside was the same and it'll be just a matter of flashing with the correct FW.
However, you seem to be using the device in an Annex A environment, am I right? I was hoping to find someone out there with experience on using the Annex A sold modem for Annex B.
In any case I am going to try starting things from the command line as you suggested. Actually I don't have and pppd processes: according to the log messages it gets started and then killed, so I never could see with what parameters it was started or even what binary it was. You ps list may prove very helful in this. Unfortunately this week I'm travelling, so I can try these only next week.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Tue Aug 05, 2014 7:24 Post subject:
try 23919, i know 24461 has wifi channel issues with ht40 & other random issues(theres an upper/lower bug that was later fixed) _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
