OpenWRT 3G/UMTS Router

comgt and option driver module are required.

clipped from forum.openwrt.org

"Mostly the comgt package provides is a sane and tested set of PPP and OpenWRT scripts designed to make configuring cellular data connections as painless as possible. Hopefully the next release will come soon and include it, but here are the additional configuration options it currently provides:

---

config interface "foo"
       option device       "/dev/ttyUSB0"
       option proto        "3g"
       option apn          "my.provider.apn"
       option service      "hsdpa" # or cdma, evdo, umts_only, or gprs_only     option pincode      "12345"     option mtu          "1492"

---

So, here are my two condensed lists, truths and needs:

---

Truths:
- Most cellular modems, whether they plug in via PCMCIA, Cardbus, ExpressCard, or direct USB are USB at heart
- Serial speed doesn't matter
- As long as you have a directly supported device and a kernel less than two years old, you don't need to mess with buffer sizes

- Actual throughput almost never matches marketed throughput

Needs:
- For a PCMCIA or Cardbus device, you will need your hardware's PCMCIA or Cardbus drivers in addition to your USB driver
- For an ExpressCard, the base PCI drivers
- A base USB driver (usually ohci_hcd for Cardbus/PCMCIA/ExpressCard)
- usb-serial (2.6) or usbserial (2.4)
- device-specific driver, if available
At this point, if you plug in your device you should see /dev/ttyUSB0 or higher. If you don't, you are missing a driver or driver option
- pppd
- A chat script (there are dozens of examples out there, comgt does provide one that should work for most people)"

"Halvljuslag"?

clipped from www.svd.se – Att köra med halvljus och bakljus samt nummerplåtsbelysning under soliga dagar är inte nödvändigt för att bilen ska upptäckas av andra bilister, mejlar Christer, dessutom drar halvljuset uppmärksamheten från fotgängare och cyklister i bilens omedelbara närhet. Han säger också att varselljuslag i den svenska meningen (att det alltid ska lysa) bara gäller i Norden och Estland. I länders som Polen, Tjeckien och Österrike gäller lagen bara vinter, i Italien dagtid utanför tätort.Österrike har, enligt ADAC:s hemsida, sedan 1 januari avskaffat lagkravet om varselljus dagtid, men tillåter bilar som redan har automatiskt halvljuspåslag att använda ljus även på dagen. En sak går att konstatera: det enade Europa är särdeles oenigt när det gäller trafiken och dess regler. Noll promille eller 0,5? Halvljus påbjudet eller förbjudet? Mobil tillåtet, eller förbjudet utan handsfree? Reflexväst i bilen?

Custom firmware w. Asus WL-500W

Mobile WLAN and UMTS Router

I bought the router Asus WL-500W in order to have it run OpenWRT Kamikaze 7.09 as a replacement for my previous Linksys WRT54G3G, which is still used in another location. The WRT54G3G has no USB ports but a CardBus slot, which contains a Huawei E600 UMTS (no HSDPA) adapter. The E600 serves the WAN port of the WRT54G3G running the Kamikaze 7.09 brcm-2.4 port since I was unable to get the WRT54G3G WLAN to work with the 2.6 kernel (brcm47xx port). This is a wellknown problem which is due to the chipset manufacturer Broadcom not releasing the source code for their proprietary WLAN driver for the Linux 2.6 kernel. (Actually, I believe it's the driver's Hardware Abstraction Layer - HAL- which is needed. Work is currently in progress in the open source community on alternative drivers, i.e. b43. The alternative drivers as of today, March 2009, are reported to work with some brcm chipsets, but according to my findings they do not yet work satisfactorily with the Broadcom WLAN chipsets in WRT54G3G (BCM4712 - 802.11g) and WL500W (BCM4321 - 802.11N-draft).

So, the new WL500W, which has two USB ports, is supposed to make use of a Huawei E220 UMTS (HSDPA) Modem, a dongle for WAN. This may not be altogether unproblematic, since the Linux 2.4 kernel has no built in support for USB modems. This was introduced in the 2.6 kernel with version 2.6.19 I believe. (http://wiki.debian.org/Huawei/E220: "E220 is supported natively in Linux kernels 2.6.20 and later, using the usbserial.ko (usbserial-generic interface) module. - Also usb_storage.ko is aware of HUAWEI E220 modem and no further action needs to be taken.")

I have experimented with a few of the open source firmwares for the WL-500W, but all seem to have their own shortcomings:

1. Koppel: www.koppel.cz/cdmawifi, versions 1.69 and 1,71. Based on the wellrespected Oleg firmwares (latest stable subversion "10") for the Asus WL-500 series of routers, which are based on stock Asus firmware and extensively modified with bugfixes. The Koppel modifications are done to get the WAN port use UMTS adapters and are developed by a czech gentleman by the name of Jiri Engelthaler. Based on the 2.4 kernel.

Koppel works very well on the WL-500W, both WAN (UMTS) and WLAN (brcm). The only caveat I have found are firewall issues, which remain from the Oleg firmware. It seems that the "A" directive in iptables is not working. I am unaware of any firewall rules with port-forwarding of SIP ports, which my setup requires, based on other than the "A" directive so the firewall doesn't work for med. The firewall is iptables with a web interface aswell as a post-firewall script. I was unable to configure the router for good and efficient use including asterisk (SIP) behind the NAT firewall.

2. Alpha versions of the Oleg firmwares can be found on Google Gode. It seems that someone has continued the development of Oleg's firmware, which has not progressed for more than a year. It runs fine, at least the subversion "d" I tried, but I could not get WAN to work with E220. No reference to the firewall issue in the list of changes.

3. Asus has brought out a new firmware for the WL-500W, version 2.0.0.6. I heard that the issues of the previous versions, corrected by Oleg, remain, so I did not work very long to check whether the E220 could be made to work. Certainly, it does not work out of the box.

4. X-WRT is a version of OpenWRT which is not a fork. It adds an improved webif configuration interface. This web interface uses some Flash memory, which is particularly limited in the WRT54G3G, only 4MB. So, only the WL-500W benefits from X-WRT if you need to install additional drivers to get E600 UMTS adapter to work. The Kamikaze 8.09 has recently been relesed, also by X-WRT, and looked fine in the brcm47xx port I tried. But i could not get the b43 driver which was installed automatically to control WLAN of the WL-500W. The mini-PCI card was not recognised.

5. DD-WRT is currently under heavy development. It looks very promising, so I installed the latest V.24 pre-SP2 mega build. It seems the WL-500W can handle it with its 8MB flash, but JFFS has only 320 kb available after enableing it. So, USB storage is required. Unfortunately I could not get E220 to work and it seems difficult to get IPKG packages to work without a functional WAN port for Internet access. It's kernel 2.4.37, so USB modems need special attention.

I'm currently investigating the possiblity to install Debian on the WL-500W. This can be done, according to http://wpkg.org/Running_Debian_on_ASUS_WL-500W, but I doubt that it will be beneficial to a router. It works very well on a NSLU2 running asterisk however. If m0n0wall is lightweight enough, I guess that could be possible. But with only 32MB of RAM available, the same with NSLU2 by the way, you must be very selective with what to install. I do need iptables, vlan, dnsmasq and a sip proxy such as milkfish, which is included in DD-WRT mega and voip builds.

Re: REPORT - Enosoft DV Processor 1.5.0

Hello, John, and thanks for taking your time.

In the meantime I have resolved the issue, which was with my XPconfiguration. Enosoft DV works fine now. Possibly, my findings may be of use to other not so competent users, so here it goes. Sorry for being lengthy.

As I indicated, I'm a first time user and have been using PPro with a Canopus capture card for some years. Now I wanted to convert a 13 GB DV-AVI file from PPro to AVC in Matroska by using Handbrake (Pre4). I thought the DV-AVI file was useless outside of PPro, and wanted Enosoft DV to convert to an intermediate DV file before Handbrake. I had previously done so using MPEG Streamclip.

Enosoft accepted the DV-AVI, but did not monitor it at all. Further processing was impossible. So I asked for this error report to be produced, and the error report production crashed the app after the email had been produced in Outlook (or Express, which I normally don't use either) but before it was sent. I managed to manually send the email to you after recovery from the crash.

I did manage to convert to DVI by using MPEG Streamclip, which is QuickTime-based. No problem here with monitoring or conversion. I tried another app by M. Paul Glagla (http://paul.glagla.free.fr/index_en.htm), DVdate 7.0.9, which simply reported that the file was not found, even after having used the File Open dialogue of the app; suspicious. Another app by M Glagla put me on the right track; ImageGrab 4.2.0. This app reported that my system was using DirectX 9 ("9 f" I believe) but had problems that some DX filters contained in quartz.dll (i e AVI splitter) were missing from my system. Bill would not let me reinstall DirectX, so I looked for an already installed tool which came with K-Lite Codec Pack a long time ago, Tweak Tool. This tool fixed DirectX/quartz.dll and removed some traces of older divx installations as a bonus. No idea why quartz.dll had been uninstalled though. Spybot S & D? Just guessing.

Now every app that relies on DX (Enosoft DV, DVdate and ImageGrab) are functional. Yours looks like a very useful app for DV editors and not too complicated for the casual user. Thank you, again.

Regards,

Mikael N

John M skrev:
> Hello,
>
> Thank you for your message.
>
> I notice from the event log (part of the overall report) that you
> manually triggered the report. When this happens, the software mimicks
> an application crash to force Windows to call the software's error
> handling. Once you have generated a report, it is not recommended that
> you continue using that instance of the software. i.e., close the
> program and start afresh. BTW, in your case, all of the information was
> correctly reported. Did you let the report generation process
> automatically create the email or did you send the .zip file manually?
>
> Were you generating the report for a particular reason or just curious
> to see what it contained? If you are having trouble with the software,
> please send a description of the problem.
>
> Kind regards,
>
> John M
> enosoft - high performance tools for music and video
>
> ------------------------------------------------------------------------
> *From:* Mikael N
> *Sent:* Thursday, November 06, 2008 1:13 AM
> *To:* support@enosoft.net
> *Subject:* REPORT - Enosoft DV Processor 1.5.0
>
>
> Had just loaded my first 60 min DV file, create by Adobe Premiere
> Pro 7.0. Was collecting an error log, when app crashed.

Goda grannar

- Taken at 9:22 PM on July 29, 2008 - cameraphone upload by ShoZu

Marcus im Heidepark Soltau

Marcus gillar TMNT