Teamviewer Problem with PF 2.3 BETA
-
Cant connect with Teamviewer with the acutal PFsense 2.3 Beta. This was running without Problems with 2.2.6.
-
I just tried from my client laptop on the LAN of my pfSense 2.3-BETA system and successfully connected to other remote devices running TeamViewer (both full install and TV Host).
What combination is not working for you? -
Likewise. I have been running TV through a 2.3 firewall behind another 2.3 firewall without issue.
-
Thank you, for the fast checks.
There is a Hurricane Electric ipv6 tunnel on the pfsense
and the lan runs dual stack. I will check it tomorrow,
maybe this is the reason for the problem. -
I checked everything with PF 2.2.6 and 2.3 but my Teamviewer wont run. Without the pfsense
e.g. direct connection it works. Pfsense and Client runs under VMware Workstation connected via 3G Modem.
I don't know where the problem is. Maybe pf is unhappy with the Vmware environment. -
Latest teamviewer, works fine for me, 2.3 is on an ESXi 5.5 host, haven't seen issues with teamviewer not connecting.
-
Might try lowering MTU used on the lan. As that can cause weird connection issues for 'some' sites..
-
I tried lowering the MTU on WAN and LAN to 1492, enabled static port on NAT, disabled all IPV6 stuff.
Upgraded to latest Windows and PF 2.3 Versions. No success. Without PFsense - no problem to connect.This is the TeamViewer log, after the Hole Punching it cant reconnect.
2016/01/29 06:21:45.870 2448 3912 S0 Negotiating session encryption: client hello sent to XXXXXXXXXXXX, RSA key length = 2048
2016/01/29 06:21:45.870 2448 3912 S0 UDP: send handshake: ()
2016/01/29 06:21:45.886 2448 3924 S0 CProcessCommandHandlerKeepAliveClient[217]::ReceivedCmdBuddy(): CC=3 CT=38
2016/01/29 06:21:45.980 2448 3912 S0 CProcessCommandHandlerKeepAliveClient[217]::ReceivedCmdBuddy(): CC=3 CT=38
2016/01/29 06:21:45.995 2448 3936 S0 CProcessCommandHandlerKeepAliveClient[217]::ReceivedCmdBuddy(): CC=3 CT=38
2016/01/29 06:21:45.995 2448 3936 S0 CProcessCommandHandlerKeepAliveClient[217]::ReceivedCmdBuddy(): CC=3 CT=38
2016/01/29 06:21:46.027 2448 3936 S0 Negotiating session encryption: server hello received
2016/01/29 06:21:46.043 2448 3936 S0 Negotiating session encryption: client handshake sent
2016/01/29 06:21:46.152 2448 3912 S0 Negotiating session encryption: server handshake received, encryption established with AES key length 256
2016/01/29 06:21:46.183 2448 3936 S0 UDP: ProcessHandshake2: ()
2016/01/29 06:21:46.183 2448 3936 S0 Initializing transmission control v2
2016/01/29 06:21:46.183 2448 3936 S0 UDP: sending master pings …: ()
2016/01/29 06:21:46.245 2448 3936 S0 UDP: connectivity: a=XXXXXXXXXXXX p=20392 p=2141: ()
2016/01/29 06:21:46.245 2448 3936 S0 UDP: punching: ()
2016/01/29 06:21:46.245 2448 3936 S0 UDP: PingOK.RequestUDP: ()
2016/01/29 06:21:46.245 2448 3936 S0 UDP: send UDPFLOW_REQUESTUDP: ()
2016/01/29 06:21:46.417 2448 3936 S0 UDP: SendUDPPunches: ()
2016/01/29 06:21:46.542 2448 3936 S0 UDP: SendUDPPunches: ()
2016/01/29 06:21:46.542 3600 2072 G1 CLoginClient::AuthenticateClient()
2016/01/29 06:21:46.949 2448 3932 S0 CarrierReconnectLogic[219]::HandleReconnect(): Reconnect successful
2016/01/29 06:21:46.995 2448 3932 S0! TcpCarrier[219]::ProcessReconnectToSessionAnswer(): Reconnect failed with client XXXXXXXXXXXXXXXX
2016/01/29 06:21:46.995 2448 3932 S0 Carrier[219]::EndCarrierInternal(): ClientID: XXXXXXXXXXXX SupportsEndSession: 1, SupportsCCmd2: 1, SessionType_RoutingSession, SendQueue: 1 (0 Bytes), CurrentSendQueue: 0 (0 Bytes), SendCache: 10 (14000 Bytes)
2016/01/29 06:21:46.995 2448 3932 S0 CGatewaySession[219]::EndSession(): Session to XXXXXXXXXXX ended. Estimated capacity=0kBit/s, Latency=81ms
2016/01/29 06:21:46.995 2448 3932 S0 CSendCommandToMaster::SendBCommandToMaster: CC=3 CT=37
2016/01/29 06:21:46.995 2448 3932 S0 UDP: create udp connection was not successful: UdpHolePuncher shutting down: ()
2016/01/29 06:21:46.995 2448 3936 S0! RemoteSession[219]::AddRequestedCarrier(): request carrier UdpToPartner failed!
2016/01/29 06:21:46.995 2448 3936 S0! UdpConnection[323]: UDP statistics: nb=6
2016/01/29 06:21:47.011 3600 2072 G1 CLogin::run() leave
2016/01/29 06:21:47.011 3600 7988 G1! InterProcessBase::Receive_RouterTime() No clock.
2016/01/29 06:21:47.011 3600 7988 G1! InterProcessBase::Receive_RouterTime() No clock. -
"UDP: create udp connection was not successful: UdpHolePuncher shutting down: (*)"
Are you blocking UDP?
-
UDP is not blocked. The UDP Hole Punching Mechanism isnt working in my case.
I switched over to anydesk (instead of Teamviewer) and everything is working.Maybe this is a TeamViewer problem.
