Browsing nfs share in other VLAN not working.
-
Yeah you could/might be able to get it to work across your L2 if its using that mode of discovery, if your NFS server is publishing it..
That is what is broke with this software... Why don't you just directly map your nfs?
-
@johnpoz said in Browsing nfs share in other VLAN not working.:
That is what is broke with this software... Why don't you just directly map your nfs?
That works fine with Kodi too. It's just not as comfortable having to enter the IP address by hand.
-
Just put in the FQDN ;)
Its a freaking 1 time thing ;)
-
But it also depends on which version NFS he's using.
-
Why the fqdn has nothing to do with nfs..
How freaking hard is to run basic network services on your own network like resolving a known server that shares nfs to a fqdn.. That has zero to do what version of nfs he is running which I would assume is 4+
Getting ready to take a vac to SD where my son moved for 12 days, and then full month over the summer out there.. Maybe I just need a break from "users" ;)
I mean really what does this have to do with pfsense, or even basic common sense for that matter? This has zero do do with routing, pfsense, firewalling.. this is understanding basic networking and how a machine accesses nfs share.. He clearly is allowing 111, etc.. What his client or server might do for some L2 discovery has zero to do with firewalls or vlans or whatever this is per application stuff..
He he doesn't understand how his client "finds" his server then the should be asking his OS or application support or his "server" forum.. This has nothing to do with L2/Switching/Vlans to be honest..
I really want to help the guy - but not understanding your own applications is not what we are here to support.. Did we become a "everything" support forum when I wasn't looking? ;) Which I am happy to do by the way, but I was not aware of the netgate/pfsense desire to support all of IT ;)
Man I need a few weeks just drinking myself to oblivion and playing with my grand kids :)
Sorry!!! ;)
-
@johnpoz said in Browsing nfs share in other VLAN not working.:
Why the fqdn has nothing to do with nfs..
How freaking hard is to run basic network services on your own network like resolving a known server that shares nfs to a fqdn.. That has zero to do what version of nfs he is running which I would assume is 4+
Getting ready to take a vac to SD where my son moved for 12 days, and then full month over the summer out there.. Maybe I just need a break from "users" ;)
I mean really what does this have to do with pfsense, or even basic common sense for that matter? This has zero do do with routing, pfsense, firewalling.. this is understanding basic networking and how a machine accesses nfs share.. He clearly is allowing 111, etc.. What his client or server might do for some L2 discovery has zero to do with firewalls or vlans or whatever this is per application stuff..
He he doesn't understand how his client "finds" his server then the should be asking his OS or application support or his "server" forum.. This has nothing to do with L2/Switching/Vlans to be honest..
I really want to help the guy - but not understanding your own applications is not what we are here to support.. Did we become a "everything" support forum when I wasn't looking? ;) Which I am happy to do by the way, but I was not aware of the netgate/pfsense desire to support all of IT ;)
Man I need a few weeks just drinking myself to oblivion and playing with my grand kids :)
Sorry!!! ;)
Hi John,
No need to say sorry! I know I am not a networking gure like you guys are. At least I try to figure out things and learn. But I understand you to the fullest because I have to deal also with the same in our company with customers who have 0.1% IT knowledge. But they need the IT to do their work so I have to help them... So no need to say sorry!
Regards Herman
-
@grimson said in Browsing nfs share in other VLAN not working.:
@johnpoz said in Browsing nfs share in other VLAN not working.:
That is what is broke with this software... Why don't you just directly map your nfs?
That works fine with Kodi too. It's just not as comfortable having to enter the IP address by hand.
Hi @Grimson. Correct. Adding the shares by hand in the XML sources file works fine. I just like to figure out why the hell I get it not working with the discovery function in vlans. Just to learn how it works. I understand that @johnpoz gets pissed because my lack of basic knowledge, but we all need to start somewhere. My working field not only networking and pfSense but I have to do so many things also. Like I said before I am always willing to learn and to know how things work. Just do the trick is not satisfying for me! Does this make sense?
There is also said that multi homing is not recommend. How else I can balance the load on my network. When the family is watching a movie and I start to copy large files the movie stutters or even stops. And the kids do not appreciate that :-)
From what I've read vlan's could be a solution. Not only for security reasons but also for permanence reasons. In my opinion do vlans over more network cards is even better. Shoot me if you like :-)
Regard,
HermanLimburg | The Netherlands.
It is nice to be important. But it is more important to be nice! | Failure, the best teacher it is! -
@herman said in Browsing nfs share in other VLAN not working.:
When the family is watching a movie and I start to copy large files the movie stutters or even stops. And the kids do not appreciate that :-)
If your loading up the server, might not matter if your on another interface or not if your sucking up the I/O to a shared disk or CPU of the machine. If your on a switch you doing something between A and B doesn't effect traffic between C and D..
Adding another interface on B, will only solve the problem of stuttering a streaming movie if the only problem was saturation of the interface.. But if your working with the same disk that the movie is streaming from... Your issue might not be network bandwidth it could be your hitting the I/O of the disk limits, or the cpu of the server streaming, etc..
An intelligent man is sometimes forced to be drunk to spend time with his fools
If you get confused: Listen to the Music Play
Please don't Chat/PM me for help, unless mod related
SG-4860 24.11 | Lab VMs 2.8, 24.11 -
@herman said in Browsing nfs share in other VLAN not working.:
Hi @Grimson. Correct. Adding the shares by hand in the XML sources file works fine.
No need to fiddle with the XML, just use the "Add network location..." option from the GUI, see: https://kodi.wiki/view/Adding_video_sources#Adding_Remote_sources
RTFM does apply to everything, not only pfSense.
I understand that johnpoz gets pissed because my lack of basic knowledge, but we all need to start somewhere.
Yes, and there are many books and online resources that will teach you the basic knowledge. A support forum is not the place to teach you this, if you want a teacher take a course at a school.
-
@johnpoz said in Browsing nfs share in other VLAN not working.:
@herman said in Browsing nfs share in other VLAN not working.:
When the family is watching a movie and I start to copy large files the movie stutters or even stops. And the kids do not appreciate that :-)
If your loading up the server, might not matter if your on another interface or not if your sucking up the I/O to a shared disk or CPU of the machine. If your on a switch you doing something between A and B doesn't effect traffic between C and D..
Adding another interface on B, will only solve the problem of stuttering a streaming movie if the only problem was saturation of the interface.. But if your working with the same disk that the movie is streaming from... Your issue might not be network bandwidth it could be your hitting the I/O of the disk limits, or the cpu of the server streaming, etc..
Thank you @johnpoz for the info... I wil dig in it.
