digininja

Put it in black list mode, then it will take everyone apart from ones in the list.

Just tried to look at this, where did you get proc_gpio from? Can't find it in the openwrt packages or in any of the svn repos.

Sounds like the .htaccess maybe ended up in the wrong place. I'll have a look.

Both Jasager and webif are password protected. The username is root and the password is whatever your root password is.

If you could build the antenna into his scythe then that would have been cool!

No problem. If you are using it at work and your company would like to make a donation, please feel free to get in touch. I'm happy to offer corporate support deals.

It looks like it is working perfectly to me. Jasager doesn't have an SSID so the fact you connected to OpenWrt means that you connected to an AP that doesn't really exist. Also, once you are connected then you stop sending probe requests so the others won't show up. Try removing the OpenWrt AP from the list and put an alternative unsecured, auto-connect SSID in and it should connect to that.

If it is like at the airport they'll think its a grenade and blow it up. Bitstream won't have anything to photograph!

next option, ssh in, set an ssid by doing iwconfig ath0 essid Fred That should then start beaconing. See if you can see/connect to that. This will tell you if it is Jasager/Karma that is at fault or something else.

No Atheros, No Karma.

You can probably do this quickly with webif. Just go through the interface and see what you can set. I've just got my new hdd installed so that is one job out of the way, this is moving up the list!

I saw a nice robotic Grim Reaper in a shop the other day, unfortunately I didn't have time to play with it to see if it could be modified.

My mate Bob has done it loads of times. He suggested setting the default webpage served to autoplay a nice loud wav file so you know who has connected. There was also mention of lemon party (go google...) but I think he is too nice to to do that.

Read these forums and watch the show, there are loads of ideas and suggestions. I think it is good that you've gone to the trouble of installing my app without even knowing what it is, thanks.

Ifr you have karma turned on then it should reply to any AP you request so you should get WORKAP to connect to. If you aren't then there is a problem somewhere. Check dmesg to make sure you have fully patched drivers (look for digininja) and check karma is on in the interface (off by default).

OK, I've just got a new Fon flashed so it is completely clean. I'll go through and set it up and then let you know the process of getting it completely online. Got to fit a new hdd to my desktop tonight so give me a day or so and I'll get what I can up.

Got you. Just ssh in through the wifi interface and do an ifconfig eth0 to find the ip address of it. If it is getting it through your dhcp server then it should be on your subnet. If not you have two options, either change its ip with ifconfig eth0 x.x.x.x or give your laptop a second interface on the right subnet by creating eth0:1. The first option is the easiest, the second one would probably require special routing on the gateway.

Simple answer, Yes. Harder answer, how to do it! Bridging is controlled by btcrl. A really good place to look for info on this is in the instructions for setting up VirtualBox, an opensource VMware replacement (or at least it used to be). You basically take down the IP on eth0 by setting it to 0.0.0.0 (there may be better ways but I know this works) then you create a bridge with brctl and add eth0 and your wifi to it. You can then treat the bridge (usually br0) as if it were a single network interface, e.g. bring up dhcp on it etc. If you do this, make sure you kill any dhcp clients that are working on eth0, they will interfere and try to get eth0 an IP when it shouldn't have one.

What do you mean connected devices? On Jasager? If so, then it won't, they are only connected clients. I think I'm missing a key thing about what you are asking, give me a bit more info and I'll help

Added to the todo list. I've just got to get round to doing them! I'm home alone for most of this week so assuming I can get my new fon's flashed I'll get some stuff done and get a new release out.

This is completely optional, you chose where to route the traffic. They way I have it set up is that the fon sits on my network through the wired port. It has a default gateway of my internet gateway so that all traffic is routed out onto the internet or onto the internal network as appropriate. The hard bit for most people is getting the default route back to the fon setup. Quick example... Jasager gives out IP's on the 10.1.1.0/255 subnet Your internal network is on 192.168.0.0/255 A Jasager client sends a packet to the internet on the wireless, the fon knows the two subnets and knows to route it to the gateway. The gateway checks the destination IP and sends it out to the internet. All is good so far. The packet comes back in and the gateway checks the IP, it is for 10.1.1.1. The gateway checks to see if it knows about that subnet, it doesn't so it throws it back out to the internet. The packet gets lost in the cloud. The way to solve this is to tell the router that it needs to use the fon to route all the traffic for the 10.1.1.0 subnet. I have an openwrt device as my router so I simply ran: route add -net 10.1.1.0 netmask 255.255.255.0 gw 192.168.0.111 (Where 192.168.0.111 is the IP of my fon) on my router. This then tells the router how to route traffic for the 10 subnet. Depending on your IP tables rules, you may have to adjust them to allow the extra traffic. This depends on how you have things setup. If you are running an off the shelf router then check it and see if it will allow you to set routes, if not then you may be out of luck with this solution. I'm sure there is probably a way to do it by routing through another machine and re-writing headers or proxy'ing or something but I'll leave that for someone else to explain. <note>All IP's and subnets are made up, substitute your own in where appropriate</note>

No idea, but if it works, who cares? Especially if you stick it inside a pineapple!

Josh Wright is a friend of mine so I'll give it a try and maybe see if I can get some help if I get chance. A while ago I started re-writing airpwn in ruby but the scruby library didn't support what I needed so I gave up. Scapy should do what I need so I may have a look at doing it in python at some point.

A couple of options, you could look at what the fon bomb actually uses and see if you could just copy the stuff across to Jasager or, if we can get lorcon working on the fon then I've got a deauth script written in ruby that works really well. I like the idea of lorcon on the fon, I'll add it to the todo list. If you look at the bomb and find anything please report back.

If you want something similar which runs on a normal laptop look at Karma. It is the same madwifi patches and a ruby framework around it. Not as pretty or interactive but does the job. It is included on the BT3 cd but doesn't work, if you want to try it, have a look my thread on the PaulDotCom forums about getting it working in BT.