The situation with V8 was it had an extra nic as a 'DMZ' with a webserver in that subnet. This has been working fine until I moved to UTM9.
I made a config-backup of V8, installed a new VM for UTM9 and restored the config. All seemed fine except for the webserver. It is a SuSE-linux server with Apache. The server can still be reached via internet (as before) and you can see the SSL-certificate being recognized but then nothing.....
I cannot find any errors in UTM nor in Apache except for time-outs. It has nothing to do with that server because I now have replaced the old V8 back and that works OK as before. Another strange thing is that when I telnet (PuTTY SSH) to the webserver (while running theUTM9) I can cd through the filesystem but when I start YaST it becomes VERY slow. The same for using WinSCP; I can browse the filesystem but cannot open files from /var/log. WinSCP looses the connection.
The setup:
- DNAT
- Traffic Source: Any
- Traffic Service: Group with http and https
- Traffic Destination: External IP bound on external nic from UTM
- Destination: DNS host (the webserver)
- Automatic Firewall rule: enabled
- Plus a few firewall rules for extra ports from internal for UPS, Nagios, etc.
And this setup has been in production for months on the 'old' V8.
What could I do to have this working again on UTM9? Has something changed that I don't know of?
Please ask if something is unclear.
This thread was automatically locked due to age.
