If not only one module

QNX Newsgroups (Archives) qdn.public.ddk.network
1

<!doctype html public “-//w3c//dtd html 4.0 transitional//en”>

Some little (or maybe trvial) questions.

If I have two modules(converter or producer) which register the same bottom paket type,
then who will get the up-ward paket?
for example, if there are two en-ip converter loaded, and en0 transfer up a ethernet paket. Then which converter will receive this paket?

And when I view the files at /dev/io-net, some of them are tailed with the digital (e.g. en0, ip0), but some are not(e.g. ip_ppp).
Can I assign it when I load/register the module?
I guess that the filter and producer will be tailed with the digita, but the converter will not. Is it right?

Thanks.

2

You can’t have two convertors that convert between the same two
types: for example, only one ip_en. That’s why they aren’t
numbered. Producers and filters are assigned the lowest unused
number at the time they register.

-seanb

Codante <codantee@hotmail.com> wrote:
: <!doctype html public “-//w3c//dtd html 4.0 transitional//en”>
:
: Some little (or maybe trvial) questions.
:

If I have two modules(converter or producer) which register the same
: bottom paket type,
:
then who will get the up-ward paket?
:
for example, if there are two en-ip converter loaded, and en0 transfer
: up a ethernet paket. Then which converter will receive this paket?
:

And when I view the files at /dev/io-net, some of them are tailed with
: the digital (e.g. en0, ip0), but some are not(e.g. ip_ppp).
:
Can I assign it when I load/register the module?
:
I guess that the filter and producer will be tailed with the digita,
: but the converter will not. Is it right?
:

Thanks.

3

Codante <codantee@hotmail.com> wrote in
news:3C91F266.A67CAEAD@hotmail.com:

!doctype html public “-//w3c//dtd html 4.0 transitional//en”
html
Some little (or maybe trvial) questions.
p>If I have two modules(converter or producer) which register the same
bottom paket type,
br>then who will get the up-ward paket?
br>for example, if there are two en-ip converter loaded, and en0
transfer up a ethernet paket. Then which converter will receive this
paket?

And when I view the files at /dev/io-net, some of them are
tailed with the digital (e.g. en0, ip0), but some are not(e.g. ip_ppp).
br>Can I assign it when I load/register the module?
br>I guess that the filter and producer will be tailed with the
digita, but the converter will not. Is it right?
p>Thanks.</html

You can’t have two converters of the same (ie en->ip) at the same time.
You could have two converters, like en->ip and en->xyz. In that case, io-
net would give the packet from the en producer to the filter which matched
the en type it wants (which I suppose could be all packets).

\

Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>

4

<!doctype html public “-//w3c//dtd html 4.0 transitional//en”>

Thanks for the information,
however, although converters can't have the same type, it seems that they still can receive the same packet.
for example,
the ip_en converter and the ppp_en converter are different, but their bottem type are the same.
(especially when both them register the pattern of received packet with _BYTE_PAT_ALL)
or
if there are (ip_en converter) and (ip_ppp converter + ppp producer + ppp_en converter) on the same computer.
The ip producer transmits a packet down, then which path will be selected?

I'm just confused by these kind of conditions. What principle does io-net use?
 

Adam Mallory wrote:

Codante <> wrote in
news:<3C91F266.A67CAEAD@hotmail.com>:

>
>
> Some little (or maybe trvial) questions.
>

If I have two modules(converter or producer) which register the same
> bottom paket type,
>
then who will get the up-ward paket?
>
for example, if there are two en-ip converter loaded, and en0
> transfer up a ethernet paket. Then which converter will receive this
> paket?

And when I view the files at /dev/io-net, some of them are
> tailed with the digital (e.g. en0, ip0), but some are not(e.g. ip_ppp).
>
Can I assign it when I load/register the module?
>
I guess that the filter and producer will be tailed with the
> digita, but the converter will not. Is it right?
>

Thanks.

You can't have two converters of the same (ie en->ip) at the same time.
You could have two converters, like en->ip and en->xyz. In that case, io-
net would give the packet from the en producer to the filter which matched
the en type it wants (which I suppose could be all packets).

--
Cheers,
  Adam

  QNX Software Systems Ltd.
  [ ]
  ---------------------------------------------------
  With a PC, I always felt limited by the software available.
  On Unix, I am limited only by my knowledge.
      --Peter J. Schoenster <>

5

Codante <codantee@hotmail.com> wrote in
news:3C97201B.89C21423@hotmail.com:

br>however, although converters can’t have the same type, it seems
that they still can receive the same packet.
br>for example,
br>the ip_en converter and the ppp_en converter are different, but
their bottem type are the same.

Sure you can have an en->ip converter and an en->xyz converter.

br>The ip producer transmits a packet down, then which path will be
selected?

I’m just confused by these kind of conditions. What
principle does io-net use?

If you had two converters which converted ip->en and ip->xyz, then each
would get a copy (one after the other has finished AFAIK).


\

Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>

6

Adam Mallory <amallory@qnx.com> wrote:
: Codante <codantee@hotmail.com> wrote in
: news:3C97201B.89C21423@hotmail.com:

:>
however, although converters can’t have the same type, it seems
:> that they still can receive the same packet.
:>
for example,
:>
the ip_en converter and the ppp_en converter are different, but
:> their bottem type are the same.

: Sure you can have an en->ip converter and an en->xyz converter.

:>
The ip producer transmits a packet down, then which path will be
:> selected?

I’m just confused by these kind of conditions. What
:> principle does io-net use?

: If you had two converters which converted ip->en and ip->xyz, then each
: would get a copy (one after the other has finished AFAIK).


This is where the reg_byte_pat comes into play. If they’ve both
registered for the same packets, they both get them. ip_en
registers for arp and ip packets.

-seanb

7

Sean Boudreau wrote:

Adam Mallory <> amallory@qnx.com> > wrote:
: Codante <> codantee@hotmail.com> > wrote in
: news:> 3C97201B.89C21423@hotmail.com> :

:>
however, although converters can’t have the same type, it seems
:> that they still can receive the same packet.
:>
for example,
:>
the ip_en converter and the ppp_en converter are different, but
:> their bottem type are the same.

: Sure you can have an en->ip converter and an en->xyz converter.

:>
The ip producer transmits a packet down, then which path will be
:> selected?

I’m just confused by these kind of conditions. What
:> principle does io-net use?

: If you had two converters which converted ip->en and ip->xyz, then each
: would get a copy (one after the other has finished AFAIK).

Yes, this is my question.
Does it mean that they got their own packets but not the same link?

This is where the reg_byte_pat comes into play. If they’ve both
registered for the same packets, they both get them. ip_en
registers for arp and ip packets.
-seanb

The reg_byte_pat handles the up-ward packets but not down-packets.
Is there any way to decide the down-ward path?

Thanks.

8

Codante <codantee@hotmail.com> wrote:

: Sean Boudreau wrote:
:>
:> Adam Mallory <amallory@qnx.com> wrote:
:> : Codante <codantee@hotmail.com> wrote in
:> : news:3C97201B.89C21423@hotmail.com:
:>
:> :>
however, although converters can’t have the same type, it seems
:> :> that they still can receive the same packet.
:> :>
for example,
:> :>
the ip_en converter and the ppp_en converter are different, but
:> :> their bottem type are the same.
:>
:> : Sure you can have an en->ip converter and an en->xyz converter.
:>
:> :>
The ip producer transmits a packet down, then which path will be
:> :> selected?

I’m just confused by these kind of conditions. What
:> :> principle does io-net use?
:>
:> : If you had two converters which converted ip->en and ip->xyz, then each
:> : would get a copy (one after the other has finished AFAIK).

: Yes, this is my question.
: Does it mean that they got their own packets but not the same link?

:> This is where the reg_byte_pat comes into play. If they’ve both
:> registered for the same packets, they both get them. ip_en
:> registers for arp and ip packets.
:> -seanb

: The reg_byte_pat handles the up-ward packets but not down-packets.
: Is there any way to decide the down-ward path?


Done headed packets are sent to a specific npkt->cell, npkt->endpoint.
All ethernet (for example) are in the same cell so if a down producer
of ip packets is targeting ethernet, only the ip<->en convertor will get
it.

-seanb

9

Thanks for your answer :slight_smile:

Sean Boudreau wrote:

Codante <> codantee@hotmail.com> > wrote:

: Sean Boudreau wrote:
:
:> Adam Mallory <> amallory@qnx.com> > wrote:
:> : Codante <> codantee@hotmail.com> > wrote in
:> : news:> 3C97201B.89C21423@hotmail.com> :
:
:> :>
however, although converters can’t have the same type, it seems
:> :> that they still can receive the same packet.
:> :>
for example,
:> :>
the ip_en converter and the ppp_en converter are different, but
:> :> their bottem type are the same.
:
:> : Sure you can have an en->ip converter and an en->xyz converter.
:
:> :>
The ip producer transmits a packet down, then which path will be
:> :> selected?

I’m just confused by these kind of conditions. What
:> :> principle does io-net use?
:
:> : If you had two converters which converted ip->en and ip->xyz, then each
:> : would get a copy (one after the other has finished AFAIK).

: Yes, this is my question.
: Does it mean that they got their own packets but not the same link?

:> This is where the reg_byte_pat comes into play. If they’ve both
:> registered for the same packets, they both get them. ip_en
:> registers for arp and ip packets.
:> -seanb

: The reg_byte_pat handles the up-ward packets but not down-packets.
: Is there any way to decide the down-ward path?

Done headed packets are sent to a specific npkt->cell, npkt->endpoint.
All ethernet (for example) are in the same cell so if a down producer
of ip packets is targeting ethernet, only the ip<->en convertor will get
it.

-seanb