Skip to main content

WZR-HP-G300NH, OpenWRT & Huawei E160E

Finally, the latest release of OpenWRT 10.03 (codenamed BackFire) is out and it supports the WZR-HP-G300NH. Didn't take long until your truly take a plunge and flash his router with this latest firmware. Actually, the firmware supported the router since it's development release but since I'm not really into testing beta stuff, I've been patiently waiting for it to be available.. officially that it.

What the first thing I tried to do .. ? You guess it right, if you've followed my blog before .. trying to get APRS4R running on it but excitement overcomes the most basic thing I should do .. yes, RTFM .. APRS4R doesn't have support for other than mipsel and x86. So, what should I do with this mega router (64MB RAM with over 65% left after all the basic stuff loaded and over 32MB flash with over 90% empty)? One thing for sure, from my last week experience, where screamyx was so damn slow due to some international link was brought down for maintenance .. yes, a backup 3G broadband and I want this to be available without tinkering with my network setup everytime this thing happens. So, after thinking for few days .. and saw somebody wanted to let go his 3G USB dongle (Huawei E160E) for RM120, didn't think that long and my wallet had flattened a bit..

What do I need to get this E160E running? Tried it many times, loading kmod-usb-ohci and kmod-usb-uhci alongside the requirement to get USB working on Linux but no go.. just to realise that this router has USB2 .. so .. added kmod-usb2 got it going.. the E160E was recognised only after I added the following line into /etc/modules.d/60-usb-serial:

usbserial vendor=0x12d1 product=0x1003 maxSize=4096

What else needed, as per the documentation, comgt is required too, this has script to do the call-out for the 3G.

And for anyone wanted to do the same thing, the following guide is really helpful (at least for me and many others) in getting things going:


Popular posts from this blog

Raspberry Pi + svxlink = Low power echolink node

What is the easiest way to get echolink node up and running on raspberry pi? Surely, get a premade image which has everything inside. I've created one image which can fit into 2GB SD card for this, just follow the following steps to get it up and running:

For hardware, you need to have the following:
Raspberry Pi for sure, with a minimum 4GB SD cardA USB echolink interface, can be commercially sourced or DIY. There are many DIY schematics out there that you could follow.  Here is the configuration on how to get the things working together, courtesy of website:

For software:
Download the following prepared image from google drive, it is based on raspbian-2015-02-16 image and has pre-installed svxlink-14.08. raspi-wheezy-svxlink.img.zipUnzip the file and copy it to your SD card using the following instructions that can be found here.Boot up the RasPi, if you do not have an HDMI monitor, you may want to access the RasPi from your terminal emulator (putty or the like), connec…

Configuring TechniColor TG784N V3 (Maxis issued broadband router) to use different DNS servers

Previous write up deleted. It seems to change the DNS servers in as shown on the status, but it does not really work.

Check the following website, this seems to work:

This can be done from the WEB GUI too, go into the following configuration path:

In my example above, I'm using paid service unblock-us instead of google public DNS servers.

Debugging DMEE

I've come across many posting on the Internet (via google search), people asking on how to debug a DMEE for payment program. One of the few suggestion was to create a user exit just before the node that we would like to debug and put our breakpoint there. It seems that SAP has built-in this feature without needing us to create a user exit (available in ECC 6, have no idea if this is available on prior releases). Here is how you can put your breakpoint without any coding.

1. Display your DMEE tree using transaction: DMEE_DEBUG.

2. Click on the node that you would like to debug.
3. Go to conditions tab, you could see the Set Breakpoint button. Click to set.

4. Run the SAPFPAYM and specified the payment run date/id, payment format etc. SAP will stop at the node which you point your breakpoint at, as in 2.
5. To remove your breakpoint, just run the DMEE_DEBUG again, there is an option to delete all own breakpoints or all.