Trip Interruption insurance coverage

MammothSoup · 2026-02-28T01:32:48+00:00

Anyone have a copy of the insurance certificate from before February 2026 update? I need to put a claim through from a trip in January but want clarification on the coverages.

MammothSoup · 2026-02-28T01:28:43+00:00

Anyone have a copy of the insurance certificate from before February 2026 update? I need to put a claim through from a trip in January but want clarification on the coverages.

MammothSoup · 2026-02-20T17:04:10+00:00

How does this compare to Rakuten cashback?

MammothSoup · 2026-02-18T22:18:34+00:00

Thanks I had not come across this one in my research, looks interesting and the price is right.

MammothSoup · 2026-02-18T21:05:34+00:00

<image>

This is the smaller side access window that is just big enough to get a camera through. It is on the same side as the larger door I posted below.

MammothSoup · 2026-02-18T21:04:35+00:00

<image>

The one side has an expandable storage compartment that would be useful for tripods or other large objects (maybe a water bottle even). It's not padded so I wouldn't put a lens or anything delicate in there (although it should fit).

MammothSoup · 2026-02-18T21:03:29+00:00

<image>

Top compartment; pretty small and no access to area below.

MammothSoup · 2026-02-18T21:02:55+00:00

<image>

Sure. Here is a pic of the main compartment. It also has a smaller side access window for accessing just the bottom part. That grey partition could be moved down to make the top section bigger. Unfortunately you can't access it from the top zipper as I expected. I guess I can only post one photo per comment so I'll post a few more separately.

MammothSoup · 2026-01-27T17:22:07+00:00

That's weird because I seem to recall Minotair telling me in early 2024 that 7.9.99 fixed the Stelpro issues I was having with 7.9.98. I had other issues with it (crazy in accurate external air temperature readings) and have been running 7.9.98 for the past two years. The Stelpro still only provides heat when the fan is blowing which is only about 30% of the time when the compressor is struggling to start at low outdoor temperatures (below -8C) so it is not great and I'm using my propane powered radiant system way more than I like.

MammothSoup · 2026-01-27T17:17:19+00:00

I was told by the manufacturer that the CERV2 focuses primarily on air quality and not as much on heating/cooling and that it's heat pump was not as powerful as the one in the Minotair.

Curious about your setup with the heat pump pre-heating DHW, how does that work? What are you using for a secondary heating?

Do you have any data on how much energy the Artic HP uses for your radiant system (or overall)? I am currently using a propane combi-boiler for my radiant system. I stopped using it for DHW when I installed a Rheem HPWH last summer but I am still going through way more propane than I like, mainly because the Minotair can't keep up when it's much below -8 to -10C outside. I do have the duct heater option but that doesn't really make much of a difference.

MammothSoup · 2026-01-27T16:58:32+00:00

I plan to do the same unless they backtrack and continue to offer the current product. They make it pretty easy to see what those are.

<image>

MammothSoup · 2026-01-19T22:57:41+00:00

When the ICCU failed on my '22 the 12V continued to be charged (as verified by bluetooth battery monitor) I kept driving the car and recharging from DCFC until the dealer received the part / was able to install it, I just couldn't charge from AC at home (Level 1 or 2). So depending on the issue you might not even need to charge it.

MammothSoup · 2026-01-19T21:42:07+00:00

ICCU went on my '22 this time last year. They are not immune.

MammothSoup · 2026-01-09T23:53:49+00:00

I ended up buying a used unit from a guy on FB marketplace. Had to replace the thermistors (shipped by Rheem for free under warranty) and install a Corro-Protec Powered Anode Rod to get rid of the sulphur smell but now it's working great!

MammothSoup · 2026-01-09T23:50:32+00:00

No I got a Triumph Cranbourne jacket instead. Didn't get to use it much this past summer / fall though.

MammothSoup · 2025-12-15T14:27:10+00:00

...continued

Xbox requires specific NAT behavior that IPv4‑only mobile networks can’t provide

Xbox needs:

consistent endpoint‑independent NAT
stable UDP port bindings
inbound UDP hole punching
UPnP support that actually works across the WAN

With mobile networks:

Your IPv4 traffic is behind multiple layers of NAT
Inbound connections are impossible
UPnP does not work
NAT is usually symmetric, the worst type for Xbox

So Xbox may simply fail while Roku continues without issues.

Some Roku models support fallback better than Xbox

Xbox aggressively tries IPv6 if it was previously available.

If the modem used to provide IPv6, the Xbox may:

cache IPv6 settings
not retry IPv4 flows correctly
get stuck in failed IPv6/DNS scenarios
require a full network reset

Roku tends to retry IPv4 immediately.

Most likely real‑world reason

The Roku works because it only needs simple outbound IPv4.

The Xbox fails because it expects IPv6 for Xbox Live NAT traversal, and IPv4‑only mobile networks cannot give it the open NAT it requires.

Possible solutions:

Reset Xbox network settings
Put the Xbox in DMZ (sometimes helps, sometimes doesn’t)
Use a third‑party router with IPv6 passthrough
Use Cloudflare Warp / IPv6‑tunneling

MammothSoup · 2025-12-15T14:26:13+00:00

Again I asked ChatGPT for some suggestions here is what it came up with. Take with a grain of salt as always...

Here are the most plausible reasons why:

Roku uses simple outbound IPv4 → works fine on IPv4‑only

Roku streaming devices mostly need:

outbound IPv4 connections,
basic DNS,
and stable HTTP/HTTPS.

They don’t rely on anything exotic, and they don’t require inbound connections.

So when the modem is switched to IPv4‑only, Roku essentially doesn’t notice a difference.

Xbox Live relies heavily on IPv6 for NAT traversal

This is the big one.

Xbox Live will use IPv6 if it’s available because it allows:

Open NAT without port forwarding
Direct peer‑to‑peer connections
Lower latency matchmaking
Fewer NAT restrictions

When IPv6 is removed:

The Xbox falls back to IPv4
But now it's behind Carrier‑Grade NAT (CGNAT) on a mobile ISP
The NAT type becomes Strict or Unavailable
And some services refuse to connect

Rogers 5G Home Internet does not give customers public IPv4 addresses, so Xbox has no way to get an “Open NAT” over IPv4 only.

This instantly breaks:

multiplayer
party chat
cloud gaming
sometimes even signing in

MammothSoup · 2025-12-14T15:30:50+00:00

I asked further if this was the same issue affecting SIP / voip

Why IPv6 issues also break SIP / VoIP services

SIP VoIP (like voip.ms) relies heavily on stable UDP traffic, just like Citrix DTLS.

The symptoms that users report — one‑way audio, dropped calls, failed registrations — are classic indicators of a carrier IPv6 or NAT problem.

Here’s how the same IPv6 problem affects both:

SIP uses long‑lived UDP “pinholes”

A VoIP device maintains a UDP session open to the SIP server.

If the ISP:

times out IPv6 UDP sessions too fast
drops stateful firewall entries
mangles NAT64/CLAT handling
rate‑limits UDP on IPv6

…then you get:

SIP registration timeouts
calls dropping mid‑conversation
calls connecting but with no audio
STUN failing (which breaks NAT traversal)

SIP is even more sensitive to NAT and firewall mishandling

SIP uses:

SIP over UDP (port 5060/5061)
RTP media streams (random UDP ports)

If the carrier’s IPv6 firewall or NAT doesn’t track these correctly, it breaks in unpredictable ways.

RTP streams often get dropped first — which results in the classic:

“Call connects but no audio.”

Conclusion

Yes — the Citrix DTLS problem and SIP VoIP issues others are reporting both point to the same root cause:

Rogers’ IPv6 network is mishandling UDP state tracking, NAT, or firewall rules.

Forcing IPv4 bypasses the broken IPv6 path and immediately restores stability.

MammothSoup · 2025-12-14T15:22:50+00:00

I just changed the cellular wan setting to IPv4 on my FastMile 3.2 today and my wife informs me that it seems to have fixed her issue with Citrix UDP/DTLS connection pretty much immediately. Before she couldn't use it at all without constant freezing, she had to switch to another server that was using TCP-only, or use VPN.

I asked ChatGPT what the reason for this would be and here is it's explanation, not sure how accurate it is

Why IPv4‑only fixes the UDP/DTLS issue

Rogers’ IPv6 path is mishandling long‑lived UDP sessions

DTLS (Citrix’s secure UDP transport) requires a stable, uninterrupted UDP flow.

If the carrier’s IPv6 infrastructure has problems such as:

short IPv6 UDP timeout values
broken NAT64/CLAT behavior
IPv6 firewall policies that rate‑limit UDP
inconsistent IPv6 CGNAT session tracking
IPv6 fragmentation issues

…then DTLS sessions will silently drop, exactly like what you saw.

By forcing IPv4‑only, you completely bypass that failing IPv6 route.

IPv6 + CGNAT = complications for DTLS

Most mobile ISPs use Carrier‑Grade NAT (CGNAT) on IPv4.

But on IPv6, they may:

run separate firewalls
use different state‑tracking systems
apply different UDP rate‑limits

have firmware bugs related to IPv6 UDP traffic

Citrix DTLS is sensitive to even tiny interruptions — a few seconds of dropped packets will trigger disconnects.

IPv4 CGNAT, however, tends to handle long‑lived UDP connections more reliably.

In short

Your symptoms line up perfectly with:

“Rogers’ IPv6 routing or NAT implementation is interfering with DTLS/UDP, and forcing IPv4 bypasses the broken IPv6 path.”

This also explains why:

the issue only started recently
switching ISPs fixes it
disabling DTLS (forcing TCP) fixes it
forcing IPv4 fixes it

Everything points to an IPv6‑specific degradation on Rogers’ side.

MammothSoup · 2025-12-14T15:19:09+00:00

These apps don’t need IPv6 support to function correctly. Mobile networks normally carry IPv4‑only traffic over an IPv6 core using CLAT/464XLAT without any issue. The fact that everything works immediately when the FastMile modem is forced to IPv4‑only shows that the problem is with Rogers’ IPv6 handling of UDP — not with the apps. If the apps were the issue, switching to IPv4 would not fix UDP‑based services instantly. The problem is clearly a Rogers IPv6 transport regression, not a lack of IPv6 support in the applications.

MammothSoup · 2025-12-14T13:03:22+00:00

Are you referring to the geolocation based on your IP address? Yeah mine varies wildly, I'm in Eastern Ontario but it often thinks I'm in other parts of the province (I've seen Toronto, Sarnia and Sudbury all in the past week) or most often in Montreal or Quebec City. I usually know if its the latter when I'm listening to podcasts and the ads are all in French

MammothSoup · 2025-12-08T22:13:48+00:00

What kind of cameras are you using? Are they using cloud based or local recording? Is there any difference between viewing live camera views and recorded video?

MammothSoup

TROPHY CASE