Hi all!

I'm doing some simple server/client based socket progs in C. My problem is that the sending routine uses the protocol family PF_PACKET -> with SOCK_DGRAM, IPPROTO_UDP so i made some own cooked frames and send them with sendto(). I' have monitored them with tcpdump, the packet arrives, the ip sum is ok the udp socket too.

The in the receiver routine is PF_INET, SOCK_DGRAM, IPPROTO_UDP the socket is binded to the proper device and never becomes readable.... WHY??????????? tcpdump sees that the packet is arrived the dest address and port are ok, but the socket never becomes readable...

Is someone have practice in this kind of solution?????

so once again i must send with PF_PACKET (because of some ehternet broadcast features) and must receive with PF_INET.

thx sodja
__________________________

Post new comment

Please note that comments may not appear immediately, so there is no need to repost your comment.
The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <pre> <ul> <ol> <li> <dl> <dt> <dd> <i> <b>
  • Lines and paragraphs break automatically.

More information about formatting options

Newsletter

Each week Linux Journal editors will tell you what's hot in the world of Linux. You will receive late breaking news, technical tips and tricks, and links to in-depth stories featured on www.linuxjournal.com.
Sign up for our Email Newsletter

Tech Tip Videos

From the Magazine

December 2009, #188

If last month's Infrastrucuture issue was too "big" for you then try on this month's Embedded issue. Find out how to use Player for programming mobile robots, build a humidity controller for your root cellar, find out how to reduce the boot time of your embedded system, and if you're new to embedded systems find out the basics that go into one. You can also read about the Beagle Board, the Mesh Potato and a spate of other interestingly named items. And along with our regular columns don't miss our new monthly column: Economy Size Geek.


Read this issue