Hmmmm... I wonder, could those networking changes be responsible for my
copy of CIPE (an IP tunneling across UDP) not working? After upgrading to pre-31-5,
ciped fails with:
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 4
setsockopt(4, SOL_SOCKET, SO_RCVBUF, [65536], 4) = 0
bind(4, {sin_family=AF_INET, sin_port=htons(123),
sin_addr=inet_addr("206.4.67.2")}, 16) = 0
connect(4, {sin_family=AF_INET, sin_port=htons(123),
sin_addr=inet_addr("204.91.82.195")}, 16) = 0
getsockname(4, {sin_family=AF_INET, sin_port=htons(123),
sin_addr=inet_addr("206.4.67.2")}, [16]) = 0
ioctl(4, 0x89f1, 0xbffffbb8) = 0
ioctl(4, 0x89f2, 0xbffffbb8) = 0
ioctl(4, 0x89f3, 0xbffffbb8) = -1 ENOTCONN (Transport
endpoint is not connected)
It didn't exhibit this behavior in pre-31-3 ( I didn't even see a
pre-31-4 anyplace).
Since I'm far from being a network guru, could someone explain the
meaning of this error and perhaps point me in a direction (any
direction will do, it doesn't even have to be right :), I'll try to
figure it out myself.
------------------------------------------------------------------------------
Nicholas J. Leon <nicholas@binary9.net>
"Elegance through Simplicity" http://mrnick.binary9.net/
PGP:finger nicholas@neko.binary9.net Shinanyaku:[Chronx/War2/XvT]
------------------------------------------------------------------------------
SF/F Reading Suggestion #3: Magic of Recluse by L.E. Modesitt, Jr.
-- Please ignore the following addresses, they are intended to determine and catch bulk emailers that scan newsgroups and mailing lists.>> linux-kernel_vger.rutgers.edu@catcher.binary9.net >> linux-kernel_vger.rutgers.edu@catcher.binary9.net >> submit-linux-dev-kernel_transmeta.com@catcher.binary9.net