initial post

server · January 12, 2001, 5:25pm

message unavailable

system · January 12, 2001, 5:25pm

joe@qnx.com wrote:

initial post

test follow-up

–
Joe Bishop (joe@qnx.com)

Bill_at_Sierra_Desig · January 13, 2001, 1:03am

Is this group intended to be RTP specific?

If so, should’n it be called ‘qdn.public.qnxrtp.ddk.network’?

<joe@qnx.com> wrote in message news:93nem2$83q$1@nntp.qnx.com…

joe@qnx.com > wrote:
initial post

test follow-up

–
Joe Bishop (> joe@qnx.com> )

Chris_McKillop1 · January 13, 2001, 7:07am

Bill at Sierra Design <BC@sierradesign.com> wrote:

Is this group intended to be RTP specific?

If so, should’n it be called ‘qdn.public.qnxrtp.ddk.network’?

Well, perhaps - if there where DDK’s for doing Network Drivers
on QNX4, which there isn’t. And yes, it is Neutrino
specific.

chris

–

cdm@qnx.com > “The faster I go, the behinder I get.”

Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Brian_Northgrave · February 13, 2001, 9:06pm

Tue Feb 13 2001 - Network Driver Development Kit Now in Beta !!!

The Network Driver Development Beta Package is now available at the following
location:

http://betas.qnx.com/net_ddk/

username: ddkbeta
passwd : ddkbeta

Simply add this repository and point it at the correct url,
then enable userid & passwd.

Start the Package Manager
Choose Add Repository
Point it at the correct url → http://betas.qnx.com/net_ddk/
Disable/Uncheck the box → Use anonymous login
Enter
Username → ddkbeta
Password → ddkbeta
Install the software !!

You will have to agree to the Click-Thru beta agreement to install this
software.

Happy beta testing !!

thanx
ben
QA
QSS

Jalaja · February 26, 2001, 8:54pm

But When I do this, it gives parsing error in .qrm files. am unable to
Install them!!!

“Brian Northgrave” <ben@qnx.com> wrote in message
news:96c7le$kdi$2@nntp.qnx.com…

Tue Feb 13 2001 - Network Driver Development Kit Now in Beta !!!

The Network Driver Development Beta Package is now available at the
following
location:

http://betas.qnx.com/net_ddk/

username: ddkbeta
passwd : ddkbeta

Simply add this repository and point it at the correct url,
then enable userid & passwd.

Start the Package Manager

Choose Add Repository

Point it at the correct url → > http://betas.qnx.com/net_ddk/

Disable/Uncheck the box → Use anonymous login

Enter
Username → ddkbeta
Password → ddkbeta

Install the software !!

You will have to agree to the Click-Thru beta agreement to install this
software.

Happy beta testing !!

thanx
ben
QA
QSS

Brian_Northgrave · February 26, 2001, 9:22pm

Driver Development Kits Moved !!!

Please Read the Posting if you are having problems downloading.
NB The Repository has moved !!!

The DDK packages have all been put into the same repository, so if you were
having problems downloading the original url please try the new one.

Sorry for the inconvenience.

All of the Driver Development Beta Packages are now available at the following
location:

http://betas.qnx.com/ddk/

username: ddkbeta
passwd : ddkbeta

Simply add this repository and point it at the correct url,
then enable userid & passwd.

Start the Package Manager
Choose Add Repository
Point it at the correct url → http://betas.qnx.com/ddk/
Disable/Uncheck the box → Use anonymous login
Enter
Username → ddkbeta
Password → ddkbeta
Install the software !!

You will have to agree to the Click-Thru beta agreement to install this
software.

Alain_Bonnefoy2 · February 27, 2001, 6:32am

Brian Northgrave a écrit :

Driver Development Kits Moved !!!

Please Read the Posting if you are having problems downloading.
NB The Repository has moved !!!

The DDK packages have all been put into the same repository, so if you were
having problems downloading the original url please try the new one.

Sorry for the inconvenience.

All of the Driver Development Beta Packages are now available at the following
location:

http://betas.qnx.com/ddk/

username: ddkbeta
passwd : ddkbeta

Simply add this repository and point it at the correct url,
then enable userid & passwd.

Start the Package Manager

Choose Add Repository

Point it at the correct url → > http://betas.qnx.com/ddk/

Disable/Uncheck the box → Use anonymous login

Enter
Username → ddkbeta
Password → ddkbeta

Install the software !!

You will have to agree to the Click-Thru beta agreement to install this
software.

??!!??

First, it’s the same address as before!
Second, same, I cannot reach the server!

Alain.

Glenn_Davidson1 · February 27, 2001, 3:59pm

I must agree that there is still something wrong with the setup of this repository.
I made the required change for the new location and still no go.

I had to download all the files using ftp to create a local copy of the repository
in order to access it.

Maybe when enough people confirm that there is a problem someone will
actually try to duplicate the problem and fix it.

Alain Bonnefoy wrote:

Brian Northgrave a écrit :

Driver Development Kits Moved !!!

Please Read the Posting if you are having problems downloading.
NB The Repository has moved !!!

The DDK packages have all been put into the same repository, so if you were
having problems downloading the original url please try the new one.

Sorry for the inconvenience.

All of the Driver Development Beta Packages are now available at the following
location:

http://betas.qnx.com/ddk/

username: ddkbeta
passwd : ddkbeta

Simply add this repository and point it at the correct url,
then enable userid & passwd.

Start the Package Manager

Choose Add Repository

Point it at the correct url → > http://betas.qnx.com/ddk/

Disable/Uncheck the box → Use anonymous login

Enter
Username → ddkbeta
Password → ddkbeta

Install the software !!

You will have to agree to the Click-Thru beta agreement to install this
software.

??!!??

First, it’s the same address as before!
Second, same, I cannot reach the server!

Alain.

–

–
Glenn Davidson || Phone: (902)492-4780
Satlantic Inc., Richmond Terminal, Pier 9 || Fax: (902)492-4781
3295 Barrington St., Halifax, NS, Canada |*| E-mail: glenn@satlantic.com

Larry_Brigman · February 27, 2001, 11:28pm

I got through with the info provided. I finally looked at the file the package manager

spit out as an error.
It’s in HTML!!! and it told me that I had a bad user id or password.
I went back and looked at my setup for the repository and sure enough I
had keyed in some info wrong. I updated it and everything else went just fine.

Glenn Davidson wrote:

I must agree that there is still something wrong with the setup of this repository.
I made the required change for the new location and still no go.

I had to download all the files using ftp to create a local copy of the repository
in order to access it.

Maybe when enough people confirm that there is a problem someone will
actually try to duplicate the problem and fix it. >

Alain Bonnefoy wrote:

Brian Northgrave a écrit :

Driver Development Kits Moved !!!

Please Read the Posting if you are having problems downloading.
NB The Repository has moved !!!

The DDK packages have all been put into the same repository, so if you were
having problems downloading the original url please try the new one.

Sorry for the inconvenience.

All of the Driver Development Beta Packages are now available at the following
location:

http://betas.qnx.com/ddk/

username: ddkbeta
passwd : ddkbeta

Simply add this repository and point it at the correct url,
then enable userid & passwd.

Start the Package Manager

Choose Add Repository

Point it at the correct url → > http://betas.qnx.com/ddk/

Disable/Uncheck the box → Use anonymous login

Enter
Username → ddkbeta
Password → ddkbeta

Install the software !!

You will have to agree to the Click-Thru beta agreement to install this
software.

??!!??

First, it’s the same address as before!
Second, same, I cannot reach the server!

Alain.

–

–
Glenn Davidson || Phone: (902)492-4780
Satlantic Inc., Richmond Terminal, Pier 9 || Fax: (902)492-4781
3295 Barrington St., Halifax, NS, Canada |*| E-mail: > glenn@satlantic.com

Mitchell_Schoenbrun · March 30, 2001, 6:31pm

Well first of all, this is not the right newsgroup. You should
post this in qdn.public.qnx4 instead. That said, you can
setup a network with two nodes. Here are some steps you will
need to take.

Setup the hardware
Make sure that your boot files are setup to have two different and
consecutive node numbers, preferably 1 and 2
Install both licenses on both nodes
Create an /etc/netmap file
Run “nettrap” to configure and start Net and your Net.driver programs
Run nameloc on each node
Run “netmap -f” to load the netmap file

To do 4) you may have to run your drivers in -v mode to get their MAC
addresses.

Previously, Gustavo wrote in qdn.public.ddk.network:

I have two licenses for qnx4.24, each one of them for a network node
only. Making use only of these licenses, I can assemble a network qnx?
Somebody can help me?

Gustavo.

Mitchell Schoenbrun --------- maschoen@pobox.com

Gustavo · March 30, 2001, 7:45pm

I have two licenses for qnx4.24, each one of them for a network node
only. Making use only of these licenses, I can assemble a network qnx?
Somebody can help me?

Gustavo.

Hans_J_Lund · September 25, 2001, 11:43am

Hello

Are som her that can help me with this:
My PCMCIA TrendWare TE100-PCBUSR card
is not working om my THOSHIBA 1690CDT
witch driver can i use and whay can QNX RTD 6.0
not find this device ??

Regards Hans Lund

QNX2 · November 1, 2001, 3:35am

Hi
Can somebody tell me how IP communicates the nexthop address to ip_en
for ARP resolution. This will be the case for all IP packets which are
destined to a non-directly connected networks.

Thanks,
Arkesh

QNX2 · November 1, 2001, 3:37am

Hi
Is there a way of finding out interface names and associated IP
addresses, if I am not using the IP module.

Thanks
Arkesh

Xiaodan_Tang1 · November 1, 2001, 4:54am

QNX <spamme@despammed.com> wrote:

Hi
Can somebody tell me how IP communicates the nexthop address to ip_en
for ARP resolution. This will be the case for all IP packets which are
destined to a non-directly connected networks.

Good eye

Yes, that is passed down as the “inter-module” member in npkt,
it’s 4 byte stands for the nexthop’s IP.

-xtang

Xiaodan_Tang1 · November 1, 2001, 4:59am

QNX <spamme@despammed.com> wrote:

Hi
Is there a way of finding out interface names and associated IP
addresses, if I am not using the IP module.

Not sure about your question. But,

if you are a module inside io-net, you could get the “advertise”
packet from driver, so you know the interface name, and it’s
cell/endpoint/iface.

If there is an IP assigned to that IP, then you will receive a
ADDR_ADD message, you could match the cell/endpoint/iface, so
you know which interface get assigned.

If you are talking about get this from outside of io-net, look
into SIOCGIFADDR

-xtang

Tony_Lee · March 8, 2002, 7:39pm

I sent this post to the wrong group. Maybe I’ll have better luck withthe
ddk.network.

Does (will) io-net infrastructure support TCP/UDP “HW checksum offload”
that is embedded in ethernet chip such as 82559 or newer gige ethernet
chip?

If not, how will QNX keep up to the performance/cpu usage in
Linux, NT, BSD world, especially for gige ethernet.

-Tony
Nokia Networks.

Sean_Boudreau1 · March 8, 2002, 8:07pm

Tony Lee <tl_168168@hotmail.com> wrote:
: I sent this post to the wrong group. Maybe I’ll have better luck withthe
: ddk.network.

It doesn’t currently. I suspect it will, although you should contact
your sales rep for anything official.

-seanb

:> Does (will) io-net infrastructure support TCP/UDP “HW checksum offload”
:> that is embedded in ethernet chip such as 82559 or newer gige ethernet
: chip?
:>
:> If not, how will QNX keep up to the performance/cpu usage in
:> Linux, NT, BSD world, especially for gige ethernet.
:>
:>
:> -Tony
:> Nokia Networks.
:>
:>