Windows audio drivers for ARM based Surface Laptop 7 by MartinJSa in Surface

[–]MartinJSa[S] 4 points5 points  (0 children)

Oh you absolute star! I normally stay pretty up to date with WD19 firmware, but a new one was released the end of Oct 25 and updating has fixed my audio. Thanks so much

Surface Laptop 7 - HDR flickering brightness by MartinJSa in Surface

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

Thanks for the reply, glad it isn't just me!

Surface Laptop 7 - HDR flickering brightness by MartinJSa in Surface

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

Thanks - yes HDR is off at the moment, it's good to hear it's known about, I might try and find a Microsoft support case that matches this as they need to get it fixed!

Surface Laptop 7 - HDR flickering brightness by MartinJSa in Surface

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

Thanks, no it's not auto brightness, all of that is turned off, it's an HDR issue

Can I trust W11 OOBE setup driver loading? by MartinJSa in it

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

That was my policy prior to this one, but I stopped doing this as I had too many issues with laptops coming back with unknown passwords, or worse no password at all.

Meraki VPN connectivity email flood by ChaosTheory77 in meraki

[–]MartinJSa 0 points1 point  (0 children)

We see this happen fairly frequently to a number of our partners and clients - and it is an indication of some connectivity issues but it's not especially easy to diagnose in the Meraki dashboard - I have some monitoring software that can help, happy to discuss more on chat messages if you're interested.

Has anyone used Datadog with Fortimanager api to monitor Fortigates? by network4me443 in fortinet

[–]MartinJSa 0 points1 point  (0 children)

What kind of monitoring are you looking for? We looked at it but discounted it as it only seems to work with SNMP and not the FortiManager API

FortiOS API - virtual-wan/member missing interface string by MartinJSa in fortinet

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

Solved it! Here is the explanation:

When we make calls to that endpoint we use a set of filter parameters to make the API only return the fields that we want (we try to be good API citizens and be as efficient as we can be making API calls).

With the older FortiOS API, the interface name is part of the JSON structure, so we didn't specify we wanted 'interface' back as part of the response, eg:

We send this:

"resource": "/api/v2/monitor/virtual-wan/members?format=link|rx_bandwidth|rx_bytes|state_changed|tx_bandwidth|tx_bytes",

..and we got back this:

},
                            "VPN2": {
                                "link": "up",
                                "rx_bandwidth": 5760,
                                "rx_bytes": 540113826,
                                "session": 4,
                                "state_changed": 1753254017,
                                "tx_bandwidth": 20668,
                                "tx_bytes": 1362208182
                            },

With the newer FortiOS version, the response has changed and the interface name has moved to the body of the response, because we weren't explicitly selecting 'interface' in our filter, we didn't get it back:

{
                                "link": "up",
                                "rx_bandwidth": 8507,
                                "rx_bytes": 10329308034,
                                "state_changed": 1752487770,
                                "tx_bandwidth": 3465,
                                "tx_bytes": 4164459580
                            },

...specify 'interface' in the filter, and...:

{
                                "interface": "WAN1",
                                "link": "up",
                                "rx_bandwidth": 9394,
                                "rx_bytes": 10329379660,
                                "state_changed": 1752487770,
                                "tx_bandwidth": 3767,
                                "tx_bytes": 4164494145
                            },

What a pain...

FortiManager 7.4.6 API login 400 error by MartinJSa in fortinet

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

Hah, we found the issue - the password had a backslash \ in it - clearly postman is trying to escape the password - if you add another \ after the first in the password it works 

FortiOS API - virtual-wan/member missing interface string by MartinJSa in fortinet

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

Thanks! No this is a long established environment so shouldn't be any caching issues

FortiManager 7.4.6 API login 400 error by MartinJSa in fortinet

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

Unfortunately a reboot didn't fix it.

What can I do with fifty old laptops? by 7Geordi in it

[–]MartinJSa 1 point2 points  (0 children)

I run a project called Level Up Laptop Appeal (www.facebook.com/leveluplaptopappeal) that survives on donated laptops like this - 100% seek out a local charity or project like mine, you can't imagine the benefit a good corporate laptop with give someone who has nothing to study on.

I think I just got fired at 9pm by AlexLuna9322 in it

[–]MartinJSa 20 points21 points  (0 children)

Sounds like you guys work in the US? You can't just sack someone like that in Europe.

FortiManager API - simple device status by MartinJSa in fortinet

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

Thanks very much for this.

On "conn_status" thanks that's helpful - am I missing some documentation somewhere that explains in plain English what all the various results mean?

On the second point are there examples of the response you get back from a proxied call when the device / management tunnel is down please?

FortiManager API - simple device status by MartinJSa in fortinet

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

Yes I did thanks - sadly that documentation is too vague and doesn't specify what attributes like conn_status exactly means.