This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DO NOT INSTALL 9.352-6 or 9.318-5

See the thread "UTM Version 9.352-6 and 9.318-5 released"

Cheers - Bob



This thread was automatically locked due to age.
Parents
  • I had the problem with the RED device with some customers but not with 9.352. It was a general problem. Turn off and on the "redsX" Interface belonging to the RED. After that disable the RED. Wait arround 30 seconds (until the RED is offline) and turn it on again. In our case the route for the network belonging to the RED was missing on the UTM. After the mentioned steps the route was added.
Reply
  • I had the problem with the RED device with some customers but not with 9.352. It was a general problem. Turn off and on the "redsX" Interface belonging to the RED. After that disable the RED. Wait arround 30 seconds (until the RED is offline) and turn it on again. In our case the route for the network belonging to the RED was missing on the UTM. After the mentioned steps the route was added.
Children
  • fix didn't help. But yes it has something todo with the routing i can ping devices behind the red when i use the internal utm ping tool but only when i say interface red xxx. When i choose "use closest route" it doesn't work.

    also the red is full up dns changes etc. are all working,
    deleting the red also doesn't help :/