Mk4 Version 1.0.2 - Alternative Beta

[Sebkinne]

Hello everyone,

I wanted to do this for a while but never got the chance.

Today I spent some time upgrading the firmware to the 3.2 kernel and I made a few other file system changes.

I would love to crowd-source the testing.

If you decide to download the 1.0.2-alternative-beta please be aware of the following:

1. There are no new features otherwise.

2. This may be buggy.

3. It requires you to perform an upgrade. These are never 100% safe, so be aware of that.

Saying that, I have tested the basic functionality and it seems to work - I just haven't been able to test reverse ssh, 3g and a few other things.

By testing this you would help us greatly as it gives us more time to work on new things.

Please report any bugs in this thread.

For anyone that is bold enough, you can download the upgrade.bin here.

Thanks a lot to anyone taking part!

Best,

Seb

[iamk3]

Seb: I'll give it a try. :)

[Sebkinne]

Thanks,

leave any feedback or bugs here.

Best,

Sebkinne

[PineDominator]

ok so I found out that you have to rename the file to upgrade.bin, went good

BUG: Karma log the one that shows associated ssids is not there/visible.

noticed after I set autoStartKarma and rebooted.

also right after the upgrade I ssh'ed in and could not locate my files on the /usb/ re-insertion did not fix, was good after a reboot:-)

thanks again....

Edited March 12, 2012 by petertfm

[iamk3]

petertfm: I think that was probably left out on purpose to keep the wrong people from flashing it. If you do it via the CLI, it doesn't matter what it's called.

Seb: I can also confirm that the Karma log does not show up on the main status page. I also tried cat /tmp/karma.log and nothing showed up. I'm not quite sure if it was supposed to though. I'm just assuming that's where it is supposed to be written to. Karma itself works fine though.

DNS Spoof works fine.

I don't have a way to test out the 3G or the ssh tunneling.

I didn't have the usb problem that petertfm mentioned above, everything seems to be working fine.

The device overall seems to be a little snappier and boot time is fairly quick (although, I didn't really have a problem with it slowing down) It is running a little warmer that it did before, but I don't think it is too warm to be an issue. It's definitely not close to as hot as the Mk3 gets.

[Sebkinne]

The karma log fails because I fail. I will upload a fix in a few minutes.

That it runs hotter is odd, but I have had mine running for over 48h now and it is still cold..

Sorry about the karma log. It isn't just the log but a few karma related things too.

Check the first post for an update.

Best,

Sebkinne

[Sebkinne]

Just to add on to my previous post:

This beta will not have a functioning karma log and associations will probably not show properly.

Generating a detailed report should still work.

The reason for this is because for some reason I cannot get hostapd to pipe the output to a file.

Sounds simple, but when piping the file doesn't get populated (or at least not more than a few lines).

I will be working on a fix but for now I can't fix the issue.

If anyone wants a play, try piping this command to a file:

hostapd -dd /var/run/hostapd-phy0.conf

You will see what I mean.

Best,

Sebkinne

[PineDominator]

Just to add on to my previous post:

This beta will not have a functioning karma log and associations will probably not show properly.

Generating a detailed report should still work.

The reason for this is because for some reason I cannot get hostapd to pipe the output to a file.

Sounds simple, but when piping the file doesn't get populated (or at least not more than a few lines).

I will be working on a fix but for now I can't fix the issue.

If anyone wants a play, try piping this command to a file:

hostapd -dd /var/run/hostapd-phy0.conf

You will see what I mean.

Best,

Sebkinne

here is the output to test.log

Configuration file: /tmp/run/hostapd-phy0.conf
Failed to create interface mon.wlan0: -23 (Too many open files in system)
Try to remove and re-create mon.wlan0
Using interface wlan0 with hwaddr 00:c0:ca:xx:xx:xx and ssid 'MiFi'
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/hostapd-phy0/wlan0' manually if it is not used anymore
Failed to setup control interface
Interface initialization failed
wlan0: Unable to setup interface.

I used "hostapd -dd /var/run/hostapd-phy0.conf > test.log"

are we suppose to see only associations of ssid's here?

Edited March 12, 2012 by petertfm

[Sebkinne]

here is the output to test.log

Configuration file: /tmp/run/hostapd-phy0.conf
Failed to create interface mon.wlan0: -23 (Too many open files in system)
Try to remove and re-create mon.wlan0
Using interface wlan0 with hwaddr 00:c0:ca:xx:xx:xx and ssid 'MiFi'
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/hostapd-phy0/wlan0' manually if it is not used anymore
Failed to setup control interface
Interface initialization failed
wlan0: Unable to setup interface.

I used "hostapd -dd /var/run/hostapd-phy0.conf > test.log"

are we suppose to see only associations of ssid's here?

Petertfm,

Thanks for running that.

Can you do this first:

"killall hostapd" #This will kill wifi. Make sure you are connected over ethernet

"hostapd -dd /var/run/hostapd-phy0.conf >> test.log"

We need to kill it first as otherwise it will not be an ongoing stream.

I have gotten so far as to narrow down the problem:

The output which should be written directly to the file is being buffered.

Once the program ends (ie hostapd) it will write the buffer out to the file.

That is why your file is populated. Hostapd is running --> program will exit after a second or two --> file will have contents.

Any ideas anyone?

[PineDominator]

Petertfm,

Thanks for running that.

Can you do this first:

"killall hostapd" #This will kill wifi. Make sure you are connected over ethernet

"hostapd -dd /var/run/hostapd-phy0.conf >> test.log"

We need to kill it first as otherwise it will not be an ongoing stream.

I have gotten so far as to narrow down the problem:

The output which should be written directly to the file is being buffered.

Once the program ends (ie hostapd) it will write the buffer out to the file.

That is why your file is populated. Hostapd is running --> program will exit after a second or two --> file will have contents.

Any ideas anyone?

OK it seems to look good,

I did what you said:

killall hostapd

touch /var/run/test.log # I know /var/ is a sim link to /tmp/ so I am not writing to flash just ram.

hostapd -dd /var/run/hostapd-phy0.conf > /var/run/test.log # at this point id does not quit it keeps running and I can see my ssid MiFi broadcasted and I am able to connect.

I go into UI and turn on karma. log off MiFi and see my fakenet ssid, I connect and it works:)

test.log

Configuration file: /var/run/hostapd-phy0.conf
Using interface wlan0 with hwaddr 00:c0:ca:xx:xx:xx and ssid 'MiFi'
wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authentication OK (open system)
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-AUTHENTICATE.indication(xx:xx:xx:xx:xx:xx, OPEN_SYSTEM)
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-DELETEKEYS.request(xx:xx:xx:xx:xx:xx)
wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: association OK (aid 1)
wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
wlan0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-ASSOCIATE.indication(xx:xx:xx:xx:xx:xx)
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-DELETEKEYS.request(xx:xx:xx:xx:xx:xx)
wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authentication OK (open system)
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-AUTHENTICATE.indication(xx:xx:xx:xx:xx:xx, OPEN_SYSTEM)
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-DELETEKEYS.request(xx:xx:xx:xx:xx:xx)
wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: association OK (aid 1)
wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
wlan0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-ASSOCIATE.indication(xx:xx:xx:xx:xx:xx)
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-DELETEKEYS.request(xx:xx:xx:xx:xx:xx)
wlan0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-DISASSOCIATE.indication(xx:xx:xx:xx:xx:xx, 8)
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-DELETEKEYS.request(xx:xx:xx:xx:xx:xx)
wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-DEAUTHENTICATE.indication(xx:xx:xx:xx:xx:xx, 2)
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-DELETEKEYS.request(xx:xx:xx:xx:xx:xx)
wlan0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authentication OK (open system)
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-AUTHENTICATE.indication(xx:xx:xx:xx:xx:xx, OPEN_SYSTEM)
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-DELETEKEYS.request(xx:xx:xx:xx:xx:xx)
wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: association OK (aid 1)
wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
wlan0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx
KARMA: Successful association of xx:xx:xx:xx:xx:xx
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-ASSOCIATE.indication(xx:xx:xx:xx:xx:xx)
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-DELETEKEYS.request(xx:xx:xx:xx:xx:xx)
wlan0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-DISASSOCIATE.indication(xx:xx:xx:xx:xx:xx, 8)
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-DELETEKEYS.request(xx:xx:xx:xx:xx:xx)
wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-DEAUTHENTICATE.indication(xx:xx:xx:xx:xx:xx, 2)
wlan0: STA xx:xx:xx:xx:xx:xx MLME: MLME-DELETEKEYS.request(xx:xx:xx:xx:xx:xx)
wlan0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx

I manually ended the logging with CTRL c, the above is the output

[Sebkinne]

Petertfm,

The output is the output of the file, right? Not to console?

If so, did you get the output AFTER Ctrl+c or before? If after, please try before.

Regards,

Seb

[PineDominator]

Petertfm,

The output is the output of the file, right? Not to console?

If so, did you get the output AFTER Ctrl+c or before? If after, please try before.

Regards,

Seb

your right it is wright-en after ending the program:-(

I tried this "stdbuf -o0 command > output" no stdbuf

there must be a way to change the buffering on the /tmp/ folder? it is not flash but somehow acts as if it is.

do you think this is a misconfigured kernel issue?

[Sebkinne]

I thought so.

I noticed that the buffer is being odd, not sure about a misconfigured kernel. It is possible.

I will be taking a look into what may have changed there.

Best,

Seb

[condor]

condor peeking around corner, listening....

[satai]

Ok so i have installed and tested, can confirm that 3g works with a T-Mobile 4G Rocket.

Usb storage is working fine, the issue i am seeing is with installing packages i get md5sum mismatch. Either the opkg or the package index are corrupt. Try 'opkg update'., opkg update doesnt fix the error.

[satai]

The main reason i wanted to run this update was i know the newer kernel works better for iptables and i really want to get sslstrip running on the pineapple, i have managed to get sslstrip running and iptables does now let me redirect port 80, unfortunately the moment i run sslstrip the device reboots.

Wil dig through the logs

[Darren Shady]

Beta firmware allows for loading of RTL8187 drivers, however, device reboots when attempting to put in monitor mode using airmon-ng

after reboot, no longer have a wifi0, internal has moved to wifi1

Also had a weird occurance when I did a wget for the stable firmware and dropped it into /tmp.....device auto flashed and rebooted? I confirming now. Are you listening for upgrade.bin in the beta build?