[volunteergrid2-l] storage node communication

[Theodore M. Rolle, Jr.]

Bottom line:
earney, cerezal: Will you send rosenkeller and me (timesoak) your
~/.tahoe.cfg file?  We're shooting a bug.  We've got it in the corner,
bloodied nose, begging for mercy.
timesoak exchanges packets with each of your nodes.  They just fly
by. :-)

Background:
I've tried a couple of things:

tahoe.cfg:
tub.port = 31416
tub.location set to the same.

In the channel, I found that ~/.tahoe/client.port should also have the
tub.port number.  Now that's some information!

...much later...
Wireshark reports that cerezal hits port 31416; rosenkeller doesn't.
There's a LOT of traffic between timesoak and cerezal.

cerezal -> timesoak: Src Port: 36504, Dst Port: xqosd (31416)
timesoak -> cerezal: Src Port: xqosd (31416), Dst Port: (36504) 36504)

earney.homedsn.org, same story.

rosenkeller.org only occasionally hits timesoak, probably because it
doesn't get any joy.  I'm listing the packet numbers so there's no
necessity to find them again. :-)
Packet 173, time: 126.557616
rosenkeller -> timesoak: Src Port: 42247 (42247), Dst Port: 47270
(47270)
Packet 174, time: 126.566105
timesoak -> rosenkeller: Src Port: 47270 (47270), Dst Port: 42247
(42247)
Packet 175, time: 126.688396
Good exchange.

rosenkeller -> timesoak: Src Port: 42247 (42247), Dst Port: 47270
(47270)
timesoak didn't send a return packet.

Packet 17815, time 2886.536458,
rosenkeller.org -> timesoak: Src Port: 42247 (42247), Dst Port: 47270
(47270)
Packet 17816, time 2886.552885
timesoak -> rosenkeller.org: Src Port: 47270 (47270), Dst Port: 42247
(42247)
Packet 17823, time: 2886.570566
Good exchange.

rosenkeller.org -> timesoak: Src Port: 42247 (42247), Dst Port: 47270
(47270)
timesoak didn't send a return packet.

It looks like rosenkeller isn't sending packets to port 31416.
And timesoak sometimes ignores packets.

Change one thing at a time philosophy:
Can you get rosenkeller to hit port 31416?
Then if timesoak still ignores rosenkeller, there's a problem at this
end, too.

All I want to do is get it fixed.
When I was a programmer, the corporate philosophy was to 'fix the blame,
then fix the problem.'  Isn't that absurd?

On Sat, 2012-03-24 at 18:58 +0100, Christoph Langguth wrote:
> On Sat, 24 Mar 2012 13:39:37 -0400, Theodore M. Rolle, Jr. wrote:
> > I'm definitely not offended!
> > How to fix it?
> >
> > Ted
> If only I knew, I would gladly tell you.
> The one thing that comes to my mind would be a firewall silently 
> dropping important packets.
> 
> But as far as I understood, this is exactly what Brian kindly proposed 
> to investigate. I would like to help if I could, but my Python skills 
> are minuscule, so I'm having a hard time understanding the internals of 
> Tahoe. So the only thing I can do is describe symptoms, but finding 
> causes or the cure is beyond me...
> 
> -- Chris
> _______________________________________________
> volunteergrid2-l mailing list
> volunteergrid2-l at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/volunteergrid2-l
> http://bigpig.org/twiki/bin/view/Main/WebHome

-- 
GPG/PGP public key: B07F9AAE