Here is some more logs from the work(goaway) side. Cranky is my home system.
2013-06-27 13:36:11 tinc.vpn[1714]: Trying to connect to cranky (Y.Y.Y.Y port
656)
2013-06-27 13:36:16 tinc.vpn[1714]: Timeout from cranky (Y.Y.Y.Y port 656)
during authentication
2013-06-27 13:36:16 tinc.vpn[1714]: Could not set up a meta connection to cranky
2013-06-27 13:36:26 tinc.vpn[1714]: Trying to connect to cranky (Y.Y.Y.Y port
656)
2013-06-27 13:36:29 tinc.vpn[1714]: Connected to cranky (Y.Y.Y.Y port 656)
2013-06-27 13:36:29 tinc.vpn[1714]: Connection with cranky (Y.Y.Y.Y port 656)
activated
2013-06-27 13:36:54 tinc.vpn[1714]: Flushing 83 bytes to cranky (Y.Y.Y.Y port
656) would block
2013-06-27 13:36:54 tinc.vpn[1714]: Flushing 181 bytes to cranky (Y.Y.Y.Y port
656) would block
2013-06-27 13:36:54 tinc.vpn[1714]: Flushing 247 bytes to cranky (Y.Y.Y.Y port
656) would block
2013-06-27 13:36:54 tinc.vpn[1714]: Flushing 339 bytes to cranky (Y.Y.Y.Y port
656) would block
2013-06-27 13:36:54 tinc.vpn[1714]: Flushing 431 bytes to cranky (Y.Y.Y.Y port
656) would block
2013-06-27 13:36:54 tinc.vpn[1714]: Flushing 523 bytes to cranky (Y.Y.Y.Y port
656) would block
2013-06-27 13:36:54 tinc.vpn[1714]: Flushing 663 bytes to cranky (Y.Y.Y.Y port
656) would block
2013-06-27 13:36:55 tinc.vpn[1714]: Flushing 755 bytes to cranky (Y.Y.Y.Y port
656) would block
2013-06-27 13:36:55 tinc.vpn[1714]: Flushing 821 bytes to cranky (Y.Y.Y.Y port
656) would block
2013-06-27 13:36:55 tinc.vpn[1714]: Flushing 881 bytes to cranky (Y.Y.Y.Y port
656) would block
2013-06-27 13:36:55 tinc.vpn[1714]: Flushing 947 bytes to cranky (Y.Y.Y.Y port
656) would block
[Many of the above logs]
2013-06-27 13:37:01 tinc.vpn[1714]: cranky (Y.Y.Y.Y port 656) could not flush
for 7 seconds (14911 bytes remaining)
2013-06-27 13:37:01 tinc.vpn[1714]: Closing connection with cranky (Y.Y.Y.Y port
656)
2013-06-27 13:37:16 tinc.vpn[1714]: Trying to connect to cranky (Y.Y.Y.Y port
656):
My linux box will keep connected a great deal longer than my Mac. My linux
system will stay online for 10-15m before it dumps me. I've tried running
top on the remote machine and constantly pinging it to keep traffic flowing.
Doesn't seem to make a difference.
Thanks,
-Matt
On Jun 27, 2013, at 11:51 AM, Matthew Tolle <matt at night.com> wrote:
>
> Howdy,
>
> I've had tinc working great for over a year now. They just made some
network changes at work and now I'm only able to make a connection for a few
seconds(30) or so before I get a "Metadata socket read error". I
wan't to think that's some kind of firewall timeout thing but I'm
not sure. I have no control over the FW or network at work so I'm not clear
on what they changed. Here are some logs:
>
> Log level2:
> 2013-06-27 11:19:47 tinc[1166]: Connection with goaway (X.X.X.X port 53770)
activated
> 2013-06-27 11:20:10 tinc[1166]: Metadata socket read error for goaway
(X.X.X.X port 53770): Connection reset by peer
> 2013-06-27 11:20:10 tinc[1166]: Closing connection with goaway (X.X.X.X
port 53770)
> 2013-06-27 11:22:45 tinc[1166]: Connection from X.X.X.X port 59325
> 2013-06-27 11:22:45 tinc[1166]: Connection with goaway (X.X.X.X port 59325)
activated
> 2013-06-27 11:23:08 tinc[1166]: Metadata socket read error for goaway
(X.X.X.X port 59325): Connection reset by peer
> 2013-06-27 11:23:08 tinc[1166]: Closing connection with goaway (X.X.X.X
port 59325)
>
> The server at work(goaway) is behind a NAT so it makes the outgoing
connection to my static IP at home. My home system just waits for work to make
contact to setup the tunnel.
>
> I'm not sure what the Metadata socket read error means. I tried
searching it on this list but couldn't find anything that got answered.
>
> Suggestions?
>
> Thanks,
>
> -Matt
>
>
>
>