(Illustration by Gaich Muramatsu)
On Tue, 9 May 2000, Jan Harkes wrote: > On Tue, May 09, 2000 at 01:02:39PM -0700, Chris Jantzen wrote: > server sends: > > [11:55:56]Main Process: "packet.c", line 110: rpc2_XmitPacket() > > Host.InetAddress = 10.1.0.5 Port.InetPortNumber = 1049 > > Prefix: BufferSize = 350 LengthOfPacket = 80 MagicNumber = 3247517 > > Q = 0x400ae3e8, RecvStamp = 0.000000 > > Header: ProtoVersion = 0x8 RemoteHandle = 0x3c3a368b > > LocalHandle = 0x1ed2b8c6 BodyLength = 20 SeqNumber = 0 > > Opcode = RPC2_INIT2 SEFlags = 0x0 SEDataOffset = 0 > > SubsysId = 627711488 ReturnCode = 0 Flags = 0x740000 > > Uniquefier = 542785141 Lamport = 3 TimeStamp = 590017755 BindTime = 0 > > client sees: > > [11:55:56]SocketListener: "packet.c", line 207: rpc2_RecvPacket() > > Packet received from Host.InetAddress = 10.1.0.3 > > Port.InetPortNumber = 370 > > Received packet.... > > Prefix: BufferSize = 4500 LengthOfPacket = 80 MagicNumber = 3247517 > > Q = 0x400c13e8, RecvStamp = 957898556.111736 > > Header: ProtoVersion = 0x8 RemoteHandle = 0x3c3a368b > > LocalHandle = 0x1ed2b8c6 BodyLength = 2416475831 > > SeqNumber = 1098622648 Opcode = 1878491477 SEFlags = 0x417ba6b8 > > SEDataOffset = 2416475811 SubsysId = 1678883000 > > ReturnCode = 2416475811 Flags = 0x740000 Uniquefier = 2958180566 > > Lamport = 1098622651 TimeStamp = 1649496675 BindTime = 2416475811 > > > The server sent an INIT2 packet with unencoded headers and the client > decided to decode it? Why does the rpc2 code rpc2_ApplyD function have: > > /* XXXXXXXXXXXXXXX this was at the beginning now moved */ > if (!(ntohl(pb->Header.Flags) & RPC2_ENCRYPTED)) > return; > > At the end of the decoding code??? WTF how did this ever work? > > Could you try moving that test back to the top of the function. > (rcp2/rpc2-src/secure.c:232) Ah, that seems to have worked. An unrelated issue, that hopefully somebody else on the mailing list can answer easily, as Jan seems to do so much himself (which I'm sure we all appreciate more than we say): I don't seem to be able to create any volumes. It seems my VLDB is not being created correctly? I ran the bld script and nothing seems to happen. This is all fresh from 5.3.7. Here's some interesting log snippets from /vice/db/SrvLog 16:19:17 VCheckVLDB: could not open VLDB 16:19:17 VInitVolPackage: no VLDB! Please create a new one. 16:19:59 VGetPartition Couldn't find partition /export/primary/vicepa/ 16:19:59 VCreateVolume: Cannot find partition /export/primary/vicepa/. Bailing out. 16:19:59 Unable to create the volume; aborted 16:19:59 create: volume creation failed for volume 1000001 16:19:59 status = (103) And, here's the createvol command line: /usr/local/sbin/createvol_rep MAYBE.NET E0000100 /export/primary/vicepa/ The 'partition' listed is what I put into vice-setup and is listed in vicetab as: ace /export/primary/vicepa ftree width=32,depth=4 (I hope I'm not spamming the mailing list too much, here.) Thanks for any input out there -- chris kb7rnl =->Received on 2000-05-09 19:55:35