Jump to content

walts

Active Members
  • Posts

    43
  • Joined

  • Last visited

Everything posted by walts

  1. Point taken - I meant association, not authentication. OK I guess I really need to figure out in more depth what is happening here. Is there any write-up that you can point me to, that discussed the interactions among the different ports on the Jasager? ifconfig shows four, not counting lo: Ath0 and wifi0 share the same mac address - which I assume to be the 802.11 interface br-lan and etho share the same mac address - which I assume to the the wired ethernet port. With the Jasager turned on and the ethernet cable connected to my laptop I get the following log: root@OpenWrt:~# cat ~/status.log Jan 1 00:01:04: DHCPDISCOVER(br-lan) 10.100.3.91 00:09:6b:d0:9a:35 Jan 1 00:01:04: DHCPOFFER(br-lan) 192.168.0.219 00:09:6b:d0:9a:35 Jan 1 00:01:04: DHCPREQUEST(br-lan) 192.168.0.219 00:09:6b:d0:9a:35 Jan 1 00:01:04: DHCPACK(br-lan) 192.168.0.219 00:09:6b:d0:9a:35 exp-t6100 Jan 1 00:10:54: DHCPACK(br-lan) 192.168.0.219 00:09:6b:d0:9a:35 exp-t6100 Jan 1 00:10:58: DHCPACK(br-lan) 192.168.0.219 00:09:6b:d0:9a:35 exp-t6100 Jan 1 00:11:24: Adding the following ssid to the list ["OpenWrt"] Jan 1 00:12:32: Node [00:19:4f:d5:6a:57] associating to ssid ["linksys"] Jan 1 00:12:36: DHCPDISCOVER(br-lan) 00:19:4f:d5:6a:57 Jan 1 00:12:36: DHCPOFFER(br-lan) 192.168.0.216 00:19:4f:d5:6a:57 Jan 1 00:12:36: DHCPDISCOVER(br-lan) 00:19:4f:d5:6a:57 Jan 1 00:12:36: DHCPOFFER(br-lan) 192.168.0.216 00:19:4f:d5:6a:57 Jan 1 00:12:36: DHCPREQUEST(br-lan) 192.168.0.216 00:19:4f:d5:6a:57 Jan 1 00:12:36: DHCPACK(br-lan) 192.168.0.216 00:19:4f:d5:6a:57 Nokia-N800-23-14 Jan 01 00:12:39: Echo script, echoing.... MAC address=00:19:4f:d5:6a:57 SSID=192.168.0.216 Echo done root@OpenWrt:~# ls /karma/etc/rc.dhcp -l lrwxrwxrwx 1 root root 25 Dec 5 2008 S01portscan -> ../../scripts/portscan.rb lrwxrwxrwx 1 root root 21 Dec 5 2008 S02echo -> ../../scripts/echo.rb root@OpenWrt:~# ls /karma/scripts -l -rwxr-xr-x 1 root root 565 Jan 1 00:05 echo.rb -rwxr-xr-x 1 root root 1572 Jan 1 2000 portscan.rb root@OpenWrt:~# 10.100.3.91 was the IP address the ethernet port on my laptop had a few minutes previously, when it was plugged in to my LAN. It looks like a connection was established with my laptop (exp-t6100). Then I opened the web interface and added "OpenWrt" to the list of forbidden SSIDs, turned Karma on, and told my Nokia=N800 to associate with "linksys", which it did, getting the IP address 192.168.0.216. I don't understand why the DHCP transactions used "br-lan" - I thought that was the wired ethernet port! At this point the "echo" script seems to have run, but not the "portscan" script. I waited a full 5 minutes before going on. Here also are directory listings of the two script directories. I'm not looking for a free ride here, just some advice as to how to diagnose and cure this issue, at the level of a Linux amateur but fairly advanced in Windows and Networking. TIA Walt
  2. I'm still having trouble with the portscan script. In /karma/etc/rc.dhcp I have 2 files - S01something (which looks like a shell script) and S01portscan (symlink to ../../scripts/portscan.rb) If I enter ./S01portscan foo bar 192.168.0.216 at the command line it works, but when 192.168.0.216 authenticates to the AP it does not. If I do as you suggested, deleting S01portscan and adding S01echo, then the echo script runs upon authentication. I'm not real good at Linux - is there something with file permissions that could be messing this up? I don't see any error messages at the terminal or in the log, I'm stumped. Walt
  3. I'm back at this after a couple of days. I did as you suggested, and the echo script gave the correct Mac and IP addresses. Now I want to add the postscan script back, but if I enter ln -s ../../scripts/portscan.rb S01portscan the portscan sript does not run. If I try to run it via the symlink immediately after the client associates, I get the "Not enough Parameters" message from portscan. Am I doing something wrong with the way I am setting up the symlink? Also, do ALL of the scripts in the rc.dhcp directory get executed? If so, in what order? Walt
  4. Thanks! I'm learning a lot about how this guy works - it's a really nice implementation. Right now my main hangup is getting a link out to the Internet. Probably after the upcoming long weekend i will have a fresh outlook and can make some more progress. You have been very helpful - thanks :D Walt
  5. I suppose technically this isn't strictly on topic, but it is Jasager related. I have the Jasager (2.1) connected to my MacBook Pro (OS X 10.5) with an Ethernet cable. The Jasager is 192.168.0.250 and the MBP is 192.168.0.1 (manually assigned). I can talk back and forth just fine with the web browser and ssh. I have Internet Sharing turned on on the MBP, as "Share your connection from AirPort", "To computers using Ethernet Adapter" The AirPort is connected to my LAN which in turn is connected to the Internet. It has a DHCP address of 10.100.3.66 If the Ethernet cable is plugged in to the Jasager, then my web browser on the MBP won't find the Internet (via the AirPort). If I unplug the Ethernet cable it works normally. From the Jasager, I can ping 192.168.0.1 but not 10.100.3.66 - "Network unreachable". I can also ping the associated "client" on the WIFI side. From the client, I can ping 192.169.0.1 but no further. It seems to me that the Internet Sharing is not working correctly on the MBP, but from everything I've found on forums, etc. I have it set up correctly. Any ideas from the Mac owners out there? Walt
  6. OK some more information. Running echo with a client associated gave "Jan 01 16:45:22 Echo Script, echoing .... Echo done" I added ip to the error message about the bad ip address, but have not yet triggered the error. I ran the postscan command with ./ portscan.rb foo bar 192.168.0.216 and it ran normally. I see what ARGV[0] does (but I don't know why) I can't find where ARGV[1] is used I don't understand what triggers the portscan script in the first place - does it run automatically when a client associates? Thanks for all the help! Walt
  7. I assume then that I would plug the Fon Ethernet wire directly into the network, not into the PC? In any event, aren't you doing the same thing as the GUI would do setting up for DHCP and no specified IP address? Not that I have anything against vi - we're old friends from using the Nokia and Zaurus! I've kind of shut down for the night now, will try more things in the morning. Thanks :-) Walt
  8. OK I've done as you suggested. Here's a recent log - I don't see anything "wrong" with the IP addresses. root@OpenWrt:~# cat status.log Jan 1 00:01:37: Adding the following ssid to the list ["OpenWrt"] Jan 1 00:02:04: Node [00:19:4f:d5:6a:57] associating to ssid ["linksys"] Jan 1 00:02:08: DHCPDISCOVER(br-lan) 00:19:4f:d5:6a:57 Jan 1 00:02:08: DHCPOFFER(br-lan) 192.168.0.216 00:19:4f:d5:6a:57 Jan 1 00:02:08: DHCPDISCOVER(br-lan) 00:19:4f:d5:6a:57 Jan 1 00:02:08: DHCPOFFER(br-lan) 192.168.0.216 00:19:4f:d5:6a:57 Jan 1 00:02:08: DHCPREQUEST(br-lan) 192.168.0.216 00:19:4f:d5:6a:57 Jan 1 00:02:08: DHCPACK(br-lan) 192.168.0.216 00:19:4f:d5:6a:57 Nokia-N800-23-14 Jan 1 00:15:24: DHCPREQUEST(br-lan) 192.168.1.247 00:16:cb:a0:29:96 Jan 1 00:15:26: DHCPREQUEST(br-lan) 192.168.1.247 00:16:cb:a0:29:96 Jan 1 00:15:29: DHCPREQUEST(br-lan) 192.168.1.247 00:16:cb:a0:29:96 Jan 1 00:15:32: DHCPDISCOVER(br-lan) 00:16:cb:a0:29:96 Jan 1 00:15:32: DHCPOFFER(br-lan) 192.168.0.247 00:16:cb:a0:29:96 Jan 1 00:15:32: DHCPDISCOVER(br-lan) 00:16:cb:a0:29:96 Jan 1 00:15:32: DHCPOFFER(br-lan) 192.168.0.247 00:16:cb:a0:29:96 Jan 1 00:15:33: DHCPREQUEST(br-lan) 192.168.0.247 00:16:cb:a0:29:96 Jan 1 00:15:33: DHCPACK(br-lan) 192.168.0.247 00:16:cb:a0:29:96 Jan 1 00:20:17: DHCPREQUEST(br-lan) 192.168.0.247 00:16:cb:a0:29:96 Jan 1 00:20:17: DHCPACK(br-lan) 192.168.0.247 00:16:cb:a0:29:96 Jan 1 00:26:32: Node [00:0e:7f:b6:81:e3] associating to ssid ["City of Boca - Guest"] Jan 1 00:26:33: DHCPREQUEST(br-lan) 192.168.1.48 00:0e:7f:b6:81:e3 Jan 1 00:26:34: DHCPREQUEST(br-lan) 192.168.1.48 00:0e:7f:b6:81:e3 Jan 1 00:26:37: DHCPDISCOVER(br-lan) 00:0e:7f:b6:81:e3 Jan 1 00:26:37: DHCPOFFER(br-lan) 192.168.0.197 00:0e:7f:b6:81:e3 Jan 1 00:26:37: DHCPDISCOVER(br-lan) 00:0e:7f:b6:81:e3 Jan 1 00:26:37: DHCPOFFER(br-lan) 192.168.0.197 00:0e:7f:b6:81:e3 Jan 1 00:26:37: DHCPDISCOVER(br-lan) 00:0e:7f:b6:81:e3 Jan 1 00:26:37: DHCPOFFER(br-lan) 192.168.0.197 00:0e:7f:b6:81:e3 Jan 1 00:29:04: ssid ["OpenWrt"] found in blacklist so rejecting Jan 1 00:29:04: ssid ["OpenWrt"] found in blacklist so rejecting Jan 1 00:29:04: ssid ["OpenWrt"] found in blacklist so rejecting Jan 1 00:29:06: ssid ["OpenWrt"] found in blacklist so rejecting Jan 1 00:42:06: DHCPREQUEST(br-lan) 192.168.0.247 00:16:cb:a0:29:96 Jan 1 00:42:06: DHCPACK(br-lan) 192.168.0.247 00:16:cb:a0:29:96 root@OpenWrt:~# Walt
  9. I'm making progress, but still a bit confused. I have the Ethernet port on my PC set to a fixed IP address of 192.168.10.10 and Der Jasager to 192.168.10.250, and they connect fine. It turns out that you need to switch to DHCP to get the IP address box to shoe, then back to Fixed. I have the WIFI connection on my PC set to Internet Sharing, and it is connected to my office AP. however, unlike the Microsoft documentation, it has a "real" IP address 10.100.3.86 - that was assigned by the DHCP server on the network. the Microsoft documentations says that the adapter doing the sharing will be set to 192.168.0.1. Doesn't Der Jasager do DHCP for the wireless connections to its "victim"? When I connect to him by looking for an AP named "linksys" I get assigned an IP address of 192.168.10.216 so why do I need to have a DHCPD running on the PC? I've read the other thread on this subject and am becoming more confused by the minute :-( Sorry to be so stupid about this. Walt Edit: 2 hours later. I now have Der Jasager and the PC talking as 102.168.0.1 (PC) and 192.168.0.250 (Fon) - both fixed IP addresses, and a Verizon wireless modem set up as the shared connection. I changed the IP of the Ethernet to correspond with Microsoft's convention. Once again, I can connect to Der Jasager over WIFI and get assigned 192.168.0.216 but the connection sharing does not seem to be working. So I fired up Wireshark to see if I could learn anything. I can ping 192.168.0.1 (the Ethernet port on the PC)from the client, but no further. If I try to ping back (from the PC) I generate a bunch of ARP requests: Who has 192.168.0.216? Tell 192.168.0.1 I'll probably quit here for today. I'm grateful for any ideas, and I'll check back in the morning Walt
  10. I agree. My recollection from setting up DD-WRT on my Linksys AP - a long time ago - was just that. For some reason, this X-Wrt GUI only opens up the IP Address box when you choose "DHCP" from the combo box (see the wiki, http://wiki.hak5.org/wiki/Internet_Connect...mit_Der_Jasager about 1/2 way down) The text next to the IP address box states that this address is used as the default if a DHCP server is not available - which is the case in my setup. Just to be sure i have the right idea, Der Jasager is plugged in by the Ethernet cable to the Ethernet port on my laptop. This is 192.168.0.250 in the example. The other interface on the laptop, a wireless interface is authenticated to my AP and then connected to the Internet. This interface is set up for ICS. When "Victim" comes along looking for "MY-AP", Der Jasager says "OK, that's me!". Now "Victim" is connected to the Internet through my laptop as a MITM. Do I have it right? Walt
  11. I'm starting with a working Fon, with Jasager 2.1 installed, and following the wiki at http://wiki.hak5.org/wiki/Internet_Connect...mit_Der_Jasager. After changing the IP address of the Fon lan connection to 192.168.0.250, DHCP, bridged, and with the Ethernet port on the PC set to 192.168.0.1, I cannot connect. I've tried setting the PC port to DHCP to no avail. I've waited up to 10 minutes after a cold boot of the Fon to give it plenty of time to start up. The settings seem reasonable - as I read the screen the Fon will try to get an IP address from the Ethernet connection, and if it can't will default to the one we've provided - 192.168.0.250. After that it should be able to connect directly with a PC with an address in the 192.168.0.0/24 subnet. Correct? Since at this point I cannot communicate with the Fon at all, I have gone back to re-flashing the ROM (twice). Can anyone help me with this connection problem? TIA Walt
  12. Neither - the Fon is just sitting on the desk, with the Ethernet cable connected to the pc running a web browser monitoring the status display. I think I need more instruction on setup and use. Is there a wiki somewhere that I'm missing? All I have found so far is the installation wiki and the Hak5 episode that discussed Jasager in the first place. Walt
  13. OK now I have 2.1 running..... Maybe my first impression was wrong - I thought the Fon was now set up as a MITM for unsecured networks; that it would answer "Here I am" to any broadcasts seeking an unsecured AP and insert itself between the client and the AP. I don't seem to be seeing that on the "Connected Clients" display. Maybe my question is answered in the log... I'm seeing a lot of DHCP entries in the log, but the last line in the log display is always "The IP address doesn't look like an IP address, aborting" (sic) Is this a misconfiguration of some sort? Where should I be looking for answers? TIA Walt
  14. Re-flashing took about 20 minutes (on a 2100), and the rest of the sequence went according to plan. See http://hak5.org/forums/index.php?showtopic...mp;#entry110139 The only hitch was at the very end - Jasager said it was shutting down the previous version - there was none - and then hung at "Starting Jasager". Power off reboot fixed that and it is running fine now! Walt
  15. You beat me to it! I just finished the same thing, for the same reason, and was thinking about the wiki. I followed a slightly different order in your step #14: root@OpenWrt:/# cd /tmp root@OpenWrt:~# ipkg install haserl_0.8.0-2_mips.ipk root@OpenWrt:~# ipkg install webif_0.3-10_mips.ipk root@OpenWrt:~# ipkg install kmod-gpio_2.6.21.5-atheros-1_mips.ipk root@OpenWrt:~# ipkg install libruby_1.8.6-p36-1_mips.ipk root@OpenWrt:~# ipkg install ruby_1.8.6-p36-1_mips.ipk root@OpenWrt:~# ipkg install ruby-core_1.8.6-p36-1_mips.ipk root@OpenWrt:~# ipkg install ruby-rexml_1.8.6-p36-1_mips.ipk root@OpenWrt:~# ipkg install jasager-madwifi_1.ipk root@OpenWrt:~# ipkg install jasager_2.1.ipk Installing jasager (2) to root... Configuring jasager Install finished, testing that it worked ok SUCCESS! Jasager installation appears OK. Welcome to Jasager! Also, after installing jasager, it tried to shut down the previous installation (there was none) and then hung on "Starting Jasager". A power-off reboot fixed that, and all is running well now. Walt
  16. Thanks! I'm back at the re-flashing step (#11), and twice now it has gotten to the point of recognizing the MAC and IP addresses of both devices and stalling; it never gives the messages about flashing the images! (never=>30 minutes.) Is there some form of "master reset" to just get back to a bootloader or something (I'm relating here to flashing ROMS on a Sharp Zaurus, a similar procedure. There you can force the device into "Maintenance mode" after which almost everything begins working again). Once I get back to the point of flashing a clean OS I will try both approaches - running the ipk or un-taring the tarball. Thanks for the help! Walt EDIT - 2 hours later - back from a meeting, and I am currently flashing back tot he original FON firmware. that seems to be working OK, and I will begin again at step 1 of the process. W.
  17. I'm not real sure what I'm doing wrong! I had 1.2 running fine, and I saw that 2.0 was out. I installed: ruby-core ruby-rexml kmod-gpio and then when I tried installing jasager_2.1.ipk i got ipkg: fork failed: Cannot allocate memory After several futile attempts I re-flashed the fon and now have 1.2 running. Any advice would be welcome! Walt
×
×
  • Create New...