Jup, Im having an NTP issue on my win10 machine If you search for it you find the same 5 "solutions" from dozens of content farms.
I'm coding them down as plantuml network code and render them using a selfhosted plantuml Server.
In the end my whole admin guide resides in a obsidian notebook as markdown There is even a plugin that renders plantuml code within obsidian
The nice thing: everything is just code and can be moved to any other tool (had my documentation in a local gitlab repo, but I swapped gitlab out for gitea)
Yep, I went in this direction...until I gave in during a bare metal install of something...
Docker is not hassle free but usually most setup guides for apps are much much easier with docker
Worth a try, will try it when Im back home
I'll try that one thanks
I changed the native vlan to '83' and allowed all others
The isoöation is done with firewall rules blocking access from the IoT net to default, with some exceptions (dns, media nas (currently), etc.)
So if I understand this right you will need to change the network on the port attached to the synology in your UniFi configuration or set the vlan tag in the synology OS, I would do the former.
doesn't the switch terminate any VLAN tagging at the port? so if I add the VLAN to the DSM configuration it doesn't receive any tagged packages and refuses them?
It sounds like you just added a second network/vlan to the existing interface which means you actually created a trunk and are getting the old network untagged and the new network with vlan tags which the synology is dropping.
with all the other devices in the IoT subnet it works with setting the VLAN on the port of the switch. If I check back on the unifi site, I found this:
'Applying a VLAN to a Switch Port
Native VLAN
The Native VLAN is the VLAN assigned to "untagged" traffic passing through a switch port. Devices physically connected to a switch port will be placed on this Native VLAN.
Tagged Networks and Trunk Ports
Ports can be configured to allow traffic from other networks. Allowing specific networks/VLANs is referred to as “tagging” them on the switch port. You can see all ports’ VLAN tags in the VLAN Viewer, found in the Ports tab.
Ports that have been tagged to allow traffic from multiple VLANs are referred to as “trunk” ports. By default, all ports on UniFi Switches are trunked to allow all VLANs. '
if I understand that in combination with your comment correctly: I set the native VLAN to 83
so everything tagged with 83
is correctly forwarded to the NAS and accepted there, stuff tagged with 1
are non native, the tag stays on and the NAS doesn't accept it?
But that would make the Synology NAS quite hard to use in any corporate setting with multiple VLANs which need to interconnect
and why does it work the other way around? while being in the default net 1
it does accept stuff from VLAN 83
Synology OS also doesn’t really support trunked ports through the UI (even though it does support a port that only uses a vlan tag) so it’s much easier to just leave them untagged.
which would mean, I can't put it in the IoT net?
It’s normal for a switch to strip a vlan tag when it sends a packet out, so that the endpoint doesn’t have to support vlans. Don’t worry about that. As far as the endpoint is concerned, it’s just normal subnetting.
okay that's what I thought
When it’s on the other vlan, can you even ping it? When you check the packet capture, can you see the ping and response? Where does it get dropped?
if I try to ping it it doesn't answer, the unifi logs do show that the packages have been forwarded to the subnet. If I use netcat to open a port on the other device it receives the connection request, but the NAS doesn't recognize it. Maybe I have to do some Wiresharking on a mirror port to see what exactly comes back, hoped I could get around it
I'm a bit hesitant to activate the tag in the DSM, as it states that it then needs a tagged counterpart to be reachable, and since all the other devices in this subnet aren't tagged anymore (as the switch untags the vlan at the port)
Connect a laptop into the same subnet as your Nas (so same vlan and IP range/subnet) and connect to the nas. This either eliminates the NAS or the router from the equation
did that, the NAS is easily reachable from within the subnet it's only a problem from another subnet
Synology not working in different subnet - please help
Hi everyone
I'm fighting with a network issue, where my synology nas doesn't accept any connection from outside it's subnet.
So, here's my setup:
-
Unifi Infrastructure with three separated subnets:
- default:
xxx.xxx.2.0/24
- no vlan - pool with all "safe" devices (notebooks, mobiles, servers etc.) - IoT:
xxx.xxx.83.0/24
- vlan 83 - here are all the IoT devices, including nvidia shield, multiple chromecast music devices etc.) - guest:
xxx.xxx.20.0/20
- vlan 20 - quarantined guest wlan - dns server are locally hosted at
xxx.xxx.2.42 and 43
- default:
-
my I got a new NAS and i designated my old DS214play (running DSM 7.1.1-42962 Update 6) as a Mediaserver that gets to live in the IoT net:
- changed the ip from
xxx.xxx.2.50
toxxx.xxx.83.50
- updated the gateway and subnet
- added the vlan tag 83 on the network port
- updated the firewall to allow all necessary ports from and to the default network (so I can stream plex to my notebooks etc.)
- changed the ip from
-
The Firewall on the NAS is not activated
Issue:
- My NAS doesn't accept any outside connections after moving it to the IoT subnet, neither from my default network nor the internet.
What I tried:
- allowed full access between LAN and IoT subnet for the NAS.
- tried it with another port -> same issue
- connected another device to this port (and setup the same firewall rules) -> this one works fine.
- checked the
unifi firewall logs
--> requests get sent from the nas and answers from the other device - checked
logs of other devices (DNS, NetCat etc.)
--> they receive the requests outside of the subnet, and return their anser but the NAS seems to block/ignore any incoming packages.
What I didn't try:
- setting the VLAN id under
"Network Interface" > "LAN" > "Enable VLAN(802.1Q)"
since, as far as I understand, the Unifi VLAN implementation terminates the VLAN tag at the port of the switch (and all other devices work without specifying it locally) - fully reset the NAS
I'm completely stuck how to solve the issue, so I have moved the NAS back to the default net, but some use cases are not working properly that way, so I'd really like to move it to the IoT subnet. Does anybody have (has?) any hints or knows of some obscure settings which need to be updated? I'd be really grateful for any pointers.
Tried that as well, it's only around 30 seconds off, which annoyingly is enough to mess up OTP challenges
Issue with windows 10 time sync - Need help
Hi everyone, I hope I'm right here with this question and you can help me with an issue that follows me since a few months now where I'm struggling with the NTP synchronization on my windows 10 PC...
The issue only happens with this one device, all other devices can sync their time with whichever ntp server I chose.
I'm even able to contact the ntp server via netcat on this exact device (Opensuse running via WSL), so it's definitely not a network issue:
nc -u -vvv time.windows.com 123 Connection to time.windows.com 123 port [udp/ntp] succeeded!
I tried all the standard solutions:
- stop and restart the
Windows Time
service - change ntp pool
- unregister and re-register via cmd: ``` net stop w32time w32tm /unregister w32tm /register net start w32time w32tm /resync
Sending resync command to local computer The computer did not resync because no time data was available. ``` 4. the peers seem to be listed correctly if I query them:
``` w32tm /query /peers #Peers: 4
Peer: ch.pool.ntp.org,0x9 State: Active Time Remaining: 32723.7373442s Mode: 3 (Client) Stratum: 0 (unspecified) PeerPoll Interval: 0 (unspecified) HostPoll Interval: 10 (1024s)
Peer: ch.pool.ntp.org,0x9 State: Active Time Remaining: 32723.7373539s Mode: 3 (Client) Stratum: 0 (unspecified) PeerPoll Interval: 0 (unspecified) HostPoll Interval: 10 (1024s)
Peer: ch.pool.ntp.org,0x9 State: Active Time Remaining: 32722.7359671s Mode: 3 (Client) Stratum: 0 (unspecified) PeerPoll Interval: 0 (unspecified) HostPoll Interval: 10 (1024s)
Peer: ch.pool.ntp.org,0x9 State: Active Time Remaining: 32722.8440001s Mode: 3 (Client) Stratum: 0 (unspecified) PeerPoll Interval: 0 (unspecified) HostPoll Interval: 10 (1024s) ```
- Group Policies are also as the should be: Link to learn.microsoft
- Defining the servers in the registry
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DateTime\Servers
- Also,
w32tm /stripchart
can contact the server:
w32tm /stripchart /computer:ntp.metas.ch /samples:5 /dataonly Tracking ntp.metas.ch [195.176.26.215:123]. Collecting 5 samples. The current time is 15 Apr 2024 17:06:54. 17:06:54, +19.2982674s 17:06:56, +19.2985170s 17:06:58, +19.2983909s 17:07:00, +19.2982707s 17:07:02, +19.2982836s
In the meantime I even completely wiped the disk and reinstalled windows 10 from scratch, but no luck.
I really don't know what else to do and where to look, since the error messages from windows are also not really helpful.
I also like that with the rest-server you can configure it with append-only, so even if someone wants to encrypt or delete the data they are not able to modify the existing backup
As far as I know you can install Mint with KDE
Also, everybody started the round the same, and it was your skill, knowledge of the map etc. Which made the difference, not if you had unlocked some better scopes or weapons
Yeah, they are more leanient with their customers than with their products...
Yeah our law teacher always stressed that there is a big difference between having a right and getting your right
Jake from the corridor crew did a video speculating what the reasoning is behind it: https://youtu.be/u2dIvUAd5QE?si=rC2Kg_c-hCy0niYF
For filesystems I have another gripe: if I move a file to another directory and I want to swap to the directory I just copied the stuff to I have to enter the whole path again...
If a person set the rule it is definitely not an AI...
I went exactly the same route as you, loved his old videos, HI. At some point I started to listen to the one with Myke (Cortex - had to look up the name) . The first few episodes where quite interesting, but it got repetitive at around episode 50 or so...
Now even the few videos he releases don't really get me anymore