Re: client not defined error

[Maribel Cosin <maribel.cosin@rediris.es>]

Giving more detailed information, this is the packets received from the
server:

arwen.rediris.es -> tais         TCP D=40004 S=60200 Syn Seq=1928751928
Len=0 Win=5840 Options=<mss 1460,sackOK,tstamp 2171739363 0,nop,wscale
2>
        tais -> arwen.rediris.es TCP D=60200 S=40004 Syn Ack=1928751929
Seq=4108423664 Len=0 Win=24616 Options=<nop,nop,tstamp 354201492
2171739363,nop,wscale 0,nop,nop,sackOK,mss 1460>
arwen.rediris.es -> tais         TCP D=40004 S=60200     Ack=4108423665
Seq=1928751929 Len=0 Win=1460 Options=<nop,nop,tstamp 2171739364
354201492>
arwen.rediris.es -> tais         TCP D=40004 S=60200     Ack=4108423665
Seq=1928751929 Len=39 Win=1460 Options=<nop,nop,tstamp 2171739364
354201492>
        tais -> arwen.rediris.es TCP D=60200 S=40004     Ack=1928751968
Seq=4108423665 Len=0 Win=24577 Options=<nop,nop,tstamp 354201492
2171739364>
arwen.rediris.es -> tais         TCP D=40004 S=60200     Ack=4108423665
Seq=1928751968 Len=242 Win=1460 Options=<nop,nop,tstamp 2171739365
354201492>
        tais -> arwen.rediris.es TCP D=60200 S=40004 Fin Ack=1928752210
Seq=4108423665 Len=0 Win=24616 Options=<nop,nop,tstamp 354201492
2171739365>
arwen.rediris.es -> tais         TCP D=40004 S=60200     Ack=4108423666
Seq=1928752210 Len=0 Win=1460 Options=<nop,nop,tstamp 2171739367
354201492>
        tais -> arwen.rediris.es TCP D=60200 S=40004 Rst Seq=4108423666
Len=0 Win=24616
arwen.rediris.es -> tais         TCP D=40004 S=60200     Ack=4108423666
Seq=1928752210 Len=39 Win=1460 Options=<nop,nop,tstamp 2171799432
354201492>


And the packets generated from the client:

12:56:47.869119 IP arwen.60200 > tais.rediris.es.40004: S
1928751928:1928751928(0) win 5840 <mss 1460,sackOK,timestamp 2171739363
0,nop,wscale 2>
12:56:47.869700 IP arwen.60200 > tais.rediris.es.40004: . ack 4108423665
win 1460 <nop,nop,timestamp 2171739364 354201492>
12:56:47.869804 IP arwen.60200 > tais.rediris.es.40004: P 0:39(39) ack 1
win 1460 <nop,nop,timestamp 2171739364 354201492>
12:56:47.870340 IP arwen.60200 > tais.rediris.es.40004: P 39:281(242)
ack 1 win 1460 <nop,nop,timestamp 2171739365 354201492>
12:56:47.872302 IP arwen.60200 > tais.rediris.es.40004: . ack 2 win 1460
<nop,nop,timestamp 2171739367 354201492>
12:57:47.928334 IP arwen.60200 > tais.rediris.es.40004: P 281:320(39)
ack 2 win 1460 <nop,nop,timestamp 2171799432 354201492>


Hope this help.


Regards,

Maribel.


El lun, 14-11-2005 a las 11:56 +0100, Maribel Cosin escribió:
> 
> Dear all,
> 
> 
> I have the same problem, but I have reviewed the connection between the
> server and the client and there is no filters that could throw away the
> packets. Maybe the reason could be the versions? The server is beacon
> 1.1.0 y the client is beacon 1.3.0.
> 
> Any idea?
> 
> Thanks in advance,
> 
> Maribel.
> 
> 
> >   "what exactly does a "client not defined" error indicate?
> >   i was unable to find any documenation on this error.  one of=20
> >   my beacon clients keeps doing this:
> > 
> >   client not defined
> >   Opening client connection
> > 
> >   thanks
> >   -b"
> >  
> > This means that your local Beacon was unable to successfully open a TCP
> > connection back to the Central Beacon Server you're pointing at in your
> > .../src/beacon.conf file.
> > 
> > Could be a firewall, could be a number of reasons, but the bottom line is
> > your Beacon says, "Hello?" to the Central Server, and gets no answer back.
> > 
> > Hope this helps!
> > 
> > Mitch
> > --
> > Mitch Kutzko | mitch@dast.nlanr.net | mitch@ncsa.uiuc.edu | 217-333-1199
> > Project: http://dast.nlanr.net  |  Personal: http://hobbes.ncsa.uiuc.edu 
> > 
> 
>