![]() ![]() ![]() ![]() |
|
A new SRM 1.3 RC (Release Candidate) is out now and is available for other models as well: Release Notes for SRM | Synology Inc.
Please support Geekzone by subscribing, or using one of our referral links: Samsung | AliExpress | Wise | Sharesies | Hatch | GoodSync | Backblaze backup
not sure whether to start a new thread or not but will try my luck here first...
Managed to get my hands on one of these routers and for the most part it is working fine. However I just cannot figure out why wired clients hostnames, in the primary network cannot be resolved by either the router itself via the network tools, or other wireless clients. Pinging IP address works from any machine and pinging a wired device from another wired device on the same network is successful using IP or name (so a DNS record must be registered somewhere). All clients are using DHCP handled by the Synology router.
If it makes any difference I have a Synology NAS, QNAP NAS and Windows 11 client that are all wired clients and none of their hostnames can be resolved.
Any ideas anyone?
Do surveys for Beer money (referral link) - Octopus Group
Link for buying beer (not affiliated, just like beer) - Good George
Are wireless clients on the same network or a new one? If a new one, make sure you didn't check "Network isolation" which does what the name says.
Please support Geekzone by subscribing, or using one of our referral links: Samsung | AliExpress | Wise | Sharesies | Hatch | GoodSync | Backblaze backup
I have created a few different wireless networks however the wireless clients that I am testing with, are on the same network as the wired clients. I've also disabled all the firewall rules I had in place (which I was using for my IoT network) even though I dont see how they could be interfering.
Also found that wired clients can resolve and ping wireless clients on the same network (i.e. my office pc 10.0.0.50 can resolve and ping my mac on 10.0.0.51 but not vice versa via hostname). I'm starting to wonder if the router is sending the resolution requests upstream to 2degrees or something instead of resolving it locally but dont have enough linux foo to ssh to the router and figure it out (yet).
I'm normally pretty good at figuring this kind of stuff out but it really has me baffled this time.
Do surveys for Beer money (referral link) - Octopus Group
Link for buying beer (not affiliated, just like beer) - Good George
Do surveys for Beer money (referral link) - Octopus Group
Link for buying beer (not affiliated, just like beer) - Good George
Can't see any way to have the native VLAN tagged on a trunk, seems to be always untagged. I can work around that, but wondering if I'm missing something.
Just received the new Synology WRX560 here and added it to my RT6600ax network as a mesh node. Couldn't be easier and quicker (via Ethernet):
Please support Geekzone by subscribing, or using one of our referral links: Samsung | AliExpress | Wise | Sharesies | Hatch | GoodSync | Backblaze backup
|
![]() ![]() ![]() ![]() |