Jump to content

WUWA

Active Members
  • Posts

    30
  • Joined

  • Last visited

Everything posted by WUWA

  1. The FON is where the IP is coming from, as it's a 192. before I plug it into the FON, and a 10. after. Roger that on the serial port. I'm using that, (thanks to your instructions). It is not usable in its current state, so I'm going to reflash. My choices are to use the 1.0 firmware, or use the instructions at http://www.hak5.org/w/index.php and http://www.hak5.org/w/index.php/Fon_Jasager_Install_v2_1, which honestly seem more stable. If however, you'd like to offer any suggestions, I'd be happy to follow them. My goal is to get a stable platform, but I haven't achieved that yet.
  2. The 10. is definitely coming from the FON. It is the only thing plugged into that port (there is no switch or router or anything between the FON and my laptop), and the laptop has a 192.186 address prior to plugging into the FON and subsequently gets changed to 10.42.43.1 by the FON. I noticed that the wireless interface seems more stable on the 1.0 firmware version on my FON than the wired interface. From the install (using the instructions on your site), and making no modifications, I can see the wireless Jasager SSID, and connect to it wirelessly easily, but I can't ssh into it from the wireless interface (assuming ssh is disabled from the wireless side). I tried to ssh into the wired side, to do a 'ps | grep dnsm' as you suggested, but ssh is problematic. Meaning, I think I was able to initially (since I changed the SSID), but can't seem to ssh from the wired side any longer for some reason (even though I didn't change anything but the SSID). My symptoms at this point on the wired side are, I plug in a laptop, get the 10.42.43.1 IP, change it manually to a 192.168.1.x address, and then try to ping 192.168.1.1 (or 254), which I set the FON to, and it seems to lock up the FON, disabling both the wired and wireless interfaces. (At that point I can't even connect wirelessly any longer). Perhaps it would be useful to walk through my installation method to see if I am doing something wrong: 1) I use the Kyocera cable connected to the JTAG port, powering up and breaking out of the boot up, to access redboot. 2) I then flash the firmware per the instructions on http://www.digininja.org/jasager/installation.php (for Firmware Users) 3) I got the1.0 firmware from http://www.digininja.org/jasager/download.php 4) This is where I noticed that the Jasager firmware is 2., not 2.1, and it seems very less stable than the method I used to install from scratch http://www.hak5.org/w/index.php/Fon_Jasager_Install_v2_1 and http://www.hak5.org/w/index.php/Fon_Jasager_Install. 5) With #4, I have the webif interface accessable, 2.1 Jasager firmware, and it seems more stable. (More, but still with the symptoms that I mentioned when I initially posted). If you would like to offer suggestions on how to proceed, I'd be happy to try them out. At this point I'm considering going back to http://www.hak5.org/w/index.php/Fon_Jasager_Install_v2_1 and http://www.hak5.org/w/index.php/Fon_Jasager_Install to start back over at what, for me, is the most stable version I've seen so far.
  3. I finally found the time to go back and nuke my Fon (for the 40th or so time) and reinstall the 1.0 firmware. My results are the same, meaning I have no webif interface, the Fon locks up constantly (so you can't even ping it), and for some strange reason always gives my laptop an 10.42.43.1 IP address. One of the few times I was able to log into the Jasager interface (on port 1471), the version of Jasager says v2. as in, not 2.1. Perhaps I am doing something wrong. I think I have a UK router, because it booted with a 0.0.0.0 IP when I first got it, and the only way to flash it was/is with a Kyocera serial cable. Perhaps that is a part of the problem, or maybe the problem is that I have a UK router and the memory addresses to flash to are other than 0x80041000? The 1.0 firmware really is not working for me at all. Does anyone have any suggestions for a fix?
  4. Maybe I'm missing something. The only firmware I can find on your site is 1.0. Which, as I mentioned above, is buggy. I can't find firmware for the other versions (1.2 and 2.1), so I had to install them from scratch, and have the bugs that I mentioned. If you would be kind enough to post the firmware for 2.1, I'd be ecstatic to try it.
  5. So after much trial and error (including bricking a couple of routers, several times, and reviving them with the Kyocera cable item number 10002518, per Digininja's instructions), I managed to install Jasager 2.1 on a Fon2100 using the newly posted wiki instructions at http://www.hak5.org/w/index.php/Fon_Jasager_Install_v2_1 and http://www.hak5.org/w/index.php/Fon_Jasager_Install. I used these pages because I tried simply installing the firmware (1.0), and it was too unstable on all (three) of the FON 2100 routers I tested. I also tried 1.2, and had similar buggy results. So when the above URLs were recently posted, I jumped on them to upgrade to Jasager 2.1 in an effort to get a stable version. My results are that there still seems to be issues with the FON. I am using: openwrt-atheros-2.6-root.squashfs openwrt-atheros-2.6-vmlinux.lzm, and the packages in the above URLs, namely: haserl_0.8.0-2_mips.ipk webif_0.3-10_mips.ipk libruby_1.8.6-p36-1_mips.ipk ruby_1.8.6-p36-1_mips.ipk ruby-core_1.8.6-p36-1_mips.ipk ruby-rexml_1.8.6-p36-1_mips.ipk jasager-madwifi_1.ipk kmod-gpio_2.6.21.5-atheros-1_mips.ipk jasager_2.1.ipk and my symptoms are: 1) Windows boxes don't seem to get an IP address when associated to the FON and the computer it is connected to is IP forwarding to the Internet. (Although Linux and Mac boxes do seem to get an IP address, which is strange). 2) When not IP forwarding through a laptop to the Internet, associated clients (targets) seem to only maintain a connection for less than a minute, then drop out. 3) portscan.rb doesn't work in the drop down, and errors out saying that it doesn't look like it was given an IP address. However, often running it from a shell (./portscan.rb foo bar IP) seems to work. 4) Often the FON will lock up, meaning that you can't even ping it. I wouldn't mind troubleshooting, but it is just seems that it is unstable, giving me the feeling that I have some installation incorrect, or some configuration not set accurately. Has anyone else ran into these symptoms, and might be able to offer some advice? If there is a firmware 2.1 version somewhere, or some other method of installing so that the FON is more stable, I'd welcome any suggestions.
×
×
  • Create New...