On Fri, 2 Jul 2004, Tom Allison wrote:
> I guess what I should be asking is where/how do I bind specific ports?
>
> I can't find anything in the man pages (at least the ones I'm looking
> at) to set this up. I am running the kernel based server so I may have
What I had in mind was to add the o
Ernest Johanson wrote:
Right. It can go in /etc/init.d or in /etc/network/interfaces. Probably
better in interfaces so the rules are applied as soon as the interfaces
are up.
I got the distinct impression that running firewall scripts using the
/etc/network/if-up.d and /etc/network/if-down.d dire
Right. It can go in /etc/init.d or in /etc/network/interfaces. Probably
better in interfaces so the rules are applied as soon as the interfaces
are up.
On Sat, 3 Jul 2004, Tom Allison wrote:
> Ernest Johanson wrote:
> > Good refinement to tighten things up.
> >
> >
>
> Thanks.
>
> I thought it w
Ernest Johanson wrote:
Good refinement to tighten things up.
Thanks.
I thought it would be necessary to re-run rpcinfo each time I booted
because I can't find anything that says these ports are a certainty.
That, and I only have NFS 3 support that I have to worry about.
# NFS
# First you open
Good refinement to tighten things up.
On Fri, 2 Jul 2004, Tom Allison wrote:
> Ernest Johanson wrote:
> > Been following this thread and understand that the goal is to configure a
> > firewall to control access to the ports used for NFS. If so, then suggest
> > the following:
> >
> > #!/bin/sh
>
Ernest Johanson wrote:
Been following this thread and understand that the goal is to configure a
firewall to control access to the ports used for NFS. If so, then suggest
the following:
#!/bin/sh
NFSPORTS=`rpcinfo -p | awk '/tcp/||/udp/ {print $4}' | sort | uniq`
for PORT_NUM in $NFSPORTS
do
On Fri, 2 Jul 2004, Tom Allison wrote:
> /etc/exports:
> /var/www192.168.1.0/24(rw,no_root_squash)
>
> These are identical on both machines
> /etc/hosts.allow is identical on both machines (empty)
to allow only certain machines to connect and disallow others
on the NFS server:
server
Been following this thread and understand that the goal is to configure a
firewall to control access to the ports used for NFS. If so, then suggest
the following:
#!/bin/sh
NFSPORTS=`rpcinfo -p | awk '/tcp/||/udp/ {print $4}' | sort | uniq`
for PORT_NUM in $NFSPORTS
do
iptables -A INPUT -j
--- [EMAIL PROTECTED] wrote:
> But I'm wondering what it is that I'm missing.
> Is this the difference between kernel and user nfs servers?
> Are there some args to pass at modprobe time?
Not in terms of options -- NFS configuration is done in the userland level
usually.
-- Thomas Adam
=
"
> On Fri, 02 Jul 2004 05:10:10 +0200, Tom Allison wrote:
>> Portmapper sits on one port, but it's redirecting the nfs connection all
>> over the place. I can't seem to nail it down to one set of ports.
>
> The only way I can think of sorting this out would be to allow any
> packets between the ser
On Fri, 02 Jul 2004 05:10:10 +0200, Tom Allison wrote:
> Portmapper sits on one port, but it's redirecting the nfs connection all
> over the place. I can't seem to nail it down to one set of ports.
The only way I can think of sorting this out would be to allow any
packets between the server and
Tadeusz Bak wrote:
On Thu, 1 Jul 2004, Tom Allison wrote:
Portmapper sits on one port, but it's redirecting the nfs connection all
over the place. I can't seem to nail it down to one set of ports.
The rpc services called by portmaper can be binded to specific ports, see
man pages for details. To
Tadeusz Bak wrote:
On Thu, 1 Jul 2004, Tom Allison wrote:
Portmapper sits on one port, but it's redirecting the nfs connection all
over the place. I can't seem to nail it down to one set of ports.
The rpc services called by portmaper can be binded to specific ports, see
man pages for details. To
On Thu, 1 Jul 2004, Tom Allison wrote:
> Portmapper sits on one port, but it's redirecting the nfs connection all
> over the place. I can't seem to nail it down to one set of ports.
The rpc services called by portmaper can be binded to specific ports, see
man pages for details. To find out wha
Thomas Adam wrote:
--- Tom Allison <[EMAIL PROTECTED]> wrote:
What are my options?
Do I have to hard code the port number into the
/etc/default/nfs-kernel-server and the client fstab files and the
iptables script?
What about changing the port that portmapper listens on?
Portmapper sits on one
--- Tom Allison <[EMAIL PROTECTED]> wrote:
> What are my options?
>
> Do I have to hard code the port number into the
> /etc/default/nfs-kernel-server and the client fstab files and the
> iptables script?
What about changing the port that portmapper listens on?
-- Thomas Adam
=
"The Lin
16 matches
Mail list logo
