On Sun, 2019-09-01 at 09:04 -0300, George N. White III wrote:
> On Sat, 31 Aug 2019 at 22:28, John Harris wrote:
>
> > On Saturday, August 31, 2019 1:09:58 AM MST Tom H wrote:
> > > On Thu, Aug 29, 2019 at 5:40 AM John Harris
> > wrote:
> > > >
> > > > NFS over UDP is faster than NFS over TCP.
On 9/1/19 8:04 PM, George N. White III wrote:
> My experience with nfsv4 on linux in this environment was relatively
> free of problems.
+1
But, I didn't want to "argue" about it since it would be OT and like similar OT
matters leads nowhere. :-)
--
If simple questions can be answered with
On Sat, 31 Aug 2019 at 22:28, John Harris wrote:
> On Saturday, August 31, 2019 1:09:58 AM MST Tom H wrote:
> > On Thu, Aug 29, 2019 at 5:40 AM John Harris
> wrote:
> >
> > >
> > >
> > > NFS over UDP is faster than NFS over TCP.
> >
>
Until the ethernet switches get busy -- then it is common to
On Saturday, August 31, 2019 1:09:58 AM MST Tom H wrote:
> On Thu, Aug 29, 2019 at 5:40 AM John Harris wrote:
>
> >
> >
> > NFS over UDP is faster than NFS over TCP.
>
>
> When using nfsv3, yes. But nfsv4 is tcp-only.
nfsv4 is also slower than nfsv3, and isn't as well supported on different
s
On Thu, Aug 29, 2019 at 5:40 AM John Harris wrote:
>
> NFS over UDP is faster than NFS over TCP.
When using nfsv3, yes. But nfsv4 is tcp-only.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedo
On Wednesday, August 28, 2019 3:06:50 AM MST Tom H wrote:
> On Wed, Aug 28, 2019 at 9:21 AM Ed Greshko wrote:
>
>
> > [root@f30-k ~]# firewall-cmd --zone=home --add-port=111/udp --permanent
> > [root@f30-k ~]# firewall-cmd --zone=home --add-port=20048/udp --permanent
>
>
> Is there a reason wh
On Wednesday, August 28, 2019 12:20:13 AM MST Ed Greshko wrote:
> That may not be sufficient depending on the zone an interface is assigned.
Correct. See below.
firewall-cmd --add-service=nfs --zone=$ZONE
firewall-cmd --add-service=nfs --zone=$ZONE --permanent
--
John M. Harris, Jr.
Splentity
On 8/28/19 6:44 PM, Ed Greshko wrote:
> It seems integration has been done with Wifi (see above) but not with wired
> connections.
On second though, there is no reason why you can't have 2 "connections" tied to
the same HW with different zones. You just need to have only one "active" at
any ti
On Wed, Aug 28, 2019 at 12:45 PM Ed Greshko wrote:
> On 8/28/19 6:32 PM, Tom H wrote:
>> On Wed, Aug 28, 2019 at 11:55 AM Ed Greshko wrote:
>>> On 8/28/19 5:44 PM, Tom H wrote:
On Tue, Aug 27, 2019 at 11:52 PM Ed Greshko wrote:
>
> The easiest way to resolve the issue is to place th
On 8/28/19 8:09 PM, Tom H wrote:
> On an nfsv4-only system with its iptables rules flushed. "showmount
> ..." doesn't even work locally (because it needs "rpc.mountd").
>
> # iptables -nL
> Chain INPUT (policy ACCEPT)
> target prot opt source destination
>
> Chain FORWARD (policy
On Wed, Aug 28, 2019 at 12:36 PM Ed Greshko wrote:
> On 8/28/19 6:06 PM, Tom H wrote:
>> On Wed, Aug 28, 2019 at 9:21 AM Ed Greshko wrote:
>>> [root@f30-k ~]# firewall-cmd --zone=home --add-port=111/udp --permanent
>>> [root@f30-k ~]# firewall-cmd --zone=home --add-port=20048/udp --permanent
>>
On Wed, 2019-08-28 at 12:32 +0200, Tom H wrote:
> On Wed, Aug 28, 2019 at 11:55 AM Ed Greshko wrote:
> > On 8/28/19 5:44 PM, Tom H wrote:
> > > On Tue, Aug 27, 2019 at 11:52 PM Ed Greshko
> > > wrote:
> > > > The easiest way to resolve the issue is to place the interface on
> > > > the NFS serve
On 8/28/19 6:32 PM, Tom H wrote:
> On Wed, Aug 28, 2019 at 11:55 AM Ed Greshko wrote:
>> On 8/28/19 5:44 PM, Tom H wrote:
>>> On Tue, Aug 27, 2019 at 11:52 PM Ed Greshko wrote:
The easiest way to resolve the issue is to place the interface on
the NFS server in the "Trusted" firewall zon
On 8/28/19 6:06 PM, Tom H wrote:
> On Wed, Aug 28, 2019 at 9:21 AM Ed Greshko wrote:
>
>> [root@f30-k ~]# firewall-cmd --zone=home --add-port=111/udp --permanent
>> [root@f30-k ~]# firewall-cmd --zone=home --add-port=20048/udp --permanent
> Is there a reason why you don't want to enable "111/tcp"
On Wed, Aug 28, 2019 at 11:55 AM Ed Greshko wrote:
> On 8/28/19 5:44 PM, Tom H wrote:
>> On Tue, Aug 27, 2019 at 11:52 PM Ed Greshko wrote:
>>>
>>> The easiest way to resolve the issue is to place the interface on
>>> the NFS server in the "Trusted" firewall zone. The setting for
>>> that can be
On Wed, Aug 28, 2019 at 9:21 AM Ed Greshko wrote:
> [root@f30-k ~]# firewall-cmd --zone=home --add-port=111/udp --permanent
> [root@f30-k ~]# firewall-cmd --zone=home --add-port=20048/udp --permanent
Is there a reason why you don't want to enable "111/tcp" and
200048/tcp" as "--add-service=rpc-b
On 8/28/19 5:44 PM, Tom H wrote:
> On Tue, Aug 27, 2019 at 11:52 PM Ed Greshko wrote:
>> On 8/28/19 5:45 AM, Bob Goodwin wrote:
>>> My NFS problems continue. The hard drive was replaced, Fedora 30
>>> installed and NFS is configured. I think the configuration is
>>> good, I followed the instructio
On Tue, Aug 27, 2019 at 11:52 PM Ed Greshko wrote:
> On 8/28/19 5:45 AM, Bob Goodwin wrote:
>>
>> My NFS problems continue. The hard drive was replaced, Fedora 30
>> installed and NFS is configured. I think the configuration is
>> good, I followed the instructions anyway.
>>
>> Firewlld appears to
On Tue, Aug 27, 2019 at 11:46 PM Bob Goodwin wrote:
>
> My NFS problems continue. The hard drive was replaced, Fedora 30
> installed and NFS is configured. I think the configuration is good,
> I followed the instructions anyway.
>
> Firewlld appears to be a new stumbling block and I don't know how
On 8/28/19 4:27 PM, Alexander Dalloz wrote:
> Port 20048 translates to the mountd firewalld service.
Oh, right. Forgot about that service. I don't have much use for it.
--
If simple questions can be answered with a simple google query then why are
there so many of them?
_
On 8/28/19 4:27 PM, Alexander Dalloz wrote:
> Am 2019-08-28 09:20, schrieb Ed Greshko:
>
> [ ... ]
>
>> [egreshko@meimei ~]$ showmount -e f30k
>> rpc mount export: RPC: Timed out
>>
>> But then
>>
>> [root@f30-k ~]# firewall-cmd --zone=home --add-port=111/udp
>> success
>> [root@f30-k ~]# firew
Am 2019-08-28 09:20, schrieb Ed Greshko:
[ ... ]
[egreshko@meimei ~]$ showmount -e f30k
rpc mount export: RPC: Timed out
But then
[root@f30-k ~]# firewall-cmd --zone=home --add-port=111/udp
success
[root@f30-k ~]# firewall-cmd --zone=home --add-port=111/udp --permanent
success
Port 111
On 8/28/19 2:52 PM, John Harris wrote:
> The following two commands, in order, add the rule to your running config,
> and
> to your permanent firewall config:
>
> firewall-cmd --add-service=nfs
> firewall-cmd --add-service=nfs --permanent
That may not be sufficient depending on the zone an inter
On Tuesday, August 27, 2019 2:45:42 PM MST Bob Goodwin wrote:
> My NFS problems continue. The hard drive was replaced, Fedora 30
> installed and NFS is configured. I think the configuration is good, I
> followed the instructions anyway.
>
> Firewlld appears to be a new stumbling block and I don'
On 8/27/19 6:47 PM, Ed Greshko wrote:
mount 192.168.2.128:/home /mnt/testb
the format is
mount from_where:what_to_mount mount_point
.
Of course that works.
Thanks Ed.
--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box83 FEDORA-30/64bit LINUX XFCE Fastmail POP3
_
On 8/28/19 6:17 AM, Bob Goodwin wrote:
>
>
> On 8/27/19 6:05 PM, Bob Goodwin wrote:
>>> The easiest way to resolve the issue is to place the interface on the NFS
>>> server in the "Trusted" firewall zone. The setting for that can be found
>>> in the Network Manager GUI for that interface in the
On 8/27/19 6:05 PM, Bob Goodwin wrote:
The easiest way to resolve the issue is to place the interface on the
NFS server in the "Trusted" firewall zone. The setting for that can
be found in the Network Manager GUI for that interface in the
"General Configuration" tab. At least that is what i
On 8/27/19 5:51 PM, Ed Greshko wrote:
On 8/28/19 5:45 AM, Bob Goodwin wrote:
My NFS problems continue. The hard drive was replaced, Fedora 30 installed and
NFS is configured. I think the configuration is good, I followed the
instructions anyway.
Firewlld appears to be a new stumbling block
On 8/28/19 5:45 AM, Bob Goodwin wrote:
> My NFS problems continue. The hard drive was replaced, Fedora 30 installed
> and NFS is configured. I think the configuration is good, I followed the
> instructions anyway.
>
> Firewlld appears to be a new stumbling block and I don't know how to fix it.
>
My NFS problems continue. The hard drive was replaced, Fedora 30
installed and NFS is configured. I think the configuration is good, I
followed the instructions anyway.
Firewlld appears to be a new stumbling block and I don't know how to fix
it. I looked at the Firewalld GUI and there is nothi
30 matches
Mail list logo
