Obi behind Sophos UTM not working

(1/3) > >>

Rinchen:
Hi,

Ever since I updated to 3.0.1 (Build: 3722) the obitalk portal has not been updating. It shows my unit as offline (but it's not and I can still make calls) and in need of a firmware update.

I've gone through all the firewall logs and nothing is being blocked (not that anything has changed either).

I've done a network reset on the unit but that didn't help.

Joey

Rinchen:
ps. I don't know if this is normal or not because I've never paid attention to it before:

Status   Backing Off;ex-addr=10.10.10.147:10000

that's obviously my internal address not a public ip.

The provisioning line is:
SYNC -A=aes -K=$SPRM0 -IV=$SPRM1 http://prov.obitalk.com/obhsnprov/profiles/9cadef200d2f-8c8b8711576a.cfg; IF ( $TPRM0 != 1 ) -T=TPRM1 https://prov.obitalk.com/obhsnprov/init/initkey; IF ( $TPRM0 == 1 ) -T=TPRM1 http://prov.obitalk.com/obhsnprov/sync/sync-$SPRM2

QBZappy:
Rinchen,

If you have tried everything else, the last resort is to delete the device from the portal and start over. In the past this has fixed things.

Rinchen:
Thanks. Right as you were posting I was thinking, gosh, my 110 works...  Turns out it's on my old static IP run which bypasses the firewall. I hooked up the 202 to that line and it registered immediately. Looks like I'll have to see about DMZ'ing the 202 internally.

Rinchen:
This is a real puzzler. Both the 202 and Obion appear to be affected behind the Sophos UTM.  There are zero logs with the IP addresses in them. I've turned whole subsystems off.  I've gone so far as doing a 1:1 NAT for the protocols and that didn't work either.

Navigation

[0] Message Index

[#] Next page