OpenWrt Forum Archive

Topic: Upgrade to 2.6.20 (Layer3-independent conntrack)

The content of this topic has been archived on 21 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi!

Would it be much work to upgrade to kernel 2.6.20?

The background is, that since 2.6.20 it ist possible to use layer-3-independent connection-tracking in conjunktion with NAT.
That means it is possible to have "established/related"-ipv6-netfilter-rules and to use NAT fpr the ipv4-link.

Sadly up to 2.6.19 it is either nat or L3-independant conntrack.

So, wouldn't it be a nice feature for a router-platform? :-)

regards
Patrick

We skip .20 and will go straight to .21 when released.

that's great news!

So I'm looking forward to the release of .21!
You don't feel like trying the rc's, don't you? ;-)

cheers
~patrick

I just don't want to work on getting an rc integrated and then do all the work again on the final release.

Are these weird problems with segmentation fault resolved now (or will be for 2.6.21)?

Last time I checked about a week ago, Kamikaze was really unusable, at least on WL-500g Deluxe and Premium.


Kamikaze r6257 with BusyBox 1.4.0 getting Segmentation fault with ps:

http://forum.openwrt.org/viewtopic.php?id=9363

(Last edited by mangoo on 25 Mar 2007, 17:18)

Should be fixed now. Please test again

Don't call Kamikaze unstable just because you have problems on one target with totally new code.. tongue

There is no wireless yet, or is there something broken with my kernel? It's ASUS WL-500g Deluxe, svn revision 6726:

# lspci
00:00.0 Host bridge: Broadcom Corporation BCM5365P Sentry5 Host Bridge
00:02.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61)
00:02.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61)
00:02.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63)
00:03.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)

# lsmod
Module                  Size  Used by
bcm43xx               423440  0
ieee80211softmac       24672  1 bcm43xx
ieee80211              26336  2 bcm43xx,ieee80211softmac
ieee80211_crypt         2624  1 ieee80211

# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:15:F2:6A:E8:34
          inet addr:192.168.10.55  Bcast:192.168.10.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:174 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:28160 (27.5 KiB)  TX bytes:2998 (2.9 KiB)
          Interrupt:4

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

(Last edited by mangoo on 27 Mar 2007, 22:32)

Just an FYI...
v2.6.21 is out.

How's the status of porting to 2.6.21?

Maybe I can help porting patches?
Since 2.6.22-rc2 is out now, we might have to consider skipping .21,too and porting directly to .22?

Patrick

it is not an easy task, especially when stability comes to mind ... patience is a virtue :-)

acoul wrote:

it is not an easy task, especially when stability comes to mind ... patience is a virtue :-)

That's why I offered my help! :-)

The discussion might have continued from here.