Er, yes, wm0 was for illustration only.  

Please use whatever ethernet device you have!

--
aboyd

-----Original Message-----
From: bob lipka [mailto:bobik@os.pl] 
Sent: Wednesday, July 16, 2008 2:40 PM
To: general-networking
Subject: Re: RE: RE: Qnet native AND over tcpip

>Try this command line
> option for qnet, which should create two L4's and
> two resolvers:
> 
>   bind=wm0,resolve=en_ionet,bind=ip,resolve=dns

Are you sure about wm0? Under /dev/io-net I only have en0, ip0, ip_en.
Thats after starting pcnet and tcpip. Before starting qnet-l4. In my
case shouldnt I use en0?

RobertL

_______________________________________________
General
http://community.qnx.com/sf/go/post10619

> I suspect that the problem may be that you can't
> have two name resolvers running at the same time

I was not sure what I saw, but now I can write this:
During my trials, when I have tried to start two L4 at once, I have seen something like two copies of io-net were 
sharing the same process number, and when I have slayed all io-nets, there were still some io-nets running. They did not
 show up via ps, but pidin showed them and I had to kill them via kill -9 proc-number. I had to do this, because next 
trial commands complained about some resources being already there or impossible to create.

RobertL

From: Robert Craig [mailto:rcraig@qnx.com] 

> it might not be possible

PR 59725 created to track this

--
aboyd  www.PoweredByQNX.com

From: bob lipka [mailto:bobik@os.pl] 

> # io-net -dpcnet -ptcpip stacksize=16384 -pqnet 
>   bind=ip,resolve=dns,bind=en0,resolve=en_ionet
> # netmanager
>
> All nodes visible, remote and local!
>
> Thank you very much for your help!

You're welcome!  Sorry it took so long for
you to get this working - it's a slightly
unusual configuration.

--
aboyd  www.PoweredByQNX.com

On Fri, Jul 18, 2008 at 10:47:11AM -0400, bob lipka wrote:
> I am replying a bit late, but I was out to do some real work :)
> 
> > Try this command line
> >   bind=wm0,resolve=en_ionet,bind=ip,resolve=dns
> 
> I have slayed io-net, then run:
> 
> # io-net -dpcnet -ptcpip stacksize=16384 -pqnet bind=ip,resolve=dns,bind=en0,resolve=en_ionet
> #netmanager
> #ls /net/q632pc2d     --- thats remote node over IP

Is the 'stacksize' option necessary?

-seanb

Isn't that interesting...  I tried those same options but with
bind=en0,resolve=en_ionet first and I couldn't seem to get it to work.

Looks like a bit more testing is required (!)

I've put in a problem report for the docs to correct the outdated option
usage.

	Robert.
	

-----Original Message-----
From: bob lipka [mailto:bobik@os.pl] 
Sent: Friday, July 18, 2008 10:47 AM
To: general-networking
Subject: Re: RE: RE: Qnet native AND over tcpip

I am replying a bit late, but I was out to do some real work :)

> Try this command line
>   bind=wm0,resolve=en_ionet,bind=ip,resolve=dns

I have slayed io-net, then run:

# io-net -dpcnet -ptcpip stacksize=16384 -pqnet
bind=ip,resolve=dns,bind=en0,resolve=en_ionet
#netmanager
#ls /net/q632pc2d     --- thats remote node over IP

Remote node's listing shows up.
#ls /net
All nodes visible, remote and local!

This 'resolve=en_ionet' bit must have done the trick. In my trials I
have given 'resolve=nds' ,as in the pdf book Utilities page 1787 (help
shows the same). And 'netmanager' command must also be given, or no
remote nodes will be accesible.

I dont know yet how stable this setup is, but for now a full success!
So I am not posting qnetstats as it looks unnecessary now, I think.

Thank you very much for your help!

RobertL

_______________________________________________
General
http://community.qnx.com/sf/go/post10720