What would be your effective solution for this? Only looking in a specific dir, or globally? Where does the board save it's content? Maybe it is enough if we take the last modified date of the files the board touches, as - AFAIK - that is the only part that really *needs* the date to be increasing.by stylesuxx - Raspberry Pi(rate)Box
This topic is meant for brainstorming ideas for the next release. It is open for everyone, so if you want to see a specific feature in 1.0.8 for the RPi release, post it here. This discussion will be open until a certain point. At that point all features are freezed and will be the TODO list for the next release. I will add Features and Ideas to the list from your suggestions as I see fit: Feaby stylesuxx - Raspberry Pi(rate)Box
Just pushed the fallback for WiFi, there now is a wpa_supplicant.conf on the boot partition, if no AP enabled WIFi stick is found, the PirateBox tries to connect to the network set in wpa_supplicant.conf instead. I am right now building the image and give it a final test. If everything works for me I will also build an RPi2 image. And upload both for testing.by stylesuxx - Raspberry Pi(rate)Box
Hey TheExpertNoob, Connecting wo Wifi via wpa_supplicant.conf on the boot disk is my last biger Todo, before I consider it a RC ;-) Should be done today, maybe tomorrow. Greetz, Chrisby stylesuxx - Raspberry Pi(rate)Box
No not your fault. I just pushed the new changes. You can now build an image with the piratebox webserver scripts from a branch of your choosing. To use the current release candidate branch run the build like so: make BRANCH="release-1.0.7" Which will pull the git repo, checkout the branch, build the piratebox package, and use this package and all the scripts from the checked outby stylesuxx - Raspberry Pi(rate)Box
Thanks. Yes, I am currently working on a feature to pass the dev dependencies to the Makefile - Should be done today, can't promise this though. Also I will upload images as soon as I am done with the above. Can you briefly explain why wgetting the file is necessary?by stylesuxx - Raspberry Pi(rate)Box
You should be able to access Failsafe Mode and reflash your PirateBox from USBby stylesuxx - PirateBox (General)
Adjusted the timesave script so it can handle date time strings with spaces, as needed for arch. This *should* not break any other functionality.by stylesuxx - Raspberry Pi(rate)Box
Exactly. Thank you for adding me :-)by stylesuxx - PirateBox (Development)
OK, found where you are setting the format, only problem seems to be, that setting the date with the openwrt format does not work with arch: # Does not work date -s"201705261113" date: invalid date '201705261113' # Works, but not comparable date -s"2017-05-26 11:13" Fri May 26 11:13:00 UTC 2017 # Works, but not comparable date -s"20170526 1113&quby stylesuxx - Raspberry Pi(rate)Box
Merging it into the feed makes sense. So I would make a branch in the feed repo for transition, and start merging the first repositories into it, moving the open issues, if any. After I am done with merging I will mark them here first, but leave them @github as they are. Once we are done with transition, we deprecate them all at once, so until then we have everything working as it is. Alsoby stylesuxx - PirateBox (Development)
I think the *cus and *eu sticks do not need the driver in there to work properly, I am trying with my different sticks to verify. Timesave said when failing: Nov 27 18:07:31 alarmpi timesave.sh[147]: Sorry, changing timebackward via timesave is not possible Did you set a date in the past? I need to edit the MOTD, since "The enable piratebox on startup" is not applicable anby stylesuxx - Raspberry Pi(rate)Box
Great to hear. I tell you, those things are nearly unbrickable :-Dby stylesuxx - PirateBox OpenWrt
Adding the nofail option, fixed the qemu boot problem - thank you. I also added a helper script to recognize the WiFi sticks we have support for, install the appropriate hostapd package and adapt the configuration. This is triggered by a udev rule that triggers when a wlan0 gets available, if everything went well it will start the PirateBox service. I added it to the build process but diby stylesuxx - Raspberry Pi(rate)Box
bs=2048 count=1048576 2048 * 1048576 = 2147483648 Byte -> 2097152 KB -> 2048 MB -> 2GB You are of course right, it still is bigger than it needs to be, but if it is zipped it is ~ 500MB or so. We could of course shrink the partition to it's needed size + some spare. edit: I misread your post. Yes 2GB is the right size.by stylesuxx - Raspberry Pi(rate)Box
Started another branch =>by stylesuxx - Raspberry Pi(rate)Box
TheExpertNoob Wrote: ------------------------------------------------------- > I don't know if putting it on the boot partition > would be easier for the end user to edit it, mount > /dev/boot to /boot on startup, and have > WPA_supplicant pull config from > /boot/WPA_supplicant.conf (fat 32 partition easliy > readable on all systems to edit the file before > firby stylesuxx - Raspberry Pi(rate)Box
Alright thank you for the feedback TheExpertNoob. I added wpa_supplicant to the dependencies and it is now installed when the image is built. I was wondering if we should add a /etc/wpa_supplicant.conf with a default network name and password, so peopble would only need to change the ESSID of their local WiFi and would be able to connect to the piratebox initially. (on the other hand, peopleby stylesuxx - Raspberry Pi(rate)Box
This is just a checklist for future tests. Since I was updating build scripts and Stuff. Before we do ne next release we will do a testing round, so if you could join us with the zero, that would be awesome.by stylesuxx - Raspberry Pi(rate)Box
C'mon guys, testing is fun and quality assurance for the whole community. I am trying to get hold of an RPi2 and will add myself as 2nd tester for RPi1 and RPi2 if I can get hold of it. Still for the zero I will need someone for testing. It was impossible for me to get hold of one of those devices. Also willing to take a zero in form of a donation if that is how you are willing to help.by stylesuxx - Raspberry Pi(rate)Box
Hello community, I was talking to Matthias @32c3 and suggested I could take the RPI part off his hands. Yesterday I have been working on improving the build scripts and I am at a point where it is automated in a way that you just need to invoke one make target, lean back and wait for the image to come out ready to be dumped on a SD card. Right now I only have an RPI 1 B+ on my hands for testby stylesuxx - Raspberry Pi(rate)Box
Some links in the main menu are broken: HowTos => Troubleshooting => Laptop (maybe this item may be removed as a whole) About => Media + Logos (technically not broken but under construction, can we fill this with content somehow? Otherwise I would say we disable it.) Unfortunately I do not see where I can edit the menu, so I am leaving this here for someone who can ;-)by stylesuxx - PirateBox (Development)
Hmm, can not be. None of the commands should have changed anything, only the mtd command will overwrite your Firmware. Device should still be pingable and go into Failsafe mode,... Those devices are almost unbrickable - as long as you can access the serial console you can reflash them,... If you ever decide you want to look into it, let me know - we can meet in IRC and try to debug it liveby stylesuxx - PirateBox OpenWrt
OK, your thumb drive is not mounted. ls /dev/ you can compare the output of this ls with the stick attached and without, the device being added when you plug in the stick is the one you need to mount. mount /dev/sda1 /mnt/usb Where /dev/sda1 needs to be replaced by the device showing in /dev when you plug in your stick. I am heading off to work now. Will take some hours before Iby stylesuxx - PirateBox OpenWrt
OK, so that is not available -_- Does mount say anything? I had the impression that the USB stick should be automatically mounted if available at boot up and entering the failsafe mode. You could also try if you can ping google from your mr3020, if so you could wget the the file directly to /tmp without needing the usb stick. Try pinging google from your mr3020: ping google.comby stylesuxx - PirateBox OpenWrt
Interesting, could you please run fdisk -l and post the output.by stylesuxx - PirateBox OpenWrt
You connect to the router via telnet. Once connected you check that you can access the USB Stick ls /mnt/usb/ Now cd to the directory containing the *.bin and write it: cd /mnt/usb mtd write openwrt-ar71xx-generic-tl-mr3020-v1-squashfs-factory.bin firmware then reboot your device reboot You should then be able to Follow Upgrade Piratebox -> Install Pirateboxby stylesuxx - PirateBox OpenWrt
If you get it to Failsafe mode you should be able to recover. Check out this thread => especially the last post describes in detail what you have to do. To summarize, get a firmware, copy it to a USB stick, plug in USB stick, power MR3020 into failsafe mode, connect via telnet and write the firmware via mtd.by stylesuxx - PirateBox OpenWrt
As suggested by and discussed with Matthias there will be some changes in the PirateBox repositories on github. The first step will be to merge all package-openwrt-* into a single repository named openwrt-packages. The repositories to me merged are as follows: * package-openwrt-piratebox (state: develop > master, other branches) * package-openwrt-extendRoot (state: develop > master,by stylesuxx - PirateBox (Development)
What kind of WiFi stick do you have attached? Please post the output of sudo iw list If this has no ouput, please post the output of dmesg | grep usbby stylesuxx - Pi(rate)Box - unofficial images