Horstbox OpenWrt project questions and comments

synnack

Neuer User
Mitglied seit
20 Jan 2007
Beiträge
4
Punkte für Reaktionen
0
Punkte
0
Hi,

I've sent roughly the following mails to foschi, I'm presenting my side here, so they can reply with their answers here as well, and it would kinda look like a thread here ;-)

I am a Horstbox user from the Netherlands and have some ideas and suggestions about where to go with the openwrt horstbox project.

(From my first e-mail)
I've recently taken an interest in your sourceforge project to port
openwrt to the horstbox and I'd like to participate and contribute.

I have a few comments and questions. First the comments:

1. A lot of precompiled packages for this platform are already available
from http://ftp.osuosl.org/pub/nslu2/feeds/openwrt/unstable/ as well as
http://downloads.openwrt.org/snapshots/ixp4xx-2.6/packages/ and
http://downloads.openwrt.org/kamikaze/7.06/ixp4xx-2.6/packages/

2. To get the intel platform to work we need 2.6.16.9 with zaphfc
(isdn), zaptel (telephony) and si3210 (modems). These modules depend on
on the Intel Access Library, which doesn't work well with newer kernels.

3. It would be nice to have a tun.ko module to support openvpn, aiccu
and possibly tinc.

4. We should supply some build environment as well.

5. We could set up a distribution which supplies all this. We could the
package lists from #1, merge them, weed out the kernel modules that are
compiled for the wrong kernel version, create some of our own .ipk
packages for the kernel modules and have a complete openwrt distribution.

6. We should look at the sources on the development iso (I have the
build environment from the live dvd) to make sure that we too can
provide things like samba (preferably in .ipk) file and printing
services. This includes the tiny usb lp port gateway (raw socket).

I'd be happy to help out with all this.

Questions:
1. Where can I find the kernel .config and the patches you used?

2. How did you compress the squashfs image, because my squashfs-lzma
complains about invalid superblocks (it works on the horstbox though).
Which version of squashfs-lzma did you use?

(From my second e-mail)

I want my horstbox to do:
* Asterisk with
* IAX to link multiple Horstboxes at several sites
* Fax to e-mail gateway
* ISDN2 external/internal
* FXO/FXS
* handle about 100 SIP phones (ext. 100-199)
* have 5 external SIP accounts
* voice call routing tests
* IPv6 (aiccu and radvd) for my SixXS tunnel
* DHCP and DNS relay for IPv4
* samba 3 working for file/printsharing
* maybe have samba 4 working, for testing Active Directory embedded,
but as this requires a port of openldap, heimdal, etc I may run out of
flash space.
* WPA2 secured wireless lan
* VPN connections through openvpn or tinc and openswan to link multiple
lans through horstboxes at several sites (openswan for routing with cisco)
* If possible a solid web interface to enable/disable and configure
some of these things, but I don't have the time to build this, probably.
* Possible a streaming audio server or handling a USB audio device for
music output w/ web interface
* Whatever else I may think of and can cram into it


I'll first focus my attention on getting openwrt to run on kernel
2.6.16.9 with the Intel Access Library and si3210 drivers for the modems
and zaphfc for ISDN2, so that asterisk functionality is complete and
configurable.

My next step would be to get aiccu to work and my horstbox to supply my
workstations with IPv6 addresses for my SixXS tunnel.

.. Then see if I can get asterisk to relay faxes to my e-mail and see if
I can get a snom phone to show line status of other sip phones cross IAX
in a secure tunnel.

Then the kernel work would be complete, as far as I'm concerned and my
attention will go toward gathering available packages, testing them and
providing a vast resource of stable .ipk packages that work from the
sources I previously mentioned.

Then I'll focus my attention on getting the AR7 board to perform
correctly. Currently I have no idea how these interfaces are connected
exactly, because the AR7 board bridges everything.. So there's a
challenge here to get my PPPoA VCMUX 4.48 to work, WPA2 wireless,
possibly Q-tagging the switch ports, if supported, etc.

I may try to set up a bluetooth/web synchronisation server for SyncML
phones with CalDAV by porting opensync (BlueZ should already work) and
possibly PHP/rscds, but I have this terrible feeling that PHP'll never
work on this thing.

I may want to write a web interface for managing basic tasks like
updating the system time, configuring SIP extensions and accounts,
adding printers, adding shares, etc. I may try to port the web interface
from the original horstbox source to a .ipk package and extend it
somewhat, but I'm not sure I'll have enough room in the squashfs
filesystem for that.

So, there you have it, a rough idea of my plans. Probably these will not
work all at once.. but that's a problem for later on.


(From my first e-mail again)
Although the horstbox is a German product and I ordered it there, I'm
not completely fluent in German, I'd like the code/comments to be
English. I'd also like to provide help with translation to Dutch.

I can read German just fine, so if you have a comment, question or answer and English is too difficult, no problem, just try me in German.

--
Wilco Baan Hofman
 
Hello Wilco,

welcome to the Forum!

synnack schrieb:
Hi,
I've sent roughly the following mails to foschi, I'm presenting my side here, so they can reply with their answers here as well, and it would kinda look like a thread here ;-)

:) I will put in hehol's answers into this thread.

synnack schrieb:
I want my horstbox to do:
* Asterisk with
* IAX to link multiple Horstboxes at several sites
* Fax to e-mail gateway
* ISDN2 external/internal
* FXO/FXS
* handle about 100 SIP phones (ext. 100-199)
* have 5 external SIP accounts
* voice call routing tests
* IPv6 (aiccu and radvd) for my SixXS tunnel
* DHCP and DNS relay for IPv4
* samba 3 working for file/printsharing
* maybe have samba 4 working, for testing Active Directory embedded,
but as this requires a port of openldap, heimdal, etc I may run out of
flash space.

hehol schrieb:
That should be no problem as long as you don't run out of flash space
(there are still 32 MB's available which are mostly unused) on the
second flash chip.

synnack schrieb:
* WPA2 secured wireless lan

hehol schrieb:
This does not work with the official firmware of the DSL board ("Herta")
because the wireless driver on the version of Linux used by D-Link does
not support WPA2.

synnack schrieb:
* VPN connections through openvpn or tinc and openswan to link multiple
lans through horstboxes at several sites (openswan for routing with cisco)

hehol schrieb:
OpenVPN might work if you copy the binary over from the voice board
("Horst") to Herta at runtime (like all current custom firewall/startup
scripts). OpenSWAN will not work due to kernel restrictions on the
2.4.19 kernel used on Herta.

synnack schrieb:
* Possible a streaming audio server or handling a USB audio device for
music output w/ web interface

hehol schrieb:
At the moment, the USB performance is very poor. I don't know what's
causing it but the ISDN TE port is almost unusable during USB (2.0)
activity.

synnack schrieb:
I'll first focus my attention on getting openwrt to run on kernel
2.6.16.9 with the Intel Access Library and si3210 drivers for the modems
and zaphfc for ISDN2, so that asterisk functionality is complete and
configurable.

hehol schrieb:
You might want to have a look at the more recent kernel versions of the
DD-WRT project at <http://svn.dd-wrt.com:8000/dd-wrt/browser/src/linux/xscale>. They have
integrated and "forward-ported" the Intel Access Library. I've successfully compiled kernel 2.6.20 from within the HorstBox development
environment but I haven't tried to run yet.

synnack schrieb:
Then I'll focus my attention on getting the AR7 board to perform
correctly. Currently I have no idea how these interfaces are connected
exactly, because the AR7 board bridges everything.. So there's a
challenge here to get my PPPoA VCMUX 4.48 to work, WPA2 wireless,
possibly Q-tagging the switch ports, if supported, etc.

hehol schrieb:
The OpenWRT Kamikaze port runs on Herta. I've successfully connected to
Herta running OpenWRT from Horst. Herta crashed when I tried to load the
wireless drivers and ran the WPA daemon (according to the wiki, this is
expected). I did not try the DSL modem because I have no DSL but
according to the OpenWRT Wiki, the DSL modem *does* work at least up to
8 MBit/s downstream. The switch cannot be reconfigured and the LEDs do
not work correctly because there is no GPIO driver available in OpenWRT
for the AR7 platform.
 
hehol schrieb:
Zitat von hehol
That should be no problem as long as you don't run out of flash space
(there are still 32 MB's available which are mostly unused) on the
second flash chip.

Yeah, I agree. But one never know once once starting messing with the big stuff (php, samba, openldap, heimdal).

About WPA2:
hehol schrieb:
This does not work with the official firmware of the DSL board ("Herta")
because the wireless driver on the version of Linux used by D-Link does
not support WPA2.

hehol schrieb:
OpenVPN might work if you copy the binary over from the voice board
("Horst") to Herta at runtime (like all current custom firewall/startup
scripts). OpenSWAN will not work due to kernel restrictions on the
2.4.19 kernel used on Herta.

It doesn't necessarily have to be on Herta, although that would be nice as well. But why copy this stuff from horst to herta? I'd have to have AR7 binaries on my armeb box, while I have 32MB for this stuff on the AR7. Isn't it more sane to store it on Herta and get the configuration from Horst?

hehol schrieb:
At the moment, the USB performance is very poor. I don't know what's
causing it but the ISDN TE port is almost unusable during USB (2.0)
activity.

Is this with mISDN or zaphfc? I don't remember seeing special USB modifications on the horstbox in the original source, is that also very poor?

hehol schrieb:
You might want to have a look at the more recent kernel versions of the
DD-WRT project at <http://svn.dd-wrt.com:8000/dd-wrt/browser/src/linux/xscale>. They have
integrated and "forward-ported" the Intel Access Library. I've successfully compiled kernel 2.6.20 from within the HorstBox development
environment but I haven't tried to run yet.

Sounds good! That's the best news I've gotten so far. I've made a start in weeding through kernel patches and adjusting them for 2.6.16.9, to be compatible with the original horstbox source, which is a real pain. If this stuff is forward-ported then I won't have to! :dance:

hehol schrieb:
The OpenWRT Kamikaze port runs on Herta. I've successfully connected to
Herta running OpenWRT from Horst. Herta crashed when I tried to load the
wireless drivers and ran the WPA daemon (according to the wiki, this is
expected). I did not try the DSL modem because I have no DSL but
according to the OpenWRT Wiki, the DSL modem *does* work at least up to
8 MBit/s downstream. The switch cannot be reconfigured and the LEDs do
not work correctly because there is no GPIO driver available in OpenWRT
for the AR7 platform.

Good to know, thanks. I've seen this on the openwrt AR7 wiki indeed. Do you know if WPA-PSK (1) does work?

The switch cannot be reconfigured period? or is that also because of the GPIO driver?

Also, why can't we run a newer kernel on Herta? Is there not a newer kernel available which runs on AR7 or is it because of some driver, what is it?

--
Wilco
 
More to cram in

I just though of some more stuff, this would make:

I want my horstbox to do:
* Asterisk with
- * IAX to link multiple Horstboxes at several sites
- * Fax to e-mail gateway
- * ISDN2 external/internal
- * FXO/FXS
- * handle about 100 SIP phones (ext. 100-199)
- * have 5 external SIP accounts
- * voice call routing tests
- * leave voice mail -> e-mail
- * Follow-me dialing -> everyone logs into the samba domain, users that are logged in get the phone ringing, otherwise redirect to cell phone/offsite sip phone, unless (manually) disabled.
- * Telephone logging, internally or to external My/PgSQL database
- * Different ringtypes for internal/external or for the various MSN numbers
* IPv6 (aiccu, radvd and ip6tables) for my SixXS tunnel
* DHCP and iptables for IPv4 and DNS relay
* samba 3 domain controller and file/print sharing
* OpenLDAP for user accounts / SIP phone address books
* maybe have samba 4 working, for testing Active Directory embedded
* WPA2 secured wireless lan
* WDS Wireless distribution system for linking other access points to extend the range
* Bittorrent client
* VPN connections through openvpn or tinc and openswan to link multiple
lans through horstboxes at several sites (openswan for routing with cisco)
* If possible a solid web interface to enable/disable and configure
some of these things, but I don't have the time to build this, probably.
* Possible a streaming audio server or handling a USB audio device for
music output w/ web interface
* FTP server
* Dropbear SSH busybox shell


I want to make these packages available as well through a repository that provides all of the above

P.S. Why can D-link make WPA2 work, and openwrt can't? D-link uses open source drivers as well, right?
 
2.6.19 works

2.6.20 is currently broken in the dd-wrt svn.

2.6.19 works with some modifications.

I've patched the OpenWRT build to have a Horstbox profile for ixp4xx-2.6, this profile enables the CONFIG_MACH_HORSTBOX option from the kernel patch I ported from the original Horstbox source.

I've made a .tar.bz2 of an svn export of the dd-wrt patched kernel which I placed in the dl directory. Because this one is already heavily patched, I moved all OpenWRT kernel patches to a backup directory. So it's just the dd-wrt kernel with the Horstbox patch.

I'll make my OpenWRT build available soon, because some kernel config changes are also necessary. (both in generic-2.6 and ixp4xx-2.6)

I think that this also solves the USB2.0 problem some of the people on this forum are facing, that's what the original horstbox had some PCI bus parameter patches for. Take a look in patch.kernel-2.6 in the archive directory.

More to come later this weekend.
 
Hi Wilco,

synnack schrieb:
It doesn't necessarily have to be on Herta, although that would be nice as well. But why copy this stuff from horst to herta? I'd have to have AR7 binaries on my armeb box, while I have 32MB for this stuff on the AR7. Isn't it more sane to store it on Herta and get the configuration from Horst?
It's better not to copy files from Horst to Herta and run them on Herta. But to get the full functionality, you have to use the firmware provided by D-Link for Herta, because the Linux drivers which are publicly available lack some functionality (stability when using DSL, WPA encryption on Wireless LAN).

synnack schrieb:
Is this with mISDN or zaphfc? I don't remember seeing special USB modifications on the horstbox in the original source, is that also very poor?
The USB performance on Horst is very poor. I did not test mISDN yet because it does not work on big endian machines.

synnack schrieb:
Good to know, thanks. I've seen this on the openwrt AR7 wiki indeed. Do you know if WPA-PSK (1) does work?
WPA (1) works with the original D-Link firmware. I tried OpenWRT as well, but the kernel crashed when loading the encryption tools. I did not have a serial cable attached at that point, so I don't know what happened. I might have done something wrong ...

synnack schrieb:
The switch cannot be reconfigured period? or is that also because of the GPIO driver?
The switch cannot be configured because the low-level GPIO functions for the AR7 platform are missing in the OpenWRT kernel. I did not check the DD-WRT kernel, but I think it is facing the same problem. Someone has to generalize the GPIO functions provided by AVM's FritzBox GPL kernel. And finally, someone has to figure out which GPIO pins D-Link uses ;-) I asked D-Link about the GPIO pinout, but they could not provide the information to me (most likely because they just bought the PCB design from someone else).

synnack schrieb:
Why can D-link make WPA2 work, and openwrt can't? D-link uses open source drivers as well, right?
D-Link does not support WPA2, only WPA. After all, they are using MontaVista Linux which includes a binary-only driver provided by Texas Instruments. Texas Instruments has not released source code for any of the non-trivial functions of the AR7 platform and I doubt they will as long as they sell the platform. It has always been their policy to only release the interface as open source and keep the actual functionality in binary files. So, you either have to stick with MontaVista Linux (like D-Link, Linksys, Netgear) or write your own drivers (like AVM).

Cheers,
Henning
 
Holen Sie sich 3CX - völlig kostenlos!
Verbinden Sie Ihr Team und Ihre Kunden Telefonie Livechat Videokonferenzen

Gehostet oder selbst-verwaltet. Für bis zu 10 Nutzer dauerhaft kostenlos. Keine Kreditkartendetails erforderlich. Ohne Risiko testen.

3CX
Für diese E-Mail-Adresse besteht bereits ein 3CX-Konto. Sie werden zum Kundenportal weitergeleitet, wo Sie sich anmelden oder Ihr Passwort zurücksetzen können, falls Sie dieses vergessen haben.