I tried upgrading from Whiterussian to Kamikazi on my Dell Truemobile 2300. 

When the thing powered up, I was unable to access the router on any ports; I tried both 192.168.1.1 and 192.168.2.1 on all of them.  I could neither ping nor telnet the device.

I suspect that the combination of the different interfaces plus the change away from NVRAM settings is causing this.  Can Kamikazi detect what kind of hardware it lands on and configure the interfaces accordingly?

Thanks!

Well, I tried out a fix from swalker, but that still didn't get it working.

Here are the nvram and ifconfig settings while under Whiterussian.  Any ideas?

root@OpenWrt:/# nvram show
os_ram_addr=80001000
wan_device=vlan1
et0macaddr=00:90:4c:49:00:2c
boot_wait=on
watchdog=1000
wl0_infra=1
et0mdcport=0
pmon_ver=PMON 3.11.48.7
wl0_ifname=eth2
vlan0ports=1 2 3 4 5*
wl0_mode=ap
os_flash_addr=bfc40000
boardtype=bcm94710ap
et1macaddr=00:90:4c:4a:00:2c
lan_netmask=255.255.255.0
wl0_ssid=typicalmacintoshuser
et1mdcport=1
tftp_ipaddr=192.168.2.1
wan_proto=dhcp
lan_ifnames=eth0 eth2
clkfreq=125
lan_ipaddr=192.168.2.1
lan_proto=static
sdram_config=0x0000
vlan1ports=0 5
scratch=a0180000
lan_ifname=br0
sdram_refresh=0x8040
sdram_ncdl=0x00000000
et0phyaddr=30
wan_ifname=eth1
wl0_radio=1
sdram_init=0x0419
dl_ram_addr=a0001000
et1phyaddr=1
boardnum=44
size: 680 bytes (32088 left)

root@OpenWrt:/# ifconfig
br0       Link encap:Ethernet  HWaddr 00:90:4B:35:80:2A
          inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:164 errors:0 dropped:0 overruns:0 frame:0
          TX packets:123 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:7616 (7.4 KiB)  TX bytes:9379 (9.1 KiB)

eth0      Link encap:Ethernet  HWaddr 00:90:4C:49:00:2C
          UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:162 errors:0 dropped:0 overruns:0 frame:0
          TX packets:127 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:10440 (10.1 KiB)  TX bytes:15551 (15.1 KiB)
          Interrupt:3

eth1      Link encap:Ethernet  HWaddr 00:90:4C:4A:00:2C
          UP BROADCAST RUNNING MULTICAST  MTU:1500  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:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:4

eth2      Link encap:Ethernet  HWaddr 00:90:4B:35:80:2A
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:573
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:1052 (1.0 KiB)
          Interrupt:6 Base address:0x2000

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)

So did anyone ever look into this?  I'd be more than happy to try something out if anyone has any suggestions.

Thanks!

Yeah I had problems with Kamikazi also a few months ago. My guess is an initial configuration issue since the 2300 uses different settings than like the WRT. I had to revert back to the White Russian build. I think I had to do the 'short the pins' trick on the flash chip to get the system to respond even... Wasn't a plesant experience. White Russian + backported apps does all I want so I'm happy.

You might try again with 7.09 since a tm2300 vlan change was checked in.

i tried it with the 7.09 but after flashing the Firmware the Router starts nomaly ( Power LED is on)
But i cant connect to the router. I have used 2.6 and 2.4er Kernel with the same result.
Can someone help ??

I have the same exact problems.  Been following the various kamikaze builds and just like goatboy I can't get the device to respond in any way and always have to revert back to whiterussian.  On the hardware wiki page it says that the tm2300 might not listen on any of the lan ports and just wireless instead at first, so I went and disabled wireless security just in case but wireless wasn't started up either.

Btw, I tried both the brcm-47xx kernel 2.6 and also the brcm-2.4 images.

One more thing.  On that  https://dev.openwrt.org/changeset/9015 tm2300 vlan fix, the script is looking for /proc/diag/model    The /proc/diag directory seems to be created via the "diag" kernel module.   Under whiterussian, this module does not install.

#insmod diag
Using /lib/modules/2.4.30/diag.o
insmod: init_module: diag: No such device

dmesg shows

diag: Router model not detected.

Looking at diag.o   

strings diag.o | grep 2300
shows
Dell TrueMobile 2300

so it's in the code somewhere but the code isn't doing the detection right.   

I'll look at the diag code to see what's up.

Sorry, please ignore my previous post.  I was using WhiteRussian rc6.  it's fine in 0.9.

Hello,
so we cant use the Kamaikaze Version ?? Is that right ??
Greetings

Sorry, but I just tried 7.09 and it still doesn't work.  I can reflash and go back to Whiterussian and it works just fine, but when I flash to 7.09 I just don't get any network response from any of the interfaces.  I tried mtd, tftp, and via the Whiterussian web interface.

When it boots up, it looks like the power led comes on at first, and then turns off.  The wireless LED never powers up either.

Who was it that confirmed the TM 2300 working on the twiki on the hardware page?

Bumping this thread up.

Anyone have any insight as to what may be happening here.   Does anyone have the TM2300 working with Kamikaze?

Also, is there perhaps a debug version of kamikaze that we can use to test.  (Perhaps dmesg messages being put in nvram or something) so that we can at least get at them after re-flashing back to white-russian.

Thanks

Take a look at my post http://forum.openwrt.org/viewtopic.php?id=13540 and see if that helps

After flashing the router, you'll need to run

tcpdump   to monitor traffic to/from router, assuming you are connected directly to router
vconfig     to add vlan 0  (you'll get a warning that it might not work w/ certain switches/routers, but you are connected directly to the router)
ping         ping 192.168.1.1 before adding the vlan, see if tcpdump sees any arp from the router on a different vlan (it should be 0, but if it's not, you can vconfig add it)
telnet       to reconfigure your router with the proper Lan interfaces

Wow, Thanks MinXu,

That worked for me.  I was able to get my tm2300 up and going with 7.09 2.4brcm

TM2300 was trying to use vlan1 so I ended up doing the following on my linux box (via eth0) directly connected to the router with nothing else running.  At first, have the router powered off.

ifconfig eth0 192.168.1.10 up
vconfig add eth0 1
ifconfig eth0.1 192.168.1.10 up

I could not get the router to ever come up with 192.168.1.1  so instead I started a dhcp server on my linux box.  With  /etc/dhcpd.conf  having a   subnet defined for 192.168.1.0    range was from 1.1 to 1.5

Then 
dhcpd eth0.1

Started the router.   

It picked up an address of 192.168.1.4

Then I was able to telnet it 

Set the password, and then changed /etc/config/network to..

#### VLAN configuration
#config switch eth0   
#       option vlan0    "0 1 2 3 5*"
#       option vlan1    "4 5"       

#### Loopback configuration
config interface loopback 
        option ifname   "lo"
        option proto    static
        option ipaddr   127.0.0.1
        option netmask  255.0.0.0

#### LAN configuration
config interface lan 
        option type     bridge
#       option ifname   "eth0.0"
        option ifname   "eth0"
        option proto    static
        option ipaddr   192.168.1.1
        option netmask  255.255.255.0

#### WAN configuration
config interface        wan
#       option ifname   "eth0.1"
        option ifname   "eth1"
        option proto    dhcp

And power cycled just to be sure, and now it came back up properly as 192.168.1.1  and I got rid of my vlan on the linux box via

vconfig rem eth0.1
killall dhcpd

And got me a proper address via   
dhclient eth0

Can someone make sure the network settings for TM2300 are set as such.

Thanks

OK, I can set up the vlan and use either dhcp or just ping it to use 192.168.1.1, but either way, I get a connection refused when I try to telnet or ssh into the machine.

It would seem to me that it shouldn't come up with telnet services enabled at first on this interface, right?  I don't see how you guys managed to telnet into it in the first place.

In either case, it might be nice if this were fixed in the image...

If you used the stock image (from the openwrt.org download page, standard broadcom image(, I believe you should be able to telnet to port 23 normally just like any other freshly flashed.  Also, for a freshly flashed image, the only interface the router is performing DHCP on is the WAN side.  So if you did happen to assign it 192.168.1.1, it would be extremely confusing for the router to respond to you.  So:

1.  Use tcpdump (windump doesn't seem to work, possibly the driver is delivering only untagged packets or packets specifically tagged to the vlan you are listening on, etc,.. don't know about wireshark on win32) on linux to listen to response when you ping 192.168.1.1   If it doens't respond, you really only have 4 vlan ports to ping it on:   0 1 2 3, so you can vconfig add eth0 0  , .. 3 etc

2   Once you have that working, telneting is the proper way to configure it.  And telnet will be open/enabled by default to allow someone in to configure it.  It is possible to set it up ssh with a default password (there's one image specifically made for buffalo wpa-g54 that starts with ssh, didn't work for my wla-g54 tho), but telnet is more ubiquitous (if you aren't using vista).

Ahh ok.  I kind of misunderstood the instructions...  I got it working now.  Thanks.

Now if only webif would work...  it's detecting the wrong device...