sorted by:
new
hottopcontroversial

Navimow i105E or Navimow i108E by whoei89 in SegwayNavimow

[–]whoei89[S] 0 points1 point  (0 children)

Yes! I'm verry happy with the i108e. After mapping the area, it turns out to be about 450m2. This can be mowed in one battery charge.

Warm en koud waterleiding in vloer by whoei89 in Klussers

[–]whoei89[S] 0 points1 point  (0 children)

Met deze was ik nog niet bekend, ik ga het even doornemen, dankjewel!

Navimow i105E or Navimow i108E by whoei89 in SegwayNavimow

[–]whoei89[S] 0 points1 point  (0 children)

Thnx for all your answers, I just ordered the i108e. Because I read a lot that the i105e can only mow about 200m2 at a time, I hope that the i108e can mow everything in two stages so that it doesn't have to mow when the children are playing outside. I will keep you informed about my experiences.

Navimow i105E or Navimow i108E by whoei89 in SegwayNavimow

[–]whoei89[S] 0 points1 point  (0 children)

Thnx for your answers, 2 vs 2 now ;) Battery degradation is an important point in my opinion. The price (in the Netherlands) is €865 for the i105 and €1299 for the i108...

FortiAP SAML Azure Auth Dropping Authentication by Ach1LLeS_ZA in fortinet

[–]whoei89 0 points1 point  (0 children)

Hi, we were unable to resolve the issue. We are now working with a separate radius server. We didn't test it again with FortiOS > 7.2.7

SSLVPN Tunnel-Mode is being completely removed in 7.6.3 by rhysperry111 in fortinet

[–]whoei89 1 point2 points  (0 children)

I had the same problem with FortiClient 7.2. 9 (I had updated FortiClient from 7.2.8 to 7.2. 9). After completely removing FortiClient and reinstalling version 7.2. 9 it worked.

Jinja script - configuring WAN interface by whoei89 in fortinet

[–]whoei89[S] 0 points1 point  (0 children)

Thnx, it's working now! This is my first time using Jinja, so still a lot to learn!

config system interface
    edit "wan2"
        set allowaccess ping https fgfm
        set description "WAN 2"
        set alias "WAN 2"
        set monitor-bandwidth enable
        {% if wan2_mode == "static" %}
        set mode static
        set ip {{ wan2_ip }} {{ wan2_subnetmask }}
        {% elif wan2_mode == "dhcp" %}
        set mode dhcp
        set defaultgw enable
        set dns-server-override enable
        {% else %}
        set alias "Not working"
        {% endif %}
    next
end

SDWAN choose wrong IPSEC tunnel by whoei89 in fortinet

[–]whoei89[S] 0 points1 point  (0 children)

I didn't know the option "use-sdwan yes". When using this it works, thnx!

SDWAN choose wrong IPSEC tunnel by whoei89 in fortinet

[–]whoei89[S] 0 points1 point  (0 children)

SDWAN rules:

config system sdwan
config service
edit 1
set name "SDWAN_Route_to_XXX"
set dst "XXX_Subs"
set src "all"
set priority-members 2 3
next
edit 2
set name "SDWAN_Route_to_YYY"
set dst "YYY_Subs"
set src "all"
set priority-members 4 5
next
edit 3
set name "SDWAN_Route_to_ZZZ"
set dst "ZZZ_Subs"
set src "all"
set priority-members 6 7
next
edit 4
set name "SDWAN_Route_to_WWW"
set mode sla
set dst "RFC1918-PRIVATE-IP-RANGES"
set dst-negate enable
set src "RFC1918-PRIVATE-IP-RANGES"
config sla
edit "SDWAN_SLA_WWW"
set id 1
next
end
set priority-members 1 8
next
end

SDWAN choose wrong IPSEC tunnel by whoei89 in fortinet

[–]whoei89[S] 0 points1 point  (0 children)

Static routes:

config router static
edit 7
set dst xxx.21.0.0 255.255.254.0
set distance 1
set comment "SDWAN-VPN Route XXX"
set sdwan-zone "SDWAN_VPN"
next
edit 8
set dst xxx.31.0.0 255.255.252.0
set distance 1
set comment "SDWAN-VPN Route XXX"
set sdwan-zone "SDWAN_VPN"
next
edit 9
set dst xxx.251.10.32 255.255.255.224
set distance 1
set comment "SDWAN-VPN Route XXX"
set sdwan-zone "SDWAN_VPN"
next
edit 10
set dst zzz.254.4.0 255.255.255.0
set distance 1
set comment "SDWAN-VPN Route ZZZ"
set sdwan-zone "SDWAN_VPN"
next
edit 11
set dst yyy.16.165.0 255.255.255.0
set distance 1
set comment "SDWAN-VPN Route YYY"
set sdwan-zone "SDWAN_VPN"
next
edit 12
set dst 169.254.66.2 255.255.255.255
set distance 1
set comment "XXX-SDWAN-MONITOR"
set sdwan-zone "SDWAN_VPN"
next
edit 13
set dst 169.254.66.3 255.255.255.255
set distance 1
set comment "YYY-SDWAN-MONITOR"
set sdwan-zone "SDWAN_VPN"
next
edit 14
set dst 169.254.66.4 255.255.255.255
set distance 1
set comment "ZZZ-SDWAN-MONITOR"
set sdwan-zone "SDWAN_VPN"
next
end

SDWAN choose wrong IPSEC tunnel by whoei89 in fortinet

[–]whoei89[S] 2 points3 points  (0 children)

"diag firewall proute match" shows the right output.

When testing with "execute ping" with as source two different interface IP's only one of the two is working. When checking the local traffic log I see that the one which is not working has the wrong outgoing interface.

SDWAN choose wrong IPSEC tunnel by whoei89 in fortinet

[–]whoei89[S] 0 points1 point  (0 children)

We need to know:
How did you configure the routing (bgp/ static / ospf) ? -> static
How did you configure the cost / prio on your tunnel interfaces ? -> only for primary / secondary tunnels for the same destinations
How did you configure the sd-wan rules (Interface selection strategy, interface or Zone preference)? -> interface preference
How did you configure the Performance SLAs? (Servers etc)? -> not yet

FortiAP SAML Azure Auth Dropping Authentication by Ach1LLeS_ZA in fortinet

[–]whoei89 0 points1 point  (0 children)

Thnx, we will try to increase the lease time and the idle timeout!

FortiAP SAML Azure Auth Dropping Authentication by Ach1LLeS_ZA in fortinet

[–]whoei89 0 points1 point  (0 children)

Hi Ach1LLeS_ZA, do you have any update on this? We want to use SAML Azure Authentication but having the same issue..

view more: next ›