SOCKET Programming Trouble
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.
Fast/Flexible Linux OS Recovery
On Demand Now
Join Linux Journal's Shawn Powers and David Huffman, President/CEO, Storix, Inc.
Free to Linux Journal readers.Register Now!
- Download "Linux Management with Red Hat Satellite: Measuring Business Impact and ROI"
- July 2016 Issue of Linux Journal
- Client-Side Performance
- Tibbo Technology's Tibbo Project System
- Libarchive Security Flaw Discovered
- Sony Settles in Linux Battle
- Peppermint 7 Released
- Profiles and RC Files
- Snappy Moves to New Platforms
- The Giant Zero, Part 0.x
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide