2017-11-21, 19:27
I'm experiencing a weird problem and trying to identify the cause of the problem and not sure where it is happening. I recently put a Mikrotik RB750GR3 in place to replace my (2) consumer grade TP-Link WDR4300 router/access point and the TP-Link devices have been relegated to AP's for now until I can get to configuring the Unifi UAP-AC-PRO.
Anyway, I've split up my network to 4 VLANs (LAN, KIDS, IoT, Guest) and I can get devices to get IP addresses, browse the internet, etc but when I put my Kodi box on the IoT VLAN and my Synology NAS on the same VLAN I can ping, etc I can mount NFS directly within the LibreELEC OS no problem, but from Kodi I cannot seem to do "NFS Browsing" or it is really slow in getting info from the NAS share.
I'm not sure if this is related to avahi not being in the MikroTik and the Mikrotik doesn't have on by default and I've added the Multicast package but I'm not sure what I would need to configure for this as far as IGMP or PIM(?) is concerned besides default setup in Winbox. I'm trying to setup a VM running CentOS (rather than Ubuntu) on my computer to run an an avahi-daemon but struggling with getting the VM to get network connectivity at this point on a VLAN via the trunked port on the host side. Not sure if I'm wasting my time trying to setup a VM for avahi if this is not the source of the problem
https://forum.mikrotik.com/viewtopic.php...hi#p543352
Should the NFS browsing just work without the avahi setup? Even if the mount point is setup (as it was prior to introducing the MIkrotik) it doesn't play any of the media attached to the drive as it just sits there spinning its wheels.
At this point my next step might be trying to mount these file systems on the Linux LibreELEC OS side and referring to the file systems through the local disk within Kodi and see if that works but I'm baffled as to why the NFS browsing isn't working. Is it timing out talking to the Mikrotik trying to query for available NFS servers? However I've put in accept all traffic inbound on the interfaces to the router changing from drop as part of troubleshooting. I would think it is just doing direct connectivity between the Kodi box and the NAS.
Anyway, I've split up my network to 4 VLANs (LAN, KIDS, IoT, Guest) and I can get devices to get IP addresses, browse the internet, etc but when I put my Kodi box on the IoT VLAN and my Synology NAS on the same VLAN I can ping, etc I can mount NFS directly within the LibreELEC OS no problem, but from Kodi I cannot seem to do "NFS Browsing" or it is really slow in getting info from the NAS share.
I'm not sure if this is related to avahi not being in the MikroTik and the Mikrotik doesn't have on by default and I've added the Multicast package but I'm not sure what I would need to configure for this as far as IGMP or PIM(?) is concerned besides default setup in Winbox. I'm trying to setup a VM running CentOS (rather than Ubuntu) on my computer to run an an avahi-daemon but struggling with getting the VM to get network connectivity at this point on a VLAN via the trunked port on the host side. Not sure if I'm wasting my time trying to setup a VM for avahi if this is not the source of the problem
https://forum.mikrotik.com/viewtopic.php...hi#p543352
Should the NFS browsing just work without the avahi setup? Even if the mount point is setup (as it was prior to introducing the MIkrotik) it doesn't play any of the media attached to the drive as it just sits there spinning its wheels.
At this point my next step might be trying to mount these file systems on the Linux LibreELEC OS side and referring to the file systems through the local disk within Kodi and see if that works but I'm baffled as to why the NFS browsing isn't working. Is it timing out talking to the Mikrotik trying to query for available NFS servers? However I've put in accept all traffic inbound on the interfaces to the router changing from drop as part of troubleshooting. I would think it is just doing direct connectivity between the Kodi box and the NAS.
)