in reply to Socket problem

It might be helpful if you performed a regular, command line ping and sniffed the results. It should be a helpful diagnostic to see if the returned packet (from a different address) makes it back to the OS ping program. So if you see the returned packet in the sniffer, but the command-line ping program doesn't see it, then it could be the OS or some sort of resident firewall blocking it.

Replies are listed 'Best First'.
Re^2: Socket problem
by elLunes (Initiate) on Mar 06, 2007 at 20:20 UTC
    Hmmmm... That's what I thought. If I ping with the OS ping program and sniff the result it says, that regardless of what ip I ping, the router will answers with the address the packet was sent to. So, is there a possibility to bind the socket not to a certain address but instead to listen for certain traffic? Cheers elLunes
[reply]

In Section Seekers of Perl Wisdom