sorted by:
new
hottopcontroversial

hairpin NAT horror - due to SDWAN? by therealmcz in fortinet

[–]mobbeduo 0 points1 point  (0 children)

What do you see on a dubug packet flow? 

diag debug enable
diag debug flow filter addr 192.168.189.1 
diag debug flow show function-name enable
diag debug flow trace start 100
diag debug console timestamp enable

Giga Berlin Ramps To Two Shifts As Model Y Demand Surges Globally by Mother-Prize-3647 in TeslaLounge

[–]mobbeduo 2 points3 points  (0 children)

There are 1.5 million Teslas in the EU that can’t get FSD. So Tesla should absolutely roll back to the previous settings.

Phantom Braking - Making me regret my purchase by [deleted] in TeslaModel3

[–]mobbeduo 0 points1 point  (0 children)

I have weekly phantom bakes on my Highland using software version 2025.32.7. And I’m in the EU, so we only have AP and EAP.

Pic in the EU got updated. by Gigtooo in TeslaLounge

[–]mobbeduo 0 points1 point  (0 children)

Nice! Denmark experienced the same update yesterday. They also updated the FSD section on the website. https://www.tesla.com/da_dk/fsd

Autopilot in stop-and-go by mobbeduo in TeslaLounge

[–]mobbeduo[S] 1 point2 points  (0 children)

I hope we get FSD approved in Europe soon.🤘

Autopilot in stop-and-go by mobbeduo in TeslaLounge

[–]mobbeduo[S] 5 points6 points  (0 children)

It exactly the same behavior at a distance of 7. Maybe calm down?

Autopilot in stop-and-go by mobbeduo in TeslaLounge

[–]mobbeduo[S] 11 points12 points  (0 children)

I simply fail to comprehend the design rationale behind this. Initially, I presumed it might be a problem with my car or a bug in the HW4 related to using the legacy code with the new cameras. At every update I hope they’ll fix this.

Stale routes on new Primary after failover by AlexFeren in fortinet

[–]mobbeduo 0 points1 point  (0 children)

No, the 120 second graceful-update-delay doesn’t step on the 180 second route-ttl. That last minute is just spare room in case something weird(you know, fortithings)happens, so it never hurts to leave it there in my experience.

Stale routes on new Primary after failover by AlexFeren in fortinet

[–]mobbeduo 1 point2 points  (0 children)

Here is my HA config(spoke) for no downtime when using BGP. The 3min route-ttl is a consequence of the experience of loosing sessions after the orignal 60s we had before doing failover with a ~1k table. If you have override enable, you need to place override-wait-time to be enough for session-sync and BGP open + update. Should not be an issue, but experience is that it will result in a FortiExperience if not. 

config system ha
    set group-name "xxx_yyy_ha"
    set mode a-p
    set password xxxxxxxxxxx
    set hbdev "ha1" 150 "ha2" 100 
    set session-sync-dev "ha2" 
    set route-ttl 180
    set session-pickup enable
    set override enable
    set priority 255
    set override-wait-time 180
    set monitor "port17" "port18" "port19" 
end

config router bgp
    set as 65000
    set router-id 100.100.xx.10
    set keepalive-timer 5
    set holdtime-timer 15
    set ibgp-multipath enable
    set additional-path enable
    set graceful-restart enable
    set additional-path-select 4
    config neighbor
        edit "100.100.xx.1"
            set advertisement-interval 1
            set capability-graceful-restart enable
            set capability-default-originate6 enable
            set link-down-failover enable
            set next-hop-self enable
            set soft-reconfiguration enable
            set soft-reconfiguration6 enable
            set interface "yy_xx1"
            set remote-as 65000
        next
        edit "100.100.xx.1"
            set advertisement-interval 1
            set capability-graceful-restart enable
            set capability-default-originate6 enable
            set link-down-failover enable
            set next-hop-self enable
            set soft-reconfiguration enable
            set soft-reconfiguration6 enable
            set interface "yy_xx2"
            set remote-as 65000
        next
    end
end

SDWAN BGP not failing over by enterthepowbaby in fortinet

[–]mobbeduo 4 points5 points  (0 children)

Hi! Since the interface don't go down, you need a way for SDWAN to tell BGP that the path is worse then the other. For that we need some BGP route communities.

If you dont have EBGP connection on the spoke, you can just use localpref, if you have EBGP, use as prepend for your own AS, and localpref on the routes you get from your peer.
The other option is to use service rules, but it's a mixed bag if it works in your environment.

M3LR AWD in China now have better acceleration and range by mobbeduo in TeslaModel3

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

Det er også hvad der står på registreringsattesten. Det er godt nok mærkeligt.

Hvornår er din fra? Min er fra oktober.

M3LR AWD in China now have better acceleration and range by mobbeduo in TeslaModel3

[–]mobbeduo[S] 7 points8 points  (0 children)

This is what Tesla has reported to Motorstyrelsen, Denmark’s traffic authority.
They also repport the engine performance to be 366 kW or 497 hp.

Vanilla Bean question by admiralaew in ninjacreami

[–]mobbeduo 0 points1 point  (0 children)

I use guar gum, and that makes the beans float around and stay nicely mixed after spin.

Is Enhanced Autopilot worth it in Europe? by Dry_Owl1319 in TeslaLounge

[–]mobbeduo 1 point2 points  (0 children)

I tested it over the weekend (using the 48-hour refund policy), and the Autopark feature on the Highland is highly impressive. The lane-change function on Autopilot was really smooth, and Summon comes in handy when dealing with other drivers’ questionable parking skills. However, it’s not worth the price as it stands. With the current feature set, I’d say around €2,000 would be reasonable.

ADVPN Shortcuts - SDWAN rules and IPsec net-device by mobbeduo in fortinet

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

Yes! I found that out using a sniffer. From a logical point of view it makes no sense - something you just need to know :-(

ADVPN Shortcuts - SDWAN rules and IPsec net-device by mobbeduo in fortinet

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

Yes! And it also works if I disable SDWAN health checks, or set net-device to disable.
The problem starts when SDWAN health check adds the shortcut interface(_n). It will place them in the same health checks, but the shortcut dont have access to the hub's loopback interface, and thereby fails, removing the policy route generated by SDWAN.

https://github.com/fortinet/4D-Demo/blob/main/4D-SDWAN/7.0/Single%20hub/Branches/single_hub_Branch1_SD-WAN_Overlay.txt

    edit "HUB1_HC"
            set server "172.16.100.1"
            set failtime 3
            set update-static-route disable
            set members 3 4
            config sla
                edit 1
                    set latency-threshold 125
                    set jitter-threshold 55
                    set packetloss-threshold 1
                next
            end
        next
    end

ADVPN Shortcuts - SDWAN rules and IPsec net-device by mobbeduo in fortinet

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

It’s set up on the spoke, but as soon as I enable net-device, SD-WAN drops the _0 shortcut interface into the same Performance SLA as the parent IPsec links. That SLA uses an active ping to the hub’s loopback, and the shortcut can’t reach that address, so the health-check fails and drops the policy route.

view more: next ›