rtnet-developers

[RTnet-developers] Documentation request

[Marcelo J c. <mjc...@cr...>]

Hi!

I want to implement raw sockets within RTnet. Do you have any
documentation not released that could help me on this?

Thanks!



DISCLAIMER: This message may contain confidential information or privileged material and is intended only for the individual(s) named. If you are not a named addressee and mistakenly received this message you should not copy or otherwise disseminate it: please delete this e-mail from your system and notify the sender immediately. E-mail transmissions are not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. Therefore, the sender does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmissions. Please request a hard copy version if verification is required. Critical Software.

[RTnet-developers] Documentation request

[Marcelo J c. <mjc...@cr...>]

Hi!

I want to implement raw sockets within RTnet. Do you have any
documentation not released that could help me on this?

Thanks!



DISCLAIMER: This message may contain confidential information or privileged material and is intended only for the individual(s) named. If you are not a named addressee and mistakenly received this message you should not copy or otherwise disseminate it: please delete this e-mail from your system and notify the sender immediately. E-mail transmissions are not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. Therefore, the sender does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmissions. Please request a hard copy version if verification is required. Critical Software.

Re: [RTnet-developers] Documentation request

[Jan K. <jan...@we...>]

Marcelo J coelho wrote:
> Hi!
>=20
> I want to implement raw sockets within RTnet. Do you have any
> documentation not released that could help me on this?

The most accurate doc has already been released: the code itself ;). If
you don't understand certain parts, simply ask. If you have some ideas
how to realise something, post even partial patches, this helps to
discuss pros and cons.

Jan

Re: [RTnet-developers] Documentation request

[Marcelo J c. <mjc...@cr...>]

Hi!


Well, for what i understood from your code, and documentation and
e-mail, i have to create a new protocol.

So i started writing raw.c, for posterior inclusion within stack/ipv4
folder.

What i started to do was trying to use udp and icmp to try to make a raw
protocol. I also have something from the kernel itself. My problem is
that my knowledge in low-level network protocols is a little tiny  :(  
and i'm trying to understand how these things are implemented.

So, am i starting it right?


Thanks for replies


Jan Kiszka wrote:
> Marcelo J coelho wrote:
>   
>> Hi!
>>
>> I want to implement raw sockets within RTnet. Do you have any
>> documentation not released that could help me on this?
>>     
>
> The most accurate doc has already been released: the code itself ;). If
> you don't understand certain parts, simply ask. If you have some ideas
> how to realise something, post even partial patches, this helps to
> discuss pros and cons.
>
> Jan
>
>   




DISCLAIMER: This message may contain confidential information or privileged material and is intended only for the individual(s) named. If you are not a named addressee and mistakenly received this message you should not copy or otherwise disseminate it: please delete this e-mail from your system and notify the sender immediately. E-mail transmissions are not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. Therefore, the sender does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmissions. Please request a hard copy version if verification is required. Critical Software.

Re: [RTnet-developers] Documentation request

[Jan K. <jan...@we...>]

Marcelo J coelho wrote:
> Hi!
>=20
>=20
> Well, for what i understood from your code, and documentation and
> e-mail, i have to create a new protocol.
>=20

Yep, a new protocol with respect to RTDM.

> So i started writing raw.c, for posterior inclusion within stack/ipv4
> folder.
>=20
> What i started to do was trying to use udp and icmp to try to make a ra=
w
> protocol. I also have something from the kernel itself. My problem is
> that my knowledge in low-level network protocols is a little tiny  :(  =

> and i'm trying to understand how these things are implemented.
>=20
> So, am i starting it right?
>=20

Generally, yes. linux/net/ipv4/raw.c will likely contain some helpful
code for a similar support under RTnet, but not all of that code will be
needed.

Maybe you should start with considering what functionality you most
urgently need from the new IP-SOCK_RAW interface, from the application
point of view. Then have a look at the involved functions under Linux
(e.g. raw_sendmsg for sending) and at similar functions for UDP and
packet sockets under RTnet. Try to understand the pattern, the usual
information flow, and adopt the Linux functions. Ask if details are uncle=
ar.

BTW, for the overall picture of RTnet's data flow, there is that ETFA
paper on the documentation page on www.rtnet.org.

Jan

Re: [RTnet-developers] Documentation request

[Marcelo J c. <mjc...@cr...>]

> Maybe you should start with considering what functionality you most
> urgently need from the new IP-SOCK_RAW interface, from the application
> point of view. Then have a look (...) and at similar functions for UDP and
> packet sockets under RTnet. Try to understand the pattern, the usual
> information flow, and adopt the Linux functions.
Should i follow the udp or icmp implementation more closely?



> BTW, for the overall picture of RTnet's data flow, there is that ETFA
> paper on the documentation page on www.rtnet.org.
>   
Already read it.  :)



DISCLAIMER: This message may contain confidential information or privileged material and is intended only for the individual(s) named. If you are not a named addressee and mistakenly received this message you should not copy or otherwise disseminate it: please delete this e-mail from your system and notify the sender immediately. E-mail transmissions are not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. Therefore, the sender does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmissions. Please request a hard copy version if verification is required. Critical Software.

Re: [RTnet-developers] Documentation request

[Jan K. <jan...@we...>]

Marcelo J coelho wrote:
>> Maybe you should start with considering what functionality you most
>> urgently need from the new IP-SOCK_RAW interface, from the application=

>> point of view. Then have a look (...) and at similar functions for UDP=
 and
>> packet sockets under RTnet. Try to understand the pattern, the usual
>> information flow, and adopt the Linux functions.
> Should i follow the udp or icmp implementation more closely?
>=20

UDP, ICMP is not directly exported to the user, especially not via RTDM.
Also that packet sockets are interesting, although they have nothing to
do with IP. They are simpler usage example than UDP/IP, and the data
flow should be easily to understand.

>=20
>=20
>> BTW, for the overall picture of RTnet's data flow, there is that ETFA
>> paper on the documentation page on www.rtnet.org.
>>  =20
> Already read it.  :)
>=20
>=20
>=20
> DISCLAIMER: This message may contain confidential information or privil=
eged material and is intended only for the individual(s) named. If you ar=
e not a named addressee and mistakenly received this message you should n=
ot copy or otherwise disseminate it: please delete this e-mail from your =
system and notify the sender immediately. E-mail transmissions are not gu=
aranteed to be secure or error-free as information could be intercepted, =
corrupted, lost, destroyed, arrive late or incomplete or contain viruses.=
 Therefore, the sender does not accept liability for any errors or omissi=
ons in the contents of this message that arise as a result of e-mail tran=
smissions. Please request a hard copy version if verification is required=
=2E Critical Software.

I guess there is nothing you can do about this footer when posting to
public lists, is it?

Jan

Re: [RTnet-developers] Documentation request

[Marcelo J c. <mjc...@cr...>]

Jan Kiszka wrote:
> Marcelo J coelho wrote:
>   
>>> Maybe you should start with considering what functionality you most
>>> urgently need from the new IP-SOCK_RAW interface, from the application
>>> point of view. Then have a look (...) and at similar functions for UDP and
>>> packet sockets under RTnet. Try to understand the pattern, the usual
>>> information flow, and adopt the Linux functions.
>>>       
>> Should i follow the udp or icmp implementation more closely?
>>
>>     
>
> UDP, ICMP is not directly exported to the user, especially not via RTDM.
> Also that packet sockets are interesting, although they have nothing to
> do with IP. They are simpler usage example than UDP/IP, and the data
> flow should be easily to understand.
>   
I didn't quite understand what you wanted to say. Should I use another
kind of example, is it?


> I guess there is nothing you can do about this footer when posting to
> public lists, is it?
>   
The only way is to use another e-mail (and gmail started to give me some
 problems.... :(    ).



DISCLAIMER: This message may contain confidential information or privileged material and is intended only for the individual(s) named. If you are not a named addressee and mistakenly received this message you should not copy or otherwise disseminate it: please delete this e-mail from your system and notify the sender immediately. E-mail transmissions are not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. Therefore, the sender does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmissions. Please request a hard copy version if verification is required. Critical Software.