I-Appliance BBS The Official Source for Internet Appliance Upgrades and Mods BBS Main List | Sign In | Sign Up | Search | Help | Linux-Hacker.net Reply to Thread | Printer |

Home / Other I-Appliances / 3Com Audrey Remote Access via QNet - A QNX Native Protocol...

Remote Access via QNet - A QNX Native Protocol... (modified 0 times) D. Wood Profile [url]http://207.198.90.123/ipaq_bsp/cross_development.html While this page deals with the ipaq, I think it could be easily translated for use for the Audrey. Cant wait to see what floppy and jay do with this! Audrey Button Gallery danielwood(at)charter(.)net 10-22-2001 21:48:10

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) scooter Profile I have gotten qnet running and it may be due to me trying to run a USB barcode scanner too but performance is simply "weird". I have to try this on one of my other Audreys without the usb keyboard stuff. If I go from my PC (QNX 6.0) to my Audrey performance is great. If I go from Audrey to the PC it's horrendous. A cd to /net/qnx60 on Audrey takes like 30 seconds. An ls once in there takes minutes. The other way around takes a 1/2 second. It's possible that it's the way I'm mounting my USB ethernet issuing a second io-net to do it which creates a second io-net process (supposedly a no-no): io-net -dklsi -pttcpip -oif=en0:192.168.123.51,gateway=192.168.123.254 "slaying" the original io-net hangs the Audrey I can't seem to come up with the appropriate mount command using something like: mount -Tio-net -oif=en0:192.168.123.51,gateway=192.168.123.254 /nto/lib/devn-klsi.so I've tried to create all sorts of config files under /etc and those don't seem to do anything. Anybody doing any better or know how to avoid the double io-net process? Also does any one know how to manipulate .script? The directory eludes me at the moment. It seems to be binary but there's a lot of strings in there that seem to be setting things like environment variables. It also seems to be where the first io-net is being started. 10-23-2001 07:03:27

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) keith721 Profile check out http://qdn.qnx.com for their two articles about building embedded systems. they're actually edited versions of akhilesh mritunjai (apologies if mis-spelled) earlier document, "A QNX buildfile roadmap". it would seem that we can replace the .script file by building our own embedded filesystem, then mounting it, and copying the file over audrey's original .script file. 10-23-2001 13:54:44

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) jukebox Profile I think qnet could be one of the most exciting network features in QNX. In my USB image I managed to kill the hardcoded network setup during boot and replace it with a new setup of choice, qnet included. If properly setup in your LAN with a PC running QNX RTP I believe you should not only be able to share files, but hardware too between Audrey and your PC! So far I have reached this point. By enabling qnet in Audrey with the USB1 or 1-1 image I get a /net directory in both Audrey and my PC. Audrey has /net/kojak and my PC has /net/localhost and /net/kojak. From my PC I am in full control of Audrey's files and hardware, however the goal is ofcourse the other way, I want full control of files and hardware of my PC in Audrey. Twenty minutes ago I used FileManager in Audrey, went to /net and pressed Refresh. I can see the nic led flicker ever since and apparently Audrey is trying to download the RTP file system, which is of no use this way. However my RTP is running any and all QNX 6.0 and 6.1 software available and is huge. I wonder if control is available what is and what isn't mapped by qnet. Or you could consider setting up a small but tailored QNX system on your PC for use with qnet and Audrey only that works possibly fast. (Btw it should be possible too enabling qnet in any Audrey image with mount from the RTP, just by adding the qnet module to the existing io-net already running, after adding the qnet lib/dll too. Forget changing the hard coded script in /proc/boot, my method is as good and easier). Who knows more about qnet and its possibilities for Audrey? jukebox http://www.prins.net/audrey/index.html 04-27-2002 18:47:45

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) jukebox Profile I wanted to be sure about hardware control over qnet. Well it works! I set the spooler in my PC that runs the RTP on Audrey's printer and printing from my RTP PC did work over Audrey, while my RTP has no printer at all. So qnet is an exciting feature indeed. Hope we can get any further with this for Audrey too. jukebox http://www.prins.net/audrey/index.html 04-27-2002 20:03:29

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) jukebox Profile Does soemone know how to change the name of Audrey for networking purposes. Mine apparently is set to kojak in USB1-1 and I want to try 2 Audreys with qnet, but both with the same name doesn't work. In the environment I found TARGET=KOJAK, but I can't change it with export or set. Any ideas? jukebox http://www.prins.net/audrey/index.html 04-28-2002 21:36:46

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) Sketchy Profile The network name of the Audrey is in Actions --> Internet Settings --> Advanced Information --> Hostname That TARGET=KOJAK is unrelated to networking. I think it's so that apps can determine if they are running on an Audrey or not. -- Jim ACID and other Audrey apps 04-28-2002 21:46:17

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) jukebox Profile Sketchy, do you have any idea in which file the hostname is written? I may have a problem by having removed ActionPalette I can't change the hostname from there, but the name should be somewhere in a file, probably in /config jukebox http://www.prins.net/audrey/index.html 04-28-2002 22:47:59

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) jukebox Profile I can set the hostname with the hostname utility from the RTP. No problem. I'll make it available for download in my Audrey Repository. jukebox http://www.prins.net/audrey/index.html 04-28-2002 23:57:46

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) Sketchy Profile Sounds like you have it figured out, but FYI I grepped my entire Audrey filesystem for my hostname "yellowaudrey" and found it in the following files: /config/USER_ISP_ETHERNET_USB.cxn /config/NetworkSettings /data/ispsetup.cfg -- Jim ACID and other Audrey apps 04-29-2002 00:53:12

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) jukebox Profile Now with two Audreys with different host names and a PC with the RTP hooked up to the LAN I get both Audreys mapped in the RTP /net directory in a second. However in Audrey I get the local host in /net alone, also when I disconnect the RTP from the LAN. I think the problem is something else and may have to do with permissions set in Audrey. Only the root user in Audrey can write to "disk", although you would think qnet is root user too. Anybody has ideas how to change permissions in Audrey to allow qnet to write to "disk"? jukebox http://www.prins.net/audrey/index.html 04-29-2002 10:20:29

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) jukebox Profile I did get a step closer to qnet working on Audrey. First of all you have to make sure all host names in /etc/hosts match the host name of each PC/Audrey. Start qnet eihter by editing /kojak/networkUSB.sh as indicated earlier or do this command from terminal: /nto/photon/bin/mount -Tio-net npm-qnet.so to allow for default settings. Next change directory in terminal to /net and use ls to see other machines on your LAN running qnet, either RTP6.1 or another Audrey running USB1-1. Qnet 6.0 is not compatible with 6.1. The last problem is when you try to change directory to the remote directory you get the message "No route to host", although I can ping without a problem. It seems qnet uses the domain name too in addition to the host name and I adjusted all names accordingly with an alias in /etc/hosts, but still the same result. However in the RTP I have full control over soft and hardware of 2 Audreys. It all becomes one PC. Any ideas about the routing? jukebox http://www.prins.net/audrey/index.html 04-29-2002 23:06:05

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) jukebox Profile I can't get any further without help on this board. The RTP is in full soft and hardware control of 2 Audreys in a LAN. The 2 Audreys can see the RTP and each other, but have no access to files or hardware. If I try to get access "No route to host" while I can ping and do get a route with the route get utility. When I create a route I get the message "Route already exists". Qnet works with ndp to resolve a hostname and I wonder if anything could be missing on Audrey to make that work. Doesn't look like it. Another problem could be Audrey boots on QNX 6.0 while the network and USB setup is QNX 6.1 and the qnet I use is 6.1 and not compatible with QNX 6.0. QNX documentation isn't clear what exactly isn't compatible between versions 6.0 and 6.1. I wonder if you use the npm-qnet.so 6.0 dll on all computers what would happen, if anything at all. I'm open for any suggestions and ideas. jukebox http://www.prins.net/audrey/index.html 04-30-2002 19:06:04

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) jukebox Profile Nice monologue.. Anyhow I tried version 6.0 npm-qnet.so on USB1-1 and the RTP 6.1 and io-net crashed. I still believe my initial qnet setup could work with a minor tweak, but I have no idea what that could be. jukebox http://www.prins.net/audrey/index.html 04-30-2002 19:50:52

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) jukebox Profile Hacking Audrey with Qnet appears to be extremely easy. When some serious hacking is going on you will have the RTP running anyway on a PC in your LAN and with Qnet running on both you'll have access to soft and hardware in Audrey from the RTP. You can link, run apps remote or local and use hardware in Audrey, all from the RTP, where the goodies are most of the time. Qnet is an exciting feature for Audrey this way already for hacking purposes. jukebox http://www.prins.net/audrey/index.html 05-02-2002 13:49:48

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) chrismckillop Profile Yes, you are going to have issues using the Qnet from 6.1 with a 6.0 kernel. You will also have issues using qnet from 6.0 with qnet from 6.1 as there where changes made that could have issues between the versions so they are made to ignore each other. -- cdm@qnx.com http://qnx.wox.org/ 05-05-2002 14:38:42

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) jukebox Profile Issues at hand here are pretty normal. If you do a search for qnet here: http://groups.google.com/ you'll find several people having the same issues booting from a QNX 6.1 kernel as I have. I don't believe booting from a 6.1 kernel is an issue after all. Currently I have 2 Audrey's and the RTP 6.1 becoming one computer already. The last issue is to have the same in Audrey itself, I'm more than half way there already with qnet. Qnet in 6.0 was alpha stage. Qnet in 6.1 probably isn't much more than beta stage and I have all my hopes up for 6.2 coming soon with more USB devices supported and a better Qnet too. jukebox http://www.prins.net/audrey/index.html 05-05-2002 15:18:18

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) chrismckillop Profile Qnet in 6.1 was very good actually, we have many customers using it in shipping systems. The issues you are going to see are due to the fact that qnet is rather tightly coupled with the kernel and there where changes in the kernel<->qnet interface between 6.0 and 6.1. So running a 6.1 qnet on 6.0 isn't going to work. Far worse in fact is if you are trying to run a 6.1 anything inside of a 6.0 io-net. -- cdm@qnx.com http://qnx.wox.org/ 05-05-2002 15:24:03

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) jukebox Profile I don't run anything 6.1 in a 6.0 io-net. Everything I use to have the network up is 6.1, including ldqnx.so.2, io-net, full tcpip, pppmgr and qnet. The same goes for the conmplete USB stack. Maybe you can run my V.USB1-1 image and help to get qnet to work for the full 100%. jukebox http://www.prins.net/audrey/index.html 05-05-2002 19:08:17

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) chrismckillop Profile You miss my meaning. You can't use the 6.1 qnet without a 6.1 kernel. Since you are still using a 6.0 kernel it doesn't matter how many of the services or libs from 6.1 you copy over, qnet won't work. You guys should just figure out how to upgrade the box. ;) And I can't flash your image, I don't own an Audrey. Too many conflicts of interest for me to work on hacking something the company I work at did the software for! :) -- cdm@qnx.com http://qnx.wox.org/ 05-05-2002 23:47:12

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) jukebox Profile Well I just gave it a try.. For the time being I'll settle for a partly working Qnet. It's a great feature. Btw I assume the 6.0 kernel is the hard coded libc.so.1 in Audrey. jukebox http://www.prins.net/audrey/index.html 05-06-2002 00:07:35

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) Sketchy Profile libc.so.1 is just the C library. I think the kernel mostly lives in procnto (don't quote me). By the way, I think it's very cool that the QNX guys (or at least Chris) are reading this list. Chris, how involved did you guys get, technically, in 3Com's Audrey business? Or did they just license the OS and disappear until the Audrey shipped? If you have any history on that, I'm sure we'd all like to hear it. -- Jim ACID and other Audrey apps 05-06-2002 09:07:52

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) Sketchy Profile I should say that libc probably implements a lot of the POSIX style kernel calls, but it's not the kernel itself. Also, procnto is the process manager, which is only a part of the kernel. I don't know why I'm going on about this when I clearly don't know anything! -- Jim ACID and other Audrey apps 05-06-2002 09:20:04

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) jukebox Profile I'm just curious what the kernel exactly is in QNX. Who knows more? jukebox http://www.prins.net/audrey/index.html 05-06-2002 13:55:19

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) chrismckillop Profile No, libc.so.1 is the C library not the kernel. The kernel is procnto and lives in the flash boot-block just after the IPL. You can see proc (the kernel process) running in the output of "pidin". It is PID 1. Best bet is for someone to get a 6.1/6.2 startup+procnto to work with the Audrey if you want to use QNET or to use nfs. -- cdm@qnx.com http://qnx.wox.org/ 05-06-2002 14:41:03

RE:Remote Access via QNet - A QNX Native Protocol... (modified 0 times) jukebox Profile I agree with what you say about Qnet, but nfs works already as a client and as a server the way I have set it up. It may not be according to plan with QNX but it does work like a charm for months now booting with QNX 6.0 and running io-net etc. in QNX 6.1. jukebox http://www.prins.net/audrey/index.html 05-06-2002 15:03:06

Reply to Thread | Printer | All times are PST Powered by UltraBoard v1.62

I-Appliance BBS General - NEWS, Breaking NEWS - linux-hacker.net BBS on CD Questions - User Groups in Your Town - E-Bay, Yahoo Auction LINKS ONLY (MODERATED) - Jokes & Humor - usdtv box I-Opener Areas - I-Opener General Posts - I-Opener Technical Stuff - I-Opener Technical Info Reference (MODERATED) WebSurfer Areas - WebSurfer General Posts - WebSurfer Technical Stuff - WebSurfer Technical Info Reference (MODERATED) Other I-Appliances - Virgin Webplayer - WebPal - MailStation - 3Com Audrey - ThinkNIC / Oracle NIC - Gateway/AOL Connected Touch Pad - Philips/AOL-TV - ACER NT-150 STB - MSN Companion - Compaq IA - Emachines IA - IBM NetVista IA - Intel dot.station - MSNTV2 Network Computers - Fujitsu-Siemens Scovery Linux Net Computers - GallantWeb Server Consoles - Dreamcast - xbox hacking Web Pads - Epods One General Post - Panasonic CF-01 - Fujitsu Stylistic 1200 - Cybiko Thin Clients - Thin Clients DigitalVideoRecorders - DTV Recorders, Replay, TiVo, Etc... - Tivo Hacks Linux - Midori Linux General Board - ITX MotherBoards Single Board Computers - Earth Computers mARMalade Elite Member Area MISC Areas - The Swap Meet WE TAKE NO RESPONSIBILITY FOR ANY TRANSACTION HERE AND NO COMMERCIAL POST PERIOD !!! - Wireless Net - Cameras - Robotics - Routers/Gateways - Mattel JuiceBox