>>>>> "Lennert" == Lennert Buytenhek <[EMAIL PROTECTED]> writes:
This may or may not help isolate the problem, but I am having similar
problems with the 2.2.20 kernel and the patches:
bridge-1.0.2-against-2.2.20.diff
bridge-ipchains-against-1.0.2-against-2.2.20.diff
This is using some Linksys LAN cards and the tulip driver. But just to
make things even more curious, I have a second box with a nearly
identical configuration that does not exhibit the problem. I am
suspicious of the Linksys cards, and will be replacing the system with
something better shortly.
The only significant difference between the two systems is the traffic
level (the one that acts up sees a lot more traffic).
I never saw the problem in a test mode, only when I put the mis-behaving
unit in service. The problem does not go away if you turn off the
ipchains rules, so the rules themselves are not at fault.
If there is any test data I can gather for you please let me know.
A previous setup with the 2.2.19 kernel and matching patches ran fine
for over a year. I'm starting to wish I had just left it alone.
Lennert> Hallo Nederlander, :-) First thing I'd like to know.. is
Lennert> this a kernel or bridge-nf patch issue? If you have time
Lennert> to test, could you try to compare
Lennert> bridge-nf-0.0.6-against-2.4.17.diff vs.
Lennert> bridge-nf-0.0.6-against-2.4.18.diff
Lennert> and
Lennert> bridge-nf-0.0.6-against-2.4.18.diff vs.
Lennert> bridge-nf-0.0.7-against-2.4.18.diff
Lennert> ? Thanks in advance.
Lennert> proost, Lennert
Lennert> On Tue, Oct 01, 2002 at 01:01:00AM +0200, M. P. van Galen
Lennert> wrote:
>> Hello all,
>>
>> After going from kernel 2.4.17 with the bridge-nf patch applied
>> to it (no problems at all), to kernel 2.4.19 with bridge-nf and
>> free-swan patches aplied, everything seems to work fine. But
>> after a certain amount of traffic has passed from the bridge
>> interface to the local network (which isn't firewalled) the
>> interface seems to hang for about 5 minutes. The log shows the
>> output of an nfs-client, but the problem is not nfs specific.
>>
>> /var/log/messages of the firewall shows no information at all.
>>
>> 2.4.18 seemed to have the same problem.
>>
>> During the blocking interface, the bridge keeps functioning, in
>> other words, there is still traffic going from our local network
>> to the internet and vv.
>>
>> Maybe someone has a clue.
>>
>> Cheers, Marijn Netwerknestor Bolkhuis.tudelft.nl
>>
>> P.S. I'm not on the list, so please CC me
>>
>> nfs-client log: Sep 30 23:54:40 serv kernel: nfs: server
>> firewall.bolkhuis not responding, still trying Sep 30 23:54:40
>> serv last message repeated 2 times Sep 30 23:56:42 serv kernel:
>> nfs: task 58285 can't get a request slot Sep 30 23:56:42 serv
>> kernel: nfs: task 58286 can't get a request slot Sep 30 23:56:48
>> serv kernel: nfs: task 58287 can't get a request slot Sep 30
>> 23:58:09 serv kernel: nfs: task 58290 can't get a request slot
>> Sep 30 23:58:13 serv kernel: nfs: task 58291 can't get a request
>> slot Sep 30 23:58:16 serv kernel: nfs: task 58292 can't get a
>> request slot Oct 1 00:00:08 serv kernel: nfs: server
>> firewall.bolkhuis OK
>>
>>
>>
>>
>> _______________________________________________ Bridge mailing
>> list [EMAIL PROTECTED]
>> http://www.math.leidenuniv.nl/mailman/listinfo/bridge
Lennert> _______________________________________________ Bridge
Lennert> mailing list [EMAIL PROTECTED]
Lennert> http://www.math.leidenuniv.nl/mailman/listinfo/bridge
--
David L. Kindred <mailto:[EMAIL PROTECTED]>
Unix Systems & Network Administrator
Telesciences, Inc. <http://www.telesciences.com>
Support: <http://support.telesciences.com>
2000 Midlantic Drive, Suite 410, Mt. Laurel, NJ 08054
Tel: +1.856.866.1000 ext. 4184
Fax: +1.856.866.0185
Cel: +1.609.413.6205
Pgr: +1.800.689.5182
SMS: <mailto:[EMAIL PROTECTED]>
---
_______________________________________________
Bridge mailing list
[EMAIL PROTECTED]
http://www.math.leidenuniv.nl/mailman/listinfo/bridge
