-=Dante=-

So, I have made a little progress toward getting this to work. I added an alias to br-lan by adding the following to /etc/config/network config interface wan3 option ifname br-lan option proto dhcp and added some firewall options based on the other interfaces that the Mk5 can receive an internet connection from (wlan1, usb0) /etc/config/firewall config zone option name wan3 option network 'wan3' option input ACCEPT option output ACCEPT option forward ACCEPT option masq 1 option mtu_fix 1 config forwarding option src lan option dest wan3 config forwarding option src wan3 option dest lan What this leaves me with is: 1. When I boot the Mk5 without the Ethernet cable plugged into a router, I can connect via WiFi on wlan0 and get a 172.16.42.* address. 2. Plugging into a router and issuing "ifup wan3" adds a second IP acquired from the router to br-lan. This can be seen by issuing "ip addr" (if you have ip installed) 3. The original device that connected via WiFi can now access the pineapple directly at 172.16.42.1, and connect to the internet, and the Mk5 can be reached over the router's lan. 4. Any subsequent devices that connect revert back to the original behavior of being bridged through the Mk5 and talking directly to the router for dhcp assignment. My current line of thought is setting up a custom route for the 172.16.42.0 block of addresses. Any input toward getting this working is appreciated.

Curiosity, stubbornness, a better understanding of the Mk5's internal workings, and maybe a pratical application. In that order.

I'm seeing the same behavior as LeeVai. When booting the Mk5 pluged directly into a router. Clients on wifi are bridged through the Mk5 and receive IP's form the router. I am not very familiar with OpenWRT but I think in order to get this working you would have to edit /etc/config/network The default for eth0 or lan is: config interface lan option ifname eth0 option type bridge option proto static option ipaddr 172.16.42.1 option netmask 255.255.255.0 option gateway 172.16.42.42 option dns 8.8.8.8 You might find these pages helpful. http://wiki.openwrt.org/doc/uci/network http://wiki.openwrt.org/doc/howto/internet.connection DISCLAMER! I do not know enough about this to be sure what this will do to br-lan. I am fairly sure that it will not exist anymore and that your only way into the Mk5 will be through WiFi. It might also break everything! I would highly recommend waiting until someone who knows more about this than I do, says something. [Edit] Turns out this does break lots of stuff. DON'T DO THIS. [Edit2] Specifically this breaks the Mk5's ability to hand out IP's over dhcp and you will not be able to connect via wireless. I was however able to ssh in over eth0 and confirm that the pineapple had properly gotten an IP from the router.

If you open the karma tile one of the tabs will have an option to enter a new ssid and a check box to make it permanent.

When you have the Mk5 and your laptop connected to your router what is the IP and subnetmask of the laptop? Is the laptop connected to your router over ethernet or wifi? Windows or Linux laptop? My first guess is that your laptop is still bound to the static IP that you would need to give it to connect directly to the pineapple. In your partial solution are you connecting the laptop's ethernet port directly to the pineapple?

I had a setup very similar to this with a Mk4 and a Kali pineapple. I was never able to get dnsspoof to properly redirect to the pineapple though. I hope you have better luck. Keep us posted!

I think the file you are going to want to change will be /etc/config/wireless. Something like this. cp -f /sd/wifi-profile-1 /etc/config/wireless You may have to bring the interface down and back up for it to associate. Make sure to keep the beginning of that file intact though or it will break wlan0.

How are you providing the pineapple with an internet connection? Are you sure that your internet connection has been established when the dip script runs?

You can do this on the fly from the client side as well with a local port forward. When ssh'ing in append "-L 1471:localhost:1471" to the end of your ssh command. ssh root@host -L 1471:localhost:1471 Then point your browser to localhost:1471 I do this through a relay server. Gives me a shell and the web UI.

I just received mine today! It is well worth the wait. Build quality is even better then I expected, and the setup took about 15 minuets from the time I had it out of the box. Outstanding job by the Hak5 team on this one. You guys have created something truly awesome.