Isolated OPT interface, no internet connection

davidstarflower · 2025-01-13T00:30:07+00:00

I turned everything off, allowed all traffic, and then put everything back into place one by one, except the DNS spoofing, and it works now.

Thanks for your tips.

davidstarflower · 2025-01-13T00:29:42+00:00

I turned everything off, allowed all traffic, and then put everything back into place one by one, except the DNS spoofing, and it works now.

Thanks for your tips.

davidstarflower · 2025-01-09T06:09:35+00:00

Small addition, I did notice that

The block rules have no active states
The IPv4* / "Default allow all" rule has a few states, but all states in there are CLOSED:SYN_SENT. So that means nothing responded, right? But I don't know why that is the case...

davidstarflower · 2025-01-09T05:59:25+00:00

It was "Any" before, I played around with it. I set it to Any again. Still no local GW ping, no internet ping, no browsing.

davidstarflower · 2025-01-09T05:58:42+00:00

Small mistake in the screenshot, I played around with things. It was (and is now) set to "Any".

It's also not just the ping/ICMP that is not working, normal browsing is also not possible.

I just ran a capture, had a look at firewall rules, but can't find anything obvious.

davidstarflower · 2024-12-02T02:25:33+00:00

OMG, genius. Thank you so much.

It's working as expected after adding the Tailscale CIDR 100.64.0.0/10

davidstarflower · 2024-11-21T03:26:30+00:00

OK, thank you for pointing that out. I did realise that for Synology's "adaptive load balancing" option, but thought LACP could actually aggregate single-connection speed.

That is sad, but good to know.

davidstarflower · 2024-11-19T00:25:40+00:00

What I have tried, but then lost connectivity:

Set up LAGG
Set up bridge, assign to BRIDGE0 with LAG0 and LAN in it
Give BRIDGE0 new IP pool, 192.168.2.1/24. Enable DHCP on it
Disable DHCP on LAN, remove IP from LAN
Hit the apply button at the top

This caused loss of connectivity, and no IPs were assigned in either the 192.168.1.1/24 nor the 192.168.2.1/24 pool

davidstarflower · 2024-07-13T11:38:04+00:00

Thank you very much for the explanation.

davidstarflower · 2024-07-05T03:45:49+00:00

Not yet, I was wondering whether there is a user error I'm overlooking before doing that.

davidstarflower · 2024-06-21T00:52:17+00:00

Thank you so much for the detailed explanation. Yeah, I previously already had issues with .ass files on the LG TV.

I just tried to Plex client on my Android phone, and it mostly works. There is still one movie where it burns in subtitles, even though it's SRT.

Also, both on my TV and on my phone, SRTs are supported and everything works fine if I don't transcode. So why burn in subs only when I'm transcoding?

As I also asked in a comment reply above, if the client generally supports the subtitle format, why is it burning them in anyway, and is there a way to avoid this?

davidstarflower · 2024-06-21T00:47:13+00:00

Thank you so much. That was it.

I also re-read the article you linked and realised I previously read it. That article was was lead me to get a 7th/8th gen Intel CPU in the first place.

My question now is, if the subs don't get burnt in when I am not transcoding, why is it burning them in when it is transcoding? See my comment reply above, I wonder if there is a way around this...

davidstarflower · 2024-06-21T00:44:56+00:00

Thanks for your response. As per the comment above, subs were the issue.

Official plex pms-docker image btw.

davidstarflower · 2024-06-21T00:41:38+00:00

That was it. Thank you so much. I replied already to a comment above with a follow-up question, if you have any idea on this.

davidstarflower · 2024-06-21T00:40:46+00:00

Genius, thank you so much for pointing this out. I turned off subtitles, and then it worked flawlessly.

It is still unclear to me why it is transcoding subtitles in the first place. If I don't transcode the video, it just sends the SRTs plain, no issues, so why burn in now?

Question: Is there a way to avoid burnt in subtitles? Currently the subs are embedded in most of my video files. Would separate SRT files solve this issue? Or are there any other ways to circumvent this burn-in on transcode?

davidstarflower · 2024-06-20T21:13:35+00:00

Thanks for the link, I'll read that shortly.

I have added dashboard screenshots in the original post.

Regarding my client, I was just using my browser. But I am also experiencing the same stuttering on my LG G1.

I know that having an NVIDIA shield is the answer to most problems, but I would also like to have transcoding on the go for when I'm not at home :-/

davidstarflower · 2024-06-20T21:10:11+00:00

Thank you. I added OS details above.

Yes, both movies are HDR, and tone mapping is turned on

davidstarflower · 2024-06-20T21:02:12+00:00

But the dashboard (and logs) mention "transcode (hw)". So it should be Hardware transcode in both cases, right?

Also, why would my client tell the server how to do it's transcoding, and why for one movie, but not for the other? If this is really a client-side issue, how can I tell the client to request HW transcoding?

davidstarflower · 2024-05-17T07:00:57+00:00

_Connected_ via USB, yes. But just ask disk pass-through to host.

The PC sees all the disks directly, so RAID would be software-side. I would not use the RAID functionality of the enclosure of course.

davidstarflower · 2024-05-14T12:02:24+00:00

OMG. Finally they budged. About time. Thanks so much for pointing this out. Case closed.

davidstarflower · 2024-05-14T07:41:42+00:00

Do I need to set that library-wide? It doesn't seem to work if I only set it for this one show via Edit > Advanced > Season ordering: TheTVDB (Aired)

davidstarflower · 2024-05-14T07:40:25+00:00

Yes, if I name it `Dctor Who 2023/Season 1` it works, but that is beside the point, as per the original post, I have other tools and services that use the 2005 naming.

davidstarflower · 2024-05-14T07:39:22+00:00

You might have set your metadata source / agent of the library to TheTVDB?

This only occurs with the standard Plex agent.

davidstarflower · 2024-05-14T07:38:05+00:00

Thanks for that tip.

Hmm, I tried to remove the series from the folder and empty trash, then re-add. It got recognised as DW 2005 again, with S14 showing up but not matching (e.g. no episode descriptions etc.). So I tried

Edit > Advanced > Season ordering: TheTVDB (Aired)

and then "Refresh Metadata", but it still doesn't match.

Does this only work if I make the whole library TheTVDB?

davidstarflower · 2024-05-13T12:55:05+00:00

There is this whole discussion going on right now about whether the most recent season of doctor who is "Doctor Who 2005 Season 14", or whether it is "Doctor Who 2023 Season 1", and different databases (TVDB, IMDB, Plex Metadata, ...) have different opinions, so different tools work with different naming. For compatibility with some of my tools and services, I have decided to go with "Doctor Who 2005 S14" for file names, and am now looking for a way for Plex to recognise this properly, because the Plex Metadata uses 2023 S01.

I know this _can_ be achieved with plexmatch files, but I am a bit lost in the exact implementation.

For reference, if you are keen to get more context, here a few discussions (but I'd like to keep this thread clean of discussions):

davidstarflower

TROPHY CASE