Re: nf_conntrack_ipv4 must be loaded explicitly

On Aug 2 2007 20:33, Patrick McHardy wrote:
>> End result:
>>
>> After loading nf_conntrack_ipv4.ko, everything works again (also with the
>> "bad" ff09b7). But I have to load it explicitly, and I think that
>> unfortunately breaks a lot of setups (such as mine) which assume ipv4
>> connection tracking is always there.
>
> I already have a patch for this queued. I'll push it upstream once
> I get a new power supply for the box I keep that tree on, hopefully
> tommorrow.

What's that patch looking like?



thanks,
	Jan
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: nf_conntrack_ipv4 must be loaded explicitly
  - From: Patrick McHardy <[email protected]>

References:
- nf_conntrack_ipv4 must be loaded explicitly
  - From: Jan Engelhardt <[email protected]>
- Re: nf_conntrack_ipv4 must be loaded explicitly
  - From: Patrick McHardy <[email protected]>

Prev by Date: Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
Next by Date: Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures
Previous by thread: Re: nf_conntrack_ipv4 must be loaded explicitly
Next by thread: Re: nf_conntrack_ipv4 must be loaded explicitly
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]