Bugs in IPX

Martijn van Oosterhout (v3100411@student.anu.edu.au)
Tue, 24 Nov 1998 00:29:02 +1100


I've been doing a little bit of coding in UDP and IPX recently
and found what I beleive are a few bugs (or at least oddities)

Tested in 2.0.36 / 2.1.127 / 2.1.129

1)
If you make a non-blocking datagram socket in both UDP and
IPX and then try to read from it, you get different (odd)
results. UDP simply binds the socket and then does a receive.

UDP: Resource temporarily unavailable
IPX: Transport endpoint is not connected

(Code is here: http://geocities.com/SiliconValley/Park/6083/test1.txt )

2)
Two more serious bugs are when opening a normal IPX socket and using
sendto straight away fails with EIO, because it isn't bound locally.
UDP simply binds it and then does the send.

Calling bind and then sending works fine, but you can't call
connect with the _same_ address. I beleive this is because it's
looking up network 0 in the routing table.

(Code is here: http://geocities.com/SiliconValley/Park/6083/test2.txt )

I have no internal network nor am I using SPX.

I can see some obvious fixes and would be willing to do a patch but
I am willing to defer to someone who has looked at the code for more
than 10 minutes.

I'm not subscribed (yet) so CCing any replies would be helpful.

Martijn van Oosterhout
Australia

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/