--=_courier-7478-1050174978-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Trond Myklebust (trond.myklebust@fys.uio.no) wrote:
> Sounds very much like a network card driver problem.
I don't think so, simply because this has happened to me on two
compeletely different Linux systems. One (griffon) has a 3c59x
card, and the other (dwarf) had a tulip and an ne2k-pci.
(Or did you mean on the server side? The OpenBSD box is using two
RTL 8139 cards.)
> > [5.] nfs: server pegasus not responding, still trying However,
> > this is erroneous. Pegasus (the OpenBSD box) responds
> > perfectly to ping, showmount -e, ssh and so on. Any existing
> > ssh connections to pegasus continue working, even ones I
> > started in an rxvt window in the 15-30 second period when the
> > NFS subsystem hadn't locked up yet. No other errors are
> > reported.
>=20
> .... and a tcpdump would show?
I haven't tried that yet, but after discussing this with another
person who was having the same problems, we learned that OpenBSD's
firewall (pf) was blocking the Linux packets when configured with
"scrub in all" (which is recommended in the OpenBSD FAQs).
After commenting out the "scrub in all" and rebooting back to 2.4.20,
I have X and NFS working simultaneously.
--=20
Greg Wooledge | "Truth belongs to everybody."
greg@wooledge.org | - The Red Hot Chili Peppers
http://wooledge.org/~greg/ |
--=_courier-7478-1050174978-0001-2
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (OpenBSD)
iD8DBQE+mGXAkAkqAYpL9t8RAohjAKDF61A1hE7sJLmPDQOKINuSeD3legCgqc+1
lntcJ+vDpzrdIpHXbz1HqA4=
=Zkst
-----END PGP SIGNATURE-----
--=_courier-7478-1050174978-0001-2--