loftrat

Post #1 ;)

Tried the ISO and found that it's still running Slax.....thought BT4 was moving to a Ubuntu/Debian base?

I've not done any manual setup of the networks, with UCI or otherwise. What firnware did you flash it with that fixed it? All I know is that when I turn the Fon on those APs all appear in the wireless networks list on my laptop. It's possible that there's a device asking for them somewhere locally, but I'd doubt it very much. Even if there were it doesn't explain the strange character set that the SSIDs appear to be listed in.

Right, I'm on the cusp of getting this sorted. I think everything's working ok, the little thing seems to be picking up the requests from my laptop and adding SSIDs to suit, then the laptop connects and gets an IP address. I can run the port scanner and it gets the results I'm expecting so things would appear to be going well. I've got a couple of little things to work through: 1. I'm getting some really weird SSIDs appearing in the wireless networks list within Windows when the Fon is up and running. Here's a picture that shows what I mean. 2. When the Fon boots it doesn't seem to be bringing up the wireless device/karma properly - I think I've found instructions on how to do that though so I'll give them a go and see how I get on. Once everything's squared away and working properly I'll write up full instructions on everything I've done to get this model working. I think some of the problems I've had have been caused by the fact that this newer model seems to be quite light on memory, I'm wondering if the Fon guys are starting to cut corners and go for cheaper hardware?

I think you'll find it easier to command the 75k starting salary (I'm assuming that's dollars yes?) if you remember to include links/files when you say you're going to post them ;)

Ok, steps to resolve the issue above: cd /usr/lib/ipkg/ mv status status_out ipkg install -nodeps /tmp/jasager_2.1.ipk

There seem to be copies of /etc /bin and others, do I just copy those over the top of the existing ones and then reboot?

And I was making so much progress..... Ok, everything seemed to be going ok - I've managed to get the serial connection working fine, got the firmware flashed, and I can now SSH into the Fon. I can also see the Webif control panel on 192.168.1.1. However..... When I try to do this: ipkg install jasager_2.1.ipk I get the following error: ipkg: fork failed: Cannot allocate memory Anybody got any thoughts/ideas on how to solve this? Just had a look at the tarball and can't see how to build it, ./configure doesn't seem to work so I'm guessing I'm misssing a step somewhere?

Ok, I get that. From what I can see though the tutorials all specify access over ssh via an ethernet connection to be able to get the firmware flashed, I obviously can't do that and I can't find any instructions for what I need to do to be able to flash it over serial. I can Control+C to get the boot sequence to stop, but I don't know where to go from there. Is it possible to reconfigure the device from serial so that I can go down the normal flashing root, or is it possible to do it all from my newly working serial connection? Having gotten to this point I'd really rather avoid bricking it if I can ;)

Thanks guys, I'm sure you're both spot on (you normally are) - either of you got any ideas where I go from here though? Thanks.

Ok, we're making progress. Finally managed to get a USB > Serial cable working and connecting to the Fon. When I connect using HyperTerminal I get the following: +Ethernet eth0: MAC address 00:18:84:40:01:ec IP: 0.0.0.0/255.255.255.0, Gateway: 0.0.0.0 Default server: 0.0.0.0 RedBoot(tm) bootstrap and debug environment [ROMRAM] OpenWrt certified release, version 1.1 - built 22:32:28, May 7 2007 Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc. Board: FON 2201 RAM: 0x80000000-0x81000000, [0x80040290-0x80fe1000] available FLASH: 0xa8000000 - 0xa87f0000, 128 blocks of 0x00010000 bytes each. == Executing boot script in 2.000 seconds - enter ^C to abort RedBoot> fis load -b 0x80100000 loader RedBoot> go 0x80100000 Failsafe loader v0.2 Looking for board config data... found at offset 0xa87f0000 Reset button GPIO: 6 Reading flash from 0xa8040000 to 0xa8278f5c... Uncompressing Linux... Ok, bootin g the kernel. [sighandler]: No more events to be processed, quitting. [cleanup]: Waiting for children. [cleanup]: All children terminated. Unlocking rootfs ... Could not open mtd device: rootfs switching to jffs2 init started: BusyBox v1.4.1 (2008-04-03 09:16:35 UTC) multi-call binary : ifconfig: SIOCSIFADDR: No such device : ifconfig: SIOCSIFADDR: No such device : Interface doesn't accept private ioctl... : ff (8BE0): Invalid argument : udhcpc (v1.4.1) started : Interface doesn't accept private ioctl... : ff (8BE0): Invalid argument : Sending discover... : route: fscanf : Sending discover... : Sending discover... : Sending discover... And so on, and so on...... This is the only type of access I've been able to gain to the Fon (as per my posts above) I can't get the GUI to work for flashing because I'm still getting the same errors. I'd be grateful if someone could give me a pointer as to the next step. Thanks :)

Perhaps the crew might like to do a Seg on it? :D

I'm using TrueCrypt for this very purpose at the moment. Works very well.

LOL Quoted for truth :)

Well, I understood these to be two completely different distributions, with two completely different aims. DVL aims to be, well, 'damn vulnerable'. The idea is that it should be used as a training distribution, with vulnerabilities built in that you can play with and learn from. BackTrack is a distribution that is built for people to USE and is not aimed at learners as such. As to which is 'best', well that kind of depends on what you're planning on doing with it.....

I think it's probably more like: Laptop: Hello, is my home network there? HomeNet: Yep, here I am - if you want to connect you'll have to tell me the password/phrase. Laptop: Ok, I'd like to connect - here it is. If you turn of encryption on your home wireless network your laptop will still connect to it, it simply goes with the flow and assumes that you are no longer using encryption. I would guess that Jasager makes use of this behaviour.

Nice one :) That's where I went wrong, it wasn't until I found about my 4th/5th guide to making these types of cables that I realised why nothing seemed to be working ;) I've now ordered one of the Nokia CA-42 cables which are also supposed to work, hopefully I'll have more luck with that :D

Who me? B) :D In my own defence, I know bugger all about hardware (I mean, seriously, I just don't do hardware at all) so it's only by the good grace of the TechnoGods that I didn't just try to wire the thing directly to my printer or something :D Now there's an idea.....

Yep, me, my soldering iron, and a couple of hours swearing, figured that out earlier :D

Never mind, I think I figured it out :( Back to the drawing board (and possibly to the shop for a new Fon :( ).

Me Again :D Ok, I've got a serial cable made up - USB to some header connectors which are currently plugged into th Ground, RX, and TX, pins on the Fon + mainboard. Putty (in Windows) doesn't seem to want to play. This seems to be because Windows doesn't want anything to do with the Fon when I plug it it - it just complains that the USB device has failed/errored and keeps doing that over and over and over. Linux doesn't seem to recognise it either -it proudly tells me (via dmesg) that it's found a new device (using uhci-hcd and address 97), then tells me that it's 'failed to enumerate USB device on port 1'. If I run dmesg again I get the same message, only it's now 98, then 99, then 100, etc. I've checked and double checked the pin connections on the cable, and they're fine. I've tried the RX cable on the TX pin and vice versa. Anybody got any thoughts on where I can go from here? Thanks :)

I notice from digininja's descriptions of cable making, and from the pictures that he's labelled of the Fon's mainboard, that there's a spare pin there (thanks for the pics and tutorials by the way digininja :)). Does anybody know if that's the +5v pin that doesn't seem to otherwise be used from the USB cable? If so, would it be possible to connect the USB +5v to this and at least power the board? Thanks :)

Hmmm, dissapointing - fair enough though, thanks guys. Guess I'd better go buy myself a soldering iron this weekend :D

Thanks for that, I'm in now. Once I've made a cable up what does that get me? I take it I make the connection from USB to Fonera.....but then what? I'm guessing this gives me terminal access (bypassing Telnet/SSH probably?) can I just ftp the images in from there and install manually somehow? Thanks :)

Ok, I'm fairly sure there's something bizarre going on. The Fonera+ that I have has an IP address on the LAN side (black port) of 192.168.10.1 Visiting that page redirects me to: htto://192.168.10.1/cgi-bin/status.sh This page tells me that I have a 'Firmware Version' of 3.0.2 r1. I can't access the 'Advanced' page as the default usernames and passwords that I can find on the web for this model don't seem to work. Request 1: If anybody has any ideas on default usernames/passwords please let me know - thanks. 'nmap -vv -sT 192.168.10.1' gives me three open ports (53, 80, 8080). I've tried the various methods for getting into it that I can find here, and nothing seems to be working - I haven't managed to try the redboot.pl script yet because I can't seem to find instructions for it. Request 2: Please could someone link me to the instuctions for the redboot.pl script (and a copy of the script if possible) I'm obviously having a dumb night. I think I'm going to have to try building a cable and going down that route if the .pl script doesn't work. I'm assuming there's a tutorial out there somewhere for actually using the cable? Thanks for all the help.