>This seems exactly correct behaviour according to RFC 1122, but missing
>in BSD. You are seeing
> writev()
> send to a port that isnt there
> <- ICMP UNREACH
> writev()
> ahah pending error
> report the error
*ROTFL*
just got myself a copy of the RFC, and yes - it's absolute normal
behaviour. x!!!%§"%%/?%%""§$&32 (wasted 1 1/2 days thinking
about possible errors...) ... porting an application to linux
and while testing never thought about setting up a listener bind()
process to that socket :)
anyway, seems like linux is - once again - way ahead in what
features it's implementing..., thumbs up everywhere.
by the way, don't want to annoy anybody here, but I looked
around in the ipv.4 sources and realized the behaviour.
What I didn't really understand is wether there
is another way to get hold of the icmp error or
is it correct to simply try to write() or writev() and
get that error?
thanks for the help
Christoph.
-- Christoph Moar (christoph.moar@mchp.siemens.de) Tel. (++49) 89 636-44628 SIEMENS AG Corporate Technology Fax. (++49) 89 636-47457 Information and Media Technology Office Adress: SIEMENS AG ZT IK 1, Otto-Hahn-Ring 6, D-81739 Munich Postal Adress: SIEMENS AG ZT IK 1, D-81730 Munich *** PGP PUBLIC KEY AVAILABLE ON REQUEST & ON KEY SERVERS WORLDWIDE ***