Can't connect behind university firewall

Support
1

I’m having issues connecting behind a university firewall. My laptop is behind the firewall trying to connect to a Raspberry pi on my home network. The connection has no problems when the laptop and Pi are both on the home network.

Some possible culprits from the log after enabling dialar and connections:

Jan 25 10:30:20 mars syncthing[10670]: [K32AQ] 2018/01/25 10:30:20.371074 structs.go:195: DEBUG: dialing <snip> kcp://<snip> prio 50
Jan 25 10:30:20 mars syncthing[10670]: [K32AQ] 2018/01/25 10:30:20.371161 kcp_dial.go:42: DEBUG: dial kcp://<snip> using existing conn on [::]:22020
Jan 25 10:30:20 mars syncthing[10670]: [K32AQ] 2018/01/25 10:30:20.371265 structs.go:195: DEBUG: dialing <snip> kcp://<snip>:22020 prio 50
Jan 25 10:30:20 mars syncthing[10670]: [K32AQ] 2018/01/25 10:30:20.371370 kcp_dial.go:42: DEBUG: dial kcp://<snip>:22020 using existing conn on [::]:22020
Jan 25 10:30:30 mars syncthing[10670]: [K32AQ] 2018/01/25 10:30:30.371603 structs.go:198: DEBUG: dialing <snip> kcp://<snip> error: i/o timeout

[...]

Jan 25 10:30:30 mars syncthing[10670]: [K32AQ] 2018/01/25 10:30:30.372050 structs.go:195: DEBUG: dialing <snip> relay://<snip>&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=relay prio 200
Jan 25 10:30:30 mars syncthing[10670]: [K32AQ] 2018/01/25 10:30:30.586046 relay_dial.go:48: DEBUG: Dial (BEP/relay): setting traffic class: setsockopt: protocol not available

[...]

Jan 25 10:34:02 mars syncthing[10670]: [K32AQ] 2018/01/25 10:34:02.459261 service.go:351: DEBUG: Not dialing relay://<snip>&pingInterval=1m0s&networkTimeout=2m0s&sessionLimitBps=0&globalLimitBps=0&statusAddr=:22070&providedBy=relay as sleep is 24s, next dial is at 2018-01-25 10:40:20.370413924 -0600 CST m=+2000.929993709 and current time is 2018-01-25 10:34:02.458554572 -0600 CST m=+1623.018134370
2

This doesn’t look like the full log, but anyway, it might be that your university requires a proxy or limits traffic only on certain ports, in which case syncthing might not be able to work around that.

3

It’s the DEBUG: Dial (BEP/relay): setting traffic class: setsockopt: protocol not available which caught my eye on IRC.

I was also thinking, if a connection to a proxy on a particular port fails, would it make sense to make sure that the next proxy that’s tried is running on a different port?

1 Like
4

Could it be possible to run a relay with commonly allowed port reassigned to syncthink 's job ? http, https …

5

This os trying to set traffic class and failing, its not relevant.

6

People already do that yet if you are only allowed to access http via a http proxy, this won’t help as relay server does not talk http.

1 Like
7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.