On Mon, 2006-06-19 at 14:53 +0200, Ralph Slooten wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Matthias Langer wrote:
> > i'm not sure which of these lines acually fixed my problem as i've just
> > looked at the output of rpcinfo and grabbed all nfs relevant ports from
> > there.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthias Langer wrote:
> i'm not sure which of these lines acually fixed my problem as i've just
> looked at the output of rpcinfo and grabbed all nfs relevant ports from
> there.
This will probably fix your problems *until* you restart nfs.
# lsof -
On Mon, 2006-06-19 at 07:24 +0200, Ralph Slooten wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Matthias Langer wrote:
> > i've recently set up a local nfs server for my disfiles; to keep the WAN
> > out i have:
> >
> > iptables -A INPUT -p TCP -i ! ${LAN} -d 0/0 --dport nfs -j DROP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthias Langer wrote:
> i've recently set up a local nfs server for my disfiles; to keep the WAN
> out i have:
>
> iptables -A INPUT -p TCP -i ! ${LAN} -d 0/0 --dport nfs -j DROP
> iptables -A INPUT -p UDP -i ! ${LAN} -d 0/0 --dport nfs -j DROP
>
>
i've recently set up a local nfs server for my disfiles; to keep the WAN
out i have:
iptables -A INPUT -p TCP -i ! ${LAN} -d 0/0 --dport nfs -j DROP
iptables -A INPUT -p UDP -i ! ${LAN} -d 0/0 --dport nfs -j DROP
everthing is working fine so far; however, my logs are full with these
messages:
sv
5 matches
Mail list logo