Re: TCPIP programming (sockaddr_in question)
- From: "Richard Maher" <maher_rj@xxxxxxxxxxxxxxxxxx>
- Date: Thu, 24 May 2007 12:03:42 +0800
Hi Brian,
Well, the "some software" would be TCP/IP services. When testing this,the
bg device was associated with a telnet session.
Hey, me too (Specifically Telnet); I wonder why?
This is what I get with a show service on telnet: -
Flags: Listen Rtty IPv6
I don't seem to have a description in the ucx help for /FLAGS=IPv6 or
/PROTOCOL=Family=V6 on my version so I assume that you can somehow
communicate the fact that you want the Auxillary Server to listen on an
INET6 socket so that all the progeny get IPv6 capabilities.
Why would I do 2 $QIOs when I need only one. I've been calling the $QIOand
passing a descriptor pointing to ample space to contain the IPv6sockaddr_in
structure. There are several ways available to determine what wasreturned
and to parse out the data I desire.
I was about to say "So you can at least get the bloody port number for the
v4 devices" but then I checked, and my Telnet BG devices *are* returning the
correct port number, so you're probably wondering what I'm babbling on
about. Then I realized that I'd been looking at the client-side BG devices
(I'm testing with client and server on the same box) and 'cos they're all
connecting to port 1024 or "0004" in network byte order that's why I was
constantly getting a perfectly reasonable port_number, Doh!
I still think the fact that you can get a IPv6 Socket back without the
io$m_extend is a buglet, but in the abscence of differing behaviour in
Multinet or TCPWare, who cares? I'll stop taking up your time now :-)
LOL! :)Yeah, but you just know that there are those who never laugh at such things.
(Makes it all worthwhile really :-)
Cheers Richard Maher
<VAXman- @SendSpamHere.ORG> wrote in message
news:00A6810C.37D24202@xxxxxxxxxxxxxxxxxxx
In article <f32m99$3q$1@xxxxxxxxxxxxxxxxxxxxxxxxxx>, "Richard Maher"<maher_rj@xxxxxxxxxxxxxxxxxx> writes:
using
Hi Brian,
My best guess is that some software on your box is creating a socket
outthe address family AF_INET6. Why someone uses IPV6 (apart from running
theof addresses) I don't know. New Multicast stuff? Something else wiz-bang?
Well, the "some software" would be TCP/IP services. When testing this,
bg device was associated with a telnet session.up
Why not try this: -
Use the normal 16 byte IPv4 sockaddr structure and if the first word ends
it"26" the do a <io$_sensemode!io$m_extend> with the 28 byte structure. (At
that stage can you dump out the owner of the BG device so we can see who
thenis and what software they're running?) If you manage to retrieve the Port
Number then please let me know. Actually, if your observations and
experiences vary *at all* from what I described in the previous reply
andplease let us all know.
Why would I do 2 $QIOs when I need only one. I've been calling the $QIO
passing a descriptor pointing to ample space to contain the IPv6sockaddr_in
structure. There are several ways available to determine what wasreturned
and to parse out the data I desire.at
From what I think I've seen, I still say it's a bug. John G is too quiet
VAXman(at)TMESIS(dot)COMthe moment considering he gets up hours before me and, once Bootcamp
winds-up, I think Matt goes on the after-dinner circuit promoting his new
book "Deadlines - Smedlines" so I don't expect to hear much from that
direction :-)
LOL! :)
--
VAXman- A Bored Certified VMS Kernel Mode Hacker
"Well my son, life is like a beanstalk, isn't it?"
.
- Follow-Ups:
- Re: TCPIP programming (sockaddr_in question)
- From: Richard Whalen
- Re: TCPIP programming (sockaddr_in question)
- References:
- Re: TCPIP programming (sockaddr_in question)
- From: John Gemignani, Jr.
- Re: TCPIP programming (sockaddr_in question)
- From: Richard Maher
- Re: TCPIP programming (sockaddr_in question)
- From: Richard Maher
- Re: TCPIP programming (sockaddr_in question)
- Prev by Date: Re: World's Fastest Processor? For Now, Anyway
- Next by Date: Re: Replacing LAT terminal servers
- Previous by thread: Re: TCPIP programming (sockaddr_in question)
- Next by thread: Re: TCPIP programming (sockaddr_in question)
- Index(es):
Relevant Pages
|