Re: [RTnet-users] Problem with protocol socket

Qeltaras wrote: 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

Re: [RTnet-users] Problem with protocol socket

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

Re: [RTnet-users] Problem with protocol socket

Qeltaras wrote: You likely ran into a hash key collision with your ETH_P_CUST protocol. RTnet uses a rather simple hash mechanism to demultiplex incoming Ethernet frames to the corresponding protocol handlers: the last n bits of the protocol ID select the slot, where n is currently 6 (there are

Re: [RTnet-users] Problem with protocol socket

Qeltaras wrote: I create the sochet with the functuin socket_rt sock = socket_rt( PF_PACKET, SOCK_DGRAM, htons( ETH_P_CUST)); the system returne: Socket error: -99 packet_if_rtai.o: init_module: Operation not permitted Hint: insmod errors can be caused by incorrect module parameters, includi

[RTnet-users] Problem with protocol socket

I create the sochet with the functuin socket_rt sock = socket_rt( PF_PACKET, SOCK_DGRAM, htons( ETH_P_CUST)); the system returne: Socket error: -99 packet_if_rtai.o: init_module: Operation not permitted Hint: insmod errors can be caused by incorrect module parameters, including invalid IO, or I