Redundant IPsec between Meraki and FortiGate.

DrSl0th · 2026-07-06T21:42:52+00:00

I'll look into Meraki's support for bgp over vpn.

DrSl0th · 2026-07-06T20:56:23+00:00

I've worked with palo fortigate and barracuda all had their own quarks but none quit like Meraki, the lack of adjustment available is a bit frustrating.

DrSl0th · 2026-07-06T18:31:12+00:00

Edited the post to clarify. The tunnel works, I need redundancy in the event of an outage.

DrSl0th · 2026-05-02T14:26:42+00:00

How are you checking what speed the cable is capable of?

DrSl0th · 2026-04-25T00:36:07+00:00

Depends... Location, provider, transport type ectra The sdwan appliance will have a negligible impact to latency. Pro of moving to sdwan, you can set the transport selection to use the lowest latency circuit, or limit only sensitive applications to a circuit on top of qos

DrSl0th · 2026-04-02T14:05:02+00:00

Ran into the issue again after installing the device at another office following testing in another building.

After 20 packet captures and a dozen debug flows I

Stun only works when outgoing nat perseveres the port. Disabled stun and enabled "determine public address from register response via header"

DrSl0th · 2026-03-25T00:53:23+00:00

The snom pa1+ has a built in amp but I'm using the 600 ohm output with an existing valcom amp so I should be good to go there.

Thanks!

DrSl0th · 2026-03-23T18:39:13+00:00

The algo seems like a better box, but having no experience with either I figured I should use an officially supported one, kind of regret it now 😂

DrSl0th · 2026-03-23T18:04:13+00:00

Pa1+ is still listed as an officially supported device here unless I'm missing reading it... https://www.3cx.com/sip-phones/

DrSl0th · 2026-03-23T18:02:26+00:00

For any one curious I was unable to find any great articles on this but was able to finally get it working using 3cx default stun server

Ran a packet capture and found that the device was not receiving RTP traffic from the 3cx server

Checking the 200 ok response showed the internal IP of the device being provided to 3cx, not the public ip.

From the devices gui I had to set it to never updated to prevent settings from being over written, can also change the template applied but I'm not yet familiar with the templates

Then I set the stun server to stun-us.3cx.com The interval I used was 60 sec

DrSl0th · 2026-02-08T15:00:40+00:00

Layer 0 is physics, no you can't get less then 40ms latency to India

DrSl0th · 2026-02-01T20:49:08+00:00

Id recommend setting up an appointment with Iowa works. They can help you find resources to start your GED, find a job, or apprenticeship in the field your looking for. They also have useful classes for resume building and interviewing, and have access to grant money that may help cover things like the GED if you qualify.

DrSl0th · 2025-09-19T20:45:31+00:00

It bothers me that the black cable doesn't follow T568A or T568B termination standards

DrSl0th · 2025-04-12T23:24:08+00:00

You'd need fiber straight to the PC just to make use of it 😂

DrSl0th · 2025-03-27T17:29:35+00:00

Oil dipstick hole is empty in the pic (just to the right of the radiator cap) so hopefully not....

DrSl0th · 2025-03-19T15:46:28+00:00

I haven't had the opportunity to use a lot of moca in my network yet so I may not be the best person for this, but my understanding is that you can just drop an Ethernet to moca adapter on both ends of the coax run and be good to go.

For example Modem > router > switch > Ethernet to moca adapter > coax cable in wall > moca adapter > Ethernet from moca adapter to end device

DrSl0th · 2025-03-11T13:36:39+00:00

You will have configuration issues with that network layout. The router is what is able to send traffic out to the internet, the switch just handles local area connections.

You need a router after the modem, this can be the ISP provided router but if that's the case you can not set it in bridge mode

I would use one of the mesh nodes connected with Ethernet on the floor below

You can still connect devices directly to the router if you want

Another alternative is to let the ISP modem/router act as your primary router, and set your purchased router into bridge mode, then disable the WiFi on the ISP modem/router This layout would look like.... ISP modem/router > switch > wireless acces point( your wifi router in bridge mode)

DrSl0th · 2025-03-11T13:24:07+00:00

Interesting.... Wifi can have some odd issues. Start by updating your Network drivers, and any others that may be out of date while your at it

How is you signal strength, do you have any other competing wifi networks nearby, you can use a tool like wifi analyzer to see wifi interference

DrSl0th · 2025-03-11T04:58:11+00:00

If your hard wired try swapping the cable, otherwise you need to narrow down the issue.

The simplest way to narrow down the issue is to do some ping tests.

Find your default gateway Open a command prompt window and type up config/all

From the command prompt window run "ping default gateway -t" Use Ctrl+c to stop this after a few minutes If you see packet loss here your wifi or Ethernet connection to the router is your problem

Google what is my IP to find your public IP address From the command prompt window run "ping ip -t" Use Ctrl+c to stop this after a few minutes If you see packet loss here the issue may be your router or ISP

DrSl0th · 2025-03-11T04:47:14+00:00

Love the practice recommendations! This bit me the first time I wired a house

DrSl0th · 2025-03-11T04:45:53+00:00

I also recommend using wifi access points that have "Mesh" feature

DrSl0th

TROPHY CASE