On Tue, Jan 09, 2024 at 07:27:47AM +0100, Otto Moerbeek wrote:
> resreved means that the port number is below 1024. The RPC system,
> (which is used to implement NFS) iuses portmapper to determine which
> service runs on which port. What problem are you trying to solve?
I'm not a fan of that
> On Tue, Jan 09, 2024 at 10:13:56AM +0300, 4 wrote:
> No need to be so dramatic, the ports only change when the service is
> restarted, so there is no need for constant monitoring and/or script
> running. Either you run the script (a one-liner, by the way, see below)
> on the server upon
> On Tue, Jan 09, 2024 at 10:13:56AM +0300, 4 wrote:
> These kind of off-topic remarks won't help you getting answers,
> -Otto
"i'm only human after all
don't put your blame on me"
On Tue, Jan 09, 2024 at 10:13:56AM +0300, 4 wrote:
> >> i'm quoting the man page for mountd:
> >> The -n flag historically allowed clients to use non-reserved ports
> >> when
> >> communicating with mountd. In OpenBSD, a reserved port is always
>
On Tue, Jan 09, 2024 at 10:13:56AM +0300, 4 wrote:
> i'm trying to solve the problem of which port need to open on the pf. the
> variant of processing rpcinfo output with script and then putting a rules
> into an anchor is not very pretty. especially considering that this is not
> enough, and i
On Tue, Jan 09, 2024 at 10:13:56AM +0300, 4 wrote:
> >> i'm quoting the man page for mountd:
> >> The -n flag historically allowed clients to use non-reserved ports
> >> when
> >> communicating with mountd. In OpenBSD, a reserved port is al
>> i'm quoting the man page for mountd:
>> The -n flag historically allowed clients to use non-reserved ports when
>> communicating with mountd. In OpenBSD, a reserved port is always used.
>> "reserved port". "always".. however the
On Tue, Jan 09, 2024 at 04:16:43AM +0300, 4 wrote:
> i'm quoting the man page for mountd:
> The -n flag historically allowed clients to use non-reserved ports when
> communicating with mountd. In OpenBSD, a reserved port is always used.
> "reserved port". "
i'm quoting the man page for mountd:
The -n flag historically allowed clients to use non-reserved ports when
communicating with mountd. In OpenBSD, a reserved port is always used.
"reserved port". "always".. however the port is different each time. how to
deal with this?
from guenther to otheruser,
pkill -HUP mountd, then testing by creating a file in a mode 777
directory on the NFS mount from 127.0.0.1. Various other switches and
tests show that it doesn't seem to be related to the sorting of the
directory names.
So: need more data. Run mountd
On Saturday, November 10, 2012 04:35:33 PM Philip Guenther wrote:
Hmm, it works for me, using an exports of
/usr/src -mapall=guenther 127.0.0.1
/usr/obj -mapall=guenther 127.0.0.1
and switching the -mapall on /usr/src from guenther to otheruser,
pkill -HUP mountd, then testing by creating
,
pkill -HUP mountd, then testing by creating a file in a mode 777
directory on the NFS mount from 127.0.0.1. Various other switches and
tests show that it doesn't seem to be related to the sorting of the
directory names.
So: need more data. Run mountd yourself with the -d option and snag
if we change
the mapall user to something else (say, testuser2), and reload the
configuration, the permissions on created files act as if we have not
made any changes.
If we do /etc/rc.d/mountd restart, mountd eventually stops running,
but no startup takes place. if we verify it isn't running
mountd and and imaps occupies the same port 993.
Are the any good ways of telling openbsd that mountd should not use
that port.
The quick n'dirty solution is to kill mountd in rc.local and start it up
again after the imap mailserver has occupied the port and then start up
mountd again
On Thu, Jul 2, 2009 at 1:18 AM, Per-Erik Perssonp...@fos.su.se wrote:
mountd and and imaps occupies the same port 993.
Are the any good ways of telling openbsd that mountd should not use that
port.
...
Upgrade to OpenBSD 4.4 or later, as that version made /etc/rc
automatically tell
I am running 4.3 and the problem arised after upgrading from a previous
version.
Well spotted :-)
Thanks a lot!
Philip Guenther wrote:
On Thu, Jul 2, 2009 at 1:18 AM, Per-Erik Perssonp...@fos.su.se wrote:
mountd and and imaps occupies the same port 993.
Are the any good ways of telling
From: [EMAIL PROTECTED]
i file nfs traffic into the stuff not supposed to be going through
the firewall category. a firewall implies there are bad people on
one side of it, and you don't want bad people to access nfs, ever.
i'd use a vpn of some sort to tunnel through the firewall.
I
Christian Rueger wrote:
Am Mittwoch, den 21.06.2006, 14:03 -0700 schrieb Clint Pachl:
Because portmap(8) dynamically assigns the mountd(8) port, how would
one write a pass rule in pf for mountd(8) traffic? My problem is that
every time mountd(8) is re/started, it operates on a different port
Ted Unangst wrote:
On 6/21/06, Clint Pachl [EMAIL PROTECTED] wrote:
Because portmap(8) dynamically assigns the mountd(8) port, how would
one write a pass rule in pf for mountd(8) traffic? My problem is that
every time mountd(8) is re/started, it operates on a different port and
my fixed pf
Scott Francis wrote:
On 6/23/06, Theo de Raadt [EMAIL PROTECTED] wrote:
[snip]
http://www.freebsd.org/cgi/man.cgi?query=mountd
It's definitely possible (Free and Net both offer the -p option).
I think that is completely ridiculous. Hardcoding RPC utilities
to non-random ports to try
On 6/24/06, Clint Pachl [EMAIL PROTECTED] wrote:
Scott Francis wrote:
On 6/23/06, Theo de Raadt [EMAIL PROTECTED] wrote:
[snip]
http://www.freebsd.org/cgi/man.cgi?query=mountd
It's definitely possible (Free and Net both offer the -p option).
I think that is completely ridiculous
On 6/21/06, Clint Pachl [EMAIL PROTECTED] wrote:
Because portmap(8) dynamically assigns the mountd(8) port, how would
one write a pass rule in pf for mountd(8) traffic? My problem is that
every time mountd(8) is re/started, it operates on a different port and
my fixed pf rules block the mount
On 6/21/06, Clint Pachl [EMAIL PROTECTED] wrote:
Because portmap(8) dynamically assigns the mountd(8) port, how would
one write a pass rule in pf for mountd(8) traffic? My problem is that
every time mountd(8) is re/started, it operates on a different port and
my fixed pf rules block the mount
On 6/21/06, Clint Pachl [EMAIL PROTECTED] wrote:
Because portmap(8) dynamically assigns the mountd(8) port, how would
one write a pass rule in pf for mountd(8) traffic? My problem is that
every time mountd(8) is re/started, it operates on a different port and
my fixed pf rules block
to pass mount protocol traffic (mountd/NFS) using pf?
On 6/21/06, Clint Pachl [EMAIL PROTECTED] wrote:
Because portmap(8) dynamically assigns the mountd(8) port, how would
one write a pass rule in pf for mountd(8) traffic? My problem is that
every time mountd(8) is re/started, it operates
On 6/23/06, Theo de Raadt [EMAIL PROTECTED] wrote:
[snip]
http://www.freebsd.org/cgi/man.cgi?query=mountd
It's definitely possible (Free and Net both offer the -p option).
I think that is completely ridiculous. Hardcoding RPC utilities
to non-random ports to try to tie it to something
Am Mittwoch, den 21.06.2006, 14:03 -0700 schrieb Clint Pachl:
Because portmap(8) dynamically assigns the mountd(8) port, how would
one write a pass rule in pf for mountd(8) traffic? My problem is that
every time mountd(8) is re/started, it operates on a different port and
my fixed pf rules
Because portmap(8) dynamically assigns the mountd(8) port, how would
one write a pass rule in pf for mountd(8) traffic? My problem is that
every time mountd(8) is re/started, it operates on a different port and
my fixed pf rules block the mount protocol and, consequently, my
clients cannot mount
Because portmap(8) dynamically assigns the mountd(8) port, how would
one write a pass rule in pf for mountd(8) traffic? My problem is that
every time mountd(8) is re/started, it operates on a different port and
my fixed pf rules block the mount protocol and, consequently, my
clients cannot
Trying to get OS X to mount an openbsd nfs share. I can force OS X to
use reserved ports by using mount_nfs -P from the command line, but
users mounting from the finder don't have that option.
OpenBSD man page for mountd says that there is an -n option to allow
mounting from unreserved ports
Will H. Backman wrote:
Trying to get OS X to mount an openbsd nfs share. I can force OS X to
use reserved ports by using mount_nfs -P from the command line, but
users mounting from the finder don't have that option.
OpenBSD man page for mountd says that there is an -n option to allow
31 matches
Mail list logo
