Qeltaras wrote:
Jan wrote:
the ETH_P_CUST is 0x6006
Oh, I see, ETH_P_CUST is not just some custom protocol, it's officially
defined by DEC. So you depend on this value, don't you?
in 16bit is 1632.
if I increse the MAX_RT_PROTOCOLS I define if 1632?
Oky, but for Implementing the ETH_P_CUST can I do?
Well, ETH_P_CUST collides with ETH_P_ARP (0x0806). Increasing
MAX_RT_PROTOCOLS will not help you until you select 12 bits, i.e. 4096
protocols - that's likely too large.
Take a look at stack/stack_mgr.c to see how hashing currently works in
RTnet. You may either patch the hashing to your needs (select some
high-nibble bits as additional key component) or extend the protocol
management with a list of handlers that can be registered on the same
hash key.
So far, this was not necessary for RTnet applications because they are
typically used in closed networks with self-defined protocols where you
can avoid collisions. Patches are always welcome!
I try to change the prtocol, using the protocol ETH_P_802_3 standard
ethernet protocol, but on my system I make 2 socket, 1 socket for
If you are actually free to select a protocol, you are also not bound to
the ETH_P_xxx defines - you can pick any number (which is not used and
which does not collide with some hash key of course).
transmission and 1 for receive, the error is only during the second
creation socket...
I don't understend why...
You don't need separate sockets for reception and transmission. But if
you want to separate them, use different protocol IDs with socket_rt.
RTnet does not allow to open the same protocol multiple times.
Jan
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users
