Date: Mon, 21 Jan 2002 21:02:31 -0000 From: =?iso-8859-1?Q?Bj=F6rn_Patrick_Swift?= <bjorn@innn.is> To: 'Ian' <freebsd@damnhippie.dyndns.org>, freebsd-stable <freebsd-stable@FreeBSD.ORG> Subject: RE: mountd / nfsd problems Message-ID: <6973E4999161D411A57600010233D19797EFFA@exchange.is.innn.is>
next in thread | raw e-mail | index | archive | help
Dear Ian.
This was exactly the problem. I added ipfw add allow all from 127.0.0.1 =
to
any via xl0 and that did the trick.
Thank you for your advice.
Bj=F6rn Swift
-----Original Message-----
From: Ian [mailto:freebsd@damnhippie.dyndns.org]=20
Sent: 21. jan=FAar 2002 18:17
To: freebsd-stable
Subject: Re: mountd / nfsd problems
> Yesterday I upgraded one of my machines to 4.5-RC and I've been =
having
some
> strange problems with nfsd since then. When the machine is booting up =
I
get
> the following error message:
>=20
> RPC: Program not registered
>=20
> and the /var/log/messages says:
>=20
> mountd[76]: can't register mount
> nfsd:[78]: can't register with udp portmap
>=20
> Using Google I was able to find some people having a similar problem =
but
it
> seemed as their problem was in the hosts.allow file, which I didn't =
alter
> while running mergemaster.
>=20
> I have two ethernet cards in the machine xl0 and xl1. xl0 is facing =
the
> world and xl1 is a crossover cable to an other machine acting as a =
nfs
> client. These are my ipfw rules:
> 00100 allow ip from 194.x.x.11 to any <- localhost
> 00200 allow ip from any to any via xl1 <- crossover to nfs
> client
> 00300 allow tcp from 194.x.x.1 to 194.144.186.11 25
> 00600 allow tcp from 194.x.x.1 to 194.144.186.11 1005-65535
> 00700 allow udp from 194.x.x.1 to 194.144.186.11 1005-65535
> 65535 deny ip from any to any
>=20
> Could the ipfw rules be the problem?
I just had exactly the same set of NFS error messages at startup. In =
my
case it was because I had accidentally enabled the firewall in the =
machine's
config, and that machine had only the default deny rule. Easily fixed.
But, it makes me think that the answer to your question might well be =
Yes,
the ipfw rules could be the problem.
I notice you don't have the "customary" rules
100 allow ip from any to any via lo0
200 deny ip from any to 127.0.0.0/8
I wonder if that could be the cause? I rediscovered the hard way a =
couple
weeks ago that these rules are normally installed by rc.firewall in =
addition
to any config file you specify in rc.conf, but if you manually do an =
ipfw
flush then reinstall your usual rules you lose these two automatic =
rules.
-- Ian
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6973E4999161D411A57600010233D19797EFFA>