Muilt WiFi/Wlan profiles

[ozric100]

I have OZ 3.5.1 all set up and working great running from SD card with pivot_root, being called from init(best way I have found)..   I have all my contacts and stuff rescued from DTM hell, and my Handcom apps install and working.  BTW  great work on 3.5.1,  I had used Opie 3.2 befor I went to the TKC rom with sharp pim apps(bad move).   Any way.............................

The only question I have now is how do I get muilt lan and wifi profiles setup,  you know one for work, one for home,  one for wardriving ect.  

Thanks

[acpkendo]

ozric,

There is an app in the feed called opie-sh-wavelanchooser.  This, AFAIK, lets you set up wireless profiles for home and work, but not Ethernet/USB.  I haven't actually used it myself--OZ 3.5.1 won't connect to the BG-2000 access point here at work for some reason.

Also, as I mentioned in this thread, in the Network application in the Hentges ROM (based on OZ 3.3.6pre1), there is a "Profiles" tab right next to the usual "Connections" tab, but it's greyed out.  Is this something that's planned to be (re-)added to the Network app in 3.5.x?

Also also, could you post a quick explanation on how you got the Hancom apps working?

[ozric100]

thanks for the info.  I will look into that.  

As for the handcom apps.  I used the old versions from the 2.10(?) sharp rom.  I made a local pkg feed on my SD card and used a ipkg-make-index script to make the Package file.  Then you just install them with force-deps,  they will bark about some 1.5 lib,  but that will be covered by oz-compat(make sure you have this installed).  The next thing is to check the uid:gid on  /opt .  The pkgs might (did on mine) mess them up, if they are messed up just chown -R root:root /opt .. that will fix it.  Now just use makecompat from the CLI or the GUI and make then use the compat libs.   Start them from the CLI first to make sure they are working ok ....    enjoy.

I have all the handcom stuff, Opera, TKCvideo ane Jeod installed and working fine.  Oh installing Jeod is a bit more involved, but it will work too.  I got the Jeod ipk from a 3.2 feed somewhere.

[acpkendo]

I went to the Hamcom site and got the following versions:

Hancom Word v. 1.4.4
Hancom Sheet v. 1.01 (en)
Hancom Presenter Viewer v. 1.2.8

Are these the ones you used?  I've tried to install these directly with aqpkg and ipkg from the command line, but I always get an error about "cannot find package foo" (I've heard this is due to a difference in "control" file formats).  If you were able to get them working simply creating a proper feed that's great.  BTW, where did you get the ipkg-make-index script?  Is this part of the ipkg-utils package I've heard about?  Does it run on the Z?  Does it include an ipkg-build or similar script?

Lastly, does Hancom sheet run OK?  Some people have said it never would, due to the difference in floating-point-number calculations between gcc 3.x and 2.9x

Is this enough questions for you?  

[ozric100]

Your are correct ... Hancomsheet is borked ...   all you get is 19's in the cells .. unless you change them to text format... Not good.  I guess I will need to look into a replacement for that.

[acpkendo]

Good to know, but actually I'm more interested in Word than Sheet.  Have you gotten that to run?  I'd be very interested to know how. . .

[kergoth]

The most correct means of setting up network and wireless profiles in OpenZaurus would be to use the existing support in /etc/network/interfaces for 'mapping' entries.  Basically, you setup an entry in that file which tells it how to determine which "mapping" it should use when you attempt to bring up an inteface.  For example, i could go to bring up wlan0, and it could call out a script that checks what mac addresses are nearby, and returns either 'work' or 'home' based on that information, and brings up the appropriate one.

There are existing tools to make this easier.  Remember that OZ is debian based.  Google for info on ifupdown-roaming and waproamd.

I do not believe any of the GUIs supports making use of any of this.  Yet.
--
Chris "kergoth" Larson