TFTP crashes the linux system...

TFTP crashes the linux system...

[Gautham Thavva]

I have enforced a firewall, using iptables-1.2.6a, on a target board running TimeSys Linux Kernel(Kernel version is 2.4.7-10).

I have applied the *tftp* patch available in the patch-o-matic. 

When I try to do a tftp "get" or "put" from a PC in a different subnet to this board, the system crashes. An Oops is generated during the init_conntrack function in ip_conntrack_core.c

Code Snippet (either Line #545 or Line #552) from init_conntrack where Oops is generated... 
Line #545 expected = LIST_FIND(&expect_list, expect_cmp, struct ip_conntrack_expect *, tuple);

Line #552 if (expected && is_confirmed(expected->expectant)) {

But the system doesnt crash if a default route has been configured.

Please can someone share their insight as to why the absence of the default route causes the system to generate Oops during TFTP operations.

With regards,
Gautham Thavva


____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005

Re: TFTP crashes the linux system...

[Harald Welte]

[-- Attachment #1: Type: text/plain, Size: 963 bytes --]

On Mon, Jan 26, 2004 at 06:20:20PM -0500, Gautham Thavva wrote:
> 
> I have enforced a firewall, using iptables-1.2.6a, on a target board running TimeSys Linux Kernel(Kernel version is 2.4.7-10).
> 
> I have applied the *tftp* patch available in the patch-o-matic. 

i strongly doubt that you will get this wokring with such an incredibly
old kernel...  You'd basically need to backport more than two years of
netfilter/iptables development on top of 2.4.7...

The patch-o-matic README doesn indicate that it only supports 2.4.18 and
later.

> With regards,
> Gautham Thavva

-- 
- Harald Welte <laforge@netfilter.org>             http://www.netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]