Sorry, it's not your bug. After your mail, I've made a simple C UDP client
on my PC that shows the same problem (UDP checksum wrong).
It's due to a default wrong configuration of the ethernet device. On default
the kernel leaves the checksum computation to the NIC, but
in my case this seems to can
what you describe is very strange, because the Android emulator is not
sending UDP packets itself, it's just using standard BSD sockets instead to
send datagrams. what happens in this case is the following:
a/ the program running in the emulator uses a socket interface to send
datagrams to a serve
I made a simple program in my linux box that intercept the udp packets sent
by Android emulator from the OUTPUT chain via ipq interface and QUEUE
target, recompute the UDP checksum field and reinject the packets in the
kernel queue.
Now the udp checksum seems correct from Wireshark, so I think is
Hi,
In detail I have a sip user agent inside the Android emulator that exchange
signalling data over an UDP socket to an Internet server.
>From Wireshark executed on the PC where run the emulator I see UDP packets
sent by my application from Android emulator marked with a wrong checksum.
The udp c
Hello Andrea,
can you clarify exactly what direction these datagrams flow ? and where
exactly you see these bad checksums.
it could be a bug in the internal router/firewall of the emulator, but I
need more detail to determine why.
On Tue, Jul 1, 2008 at 5:11 PM, Andrea Bernardi <[EMAIL PROTECTE
5 matches
Mail list logo
