Hello All, Following a thread I posted recently related to routing the
same firewall is giving me problems with a NAT (fortigate 200B, running
v4.0,build0639,120906 (MR3 Patch 10)) I am struggling to find a reason
why a server with inbound NAT config...
Hello, I have copied a configuration file from a fortigate 60ADSL (the
ADSL interface was not in use) to a fortigate 80c after editing the
#config-version header but it doesn' t work despite the fact they looked
identical when compared side by side. ...
It' s looking like I might have to re-create some policies on this thing
to try to get it to behave how I need it to. I inherited this config (I
converted the config from a 200A to this 200B) and its not ideal now so
I might try to shape the interfac...
Thanks again but I do have the ID column shown, I remember going from
the older green interface to the new look and wondered where the ID had
gone to :) Perhaps if I try to shuffle the VPN zone around it might then
let me move the firewall policies t...
I did try to move the policy up but it refused because I am using a zone
to group some interface mode IPsec tunnels together. It comes up with
this: " Moving a policy from one interface/zone pair to a different
interface/zone pair is not permitted." ...
Thanks micahawitt. Yes you understood what I was trying to say. I don' t
normally use IP pools when choosing NAT on an outbound policy, normally
I leave it set to use destination interface address. I did actually have
a firewall policy like you descr...
Just thought I' d post to say that it worked fine. I did the copy the
first 3 lines trick. I think the reason it failed last time was due to
the fact the fortigate units were on different firmware versions now
that I think about it. Thanks for your h...
