0

Strange network behaviour on several TG200s

Hello, we`re using several TG100s and TG200s in my company to just import voice calls to a PBX. The solution is terminating to a pfSense firewall with OpenVPN service running on it. With the TG100s we don`t have much of an issue, but the TG200s are just like hell...
Yesterday we did setup a new TG200 and it worked fine with one SIM card, calls were redirected, OpenVPN connection was established. After we shipped the box, it started behaving very strange and in the OpenVPN log of the pfSense (whose settings are intact for long ago and other simboxes are connected) there were numerous UNDEF connections and every new session was terminated with TLS handshake error (on the previous location, the VPN worked, no one touched the settings, there are certificates imported via openvpn.tar config bundle). It was with version 53.18.0.44, upgraded it to the latest 53.18.0.46 and it seems like this fixed the issue for this box.
The same issue I experienced with another TG200 V2 in my lab in the office - it was working for maybe a month or two and then suddenly it did the exactly same thing - many UNDEF connections and not able to create the OpenVPN connection...
I tried with several factory-resets - didn`t helped at all.
I`m having another TG200 V2 (again brand new) - opened it and tried to configure it from scratch - same result...
I set a real IP address and as a secondary I left 192.168.5.150/24 , enabled SSH, made the port to be 22 and tried to see if the box is pingable... but it`s only pingable from the local network and it can`t even ping its def. gateway - masks are correct, def GW address is correct, checked it several times... SSH is working with great delay on the box and when I issued ifconfig, it showed very strange broadcast address - 0.0.0.0 for both eth0 and eth0.2 (the secondary IP - 192.168.5.150...) Both boxes in my office are behaving the same and both are to with the latest firmware - 53.18.0.46 ...
Any suggestions? I tried to set the bcast address manually - it worked, but didn`t changed the situation at all...

0 comments

Please sign in to leave a comment.