| To: | Yann Dupont <Yann.Dupont@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: dst cache overflow on 2.2.16 kernel. |
| From: | Chris Wedgwood <cw@xxxxxxxx> |
| Date: | Tue, 17 Jul 2001 02:52:51 +1200 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <3B52FC3B.7050107@xxxxxxxxxxxxxxxxxxx> |
| References: | <3B52FC3B.7050107@xxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.18i |
On Mon, Jul 16, 2001 at 04:37:47PM +0200, Yann Dupont wrote:
Sorry for my poor english ...
Mine is probably worse.
fw-1 is a module that sits beetwen the IP layer & the interface
(Well. I think it perform like this. Mayne I'm totally wrong here)
I assume it works this way.
So even if I can ping 127.0.0.1, Maybe it blocks acces to lo for
some other programs.
Depending on the rules, it may well do so. I don't think that is the
cause here, its just the reported error I have seen as the result of
there being no loopback device.
As the firewall as been installed by a 3rd party - And not very
well installed, because there are LOTS of daemons still there - I
can't say...
Does the problem still occur with the firewall unloaded?
--cw
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: dst cache overflow on 2.2.16 kernel., Yann Dupont |
|---|---|
| Next by Date: | hard_start_xmit behavior, Noah Romer |
| Previous by Thread: | Re: dst cache overflow on 2.2.16 kernel., Yann Dupont |
| Next by Thread: | hard_start_xmit behavior, Noah Romer |
| Indexes: | [Date] [Thread] [Top] [All Lists] |