Sorry for the double post, initially posted in the wrong forum group

First of all, great work on this. I am using buildroot to build my toolchains, I find it superior, cleaner and more reliable than other tools designed to do the same thing. Without going thru all the scripts, etc....I would like to know how to control or choose the kernel used, 2.6.18.1 vs 2.6.17, 2.6.19.1 etc ? Is there an easyway to do this as it is not an option in menuconfig.

I also may be reading older documentation, but I don't believe so, the documentation that I am reading suggest an option for changing the staging_dir outside of buildroot, however that option does not exist in menuconfig, as is in the documentation.

Build options ->  Toolchain and header file location, which defaults to staging_dir_ARCH/.

current SVN 5899

Any help appr.

Hi,
I had a Linksys WRT54G (ver 1.0) bought a while ago.  Had assigned it a local address 172.16.0.68.  Had set up admin password, encripted wireless trasmission etc., until a week ago I decided to go for openwrt, because I was excited about it that it will give me the flexibility of a linux system.

I followed the documentation, downloaded the white russian openwrt for pppoe, sqash FS and followed the recommended way to flash using the Linksys web-interface and flashed the router.  The flashing was successful.  One thing I didn't (and couldn't do) was to set the boot_wait.   Searched the router documentation, but couldn't find a way to do it.

Now, I cannot login.  I can ping well.  However, neither telnet nor ssh work.  I am immediately kicked out with a message:

telnet: connect to address 172.16.0.68: Connection refused.

I try ssh and the same again:

ssh: connect to address 172.16.0.68: port 22: Connection refused.

I think that reflashing wouldn't help.   I don't remember closing any ports on the router previously with the default linksys firmware.  However, I did have encription enabled on the wireless interface with strict mac address checks.

The router seems to boot well, with Power (green) and Diag (red) light coming ON and then after about 10 secs the DMZ (green) light switch comes on, followed by Link (green) and a couple of blinks on Act.  Finally, the power, link and top light in the internet box stay on.   I have connected it to the up-link ethernet interface and I can ping it well without any loss of packets.

I searched the forum posts for similar problems.  Couldn't find any so far.

Can somebody out there help me?
Thanks in advance.

@m_osgood: you're posting in the wrong thread.
@TornadoCFE: There is no easy way to do this, since the new kernel patches no longer apply to old kernels. Why do you want to do this anyway?

ndb,
Thanks, that was the answer I was looking for.

I am also using OpenWRT as buildroot system for other non-router targets. What I did for my own ARM board (the vendor delivers only a patch for 2.4.26 that doesn't apply on 2.4.33.4) is the following:
I've created a new target for my board (ts7300) with the following Makefile that overrides the default 2.4.33.4 kernel and the default kernel preparation routine
Disadvantage is of course that you do not get the generic 2.4 patches (but I didn't need them).

include $(TOPDIR)/rules.mk

ARCH:=arm
BOARD:=ts7300
BOARDNAME:=Technologic Systems TS7300 board
FEATURES:=

define Target/Description
    Build firmware images for the Technologic Systems TS7300 ARM board
endef

LINUX_VERSION:=2.4.26
LINUX_RELEASE:=1
LINUX_KERNEL_MD5SUM:=88d7aefa03c92739cb70298a0b486e2c

define Kernel/Prepare/ts7300
    bzcat $(DL_DIR)/$(LINUX_SOURCE) | tar -C $(KERNEL_BUILD_DIR) $(TAR_OPTIONS)
    # [ -d ../generic-$(KERNEL)/patches ] && $(PATCH) $(LINUX_DIR) ../generic-$(KERNEL)/patches 
    [ -d ./patches ] && $(PATCH) $(LINUX_DIR) ./patches
endef

# Override Kernel/Prepare from kernel-build.mk to prevent patching with generic-2.4 patches for 2.4.33.4
override define Kernel/Prepare
    $(call Kernel/Prepare/ts7300)
endef

include $(INCLUDE_DIR)/kernel-build.mk

$(eval $(call BuildKernel))