Jump to content

or4n9e

Active Members
  • Posts

    34
  • Joined

  • Last visited

Posts posted by or4n9e

  1. why?

    svn co http://svn.fonosfera.org/fon-ng/trunk fon-ng

    it contains all ralink drivers

    differences between fon2.0g -> fon2.0n

    * 4 network ports

    * "stable" usb port (1.x & 2.x usb without the need for a 2.0 usb hub)

    * wifi-n : better wifi range possible even at "g" speeds

    * better cpu (400mhz instead of 182mhz) -> data throughput was bottlenecked due to this to 1Mbit... now it can have 8Mbit

    additional difference between fon2.0g -> fon2.0n

    * NO (at least worse) injection capabilities and thus a really BAD deal

  2. While this is certainly everyone's own decision, I cannot really see the point of using ANY of these various GUI flashers - besides the before-mentioned Fon Flash from Gargoyle - BUT even that one does NOT issue a "full initialization flash", a step that is urgently needed when e.g. moving from dd-wrt.

    Thus my question is simple: Is it really that difficult to flash the device manually utilizing the official install instructions at http://piranha.klashed.net/pub/inst? I mean, I'm certainly open for suggestions to make them even more straightforward for the users - no doubt about it!

    I'd just like to understand WHY you prefer bricking your devices with in-appropriate tools instead of appreciating to have the full control over the process. Please let me know! Just my 2c!

  3. JFYI, I notified our MMC guru at FoneraHacks via PM about your problem. I hope that he'll find the time to support you here. As I myself have no MMC card at all I guess I'll be of very little help here. One thing though... have you properly partitioned the MMC card with either a vfat or an ext2 filesystem(recommended)?

  4. I just flashed a fresh Install of Piranha 2 on the fon, but I can't see the /dev/mmc device, does i t have a differnt name?

    I myself have no MMC card attached to my fon, but here's the logread output of another Piranha 2 user

    Feb 6 02:08:43 OpenWrt user.warn kernel: gpio-mmc: Failed to request mmc_spi module.
    Feb 6 02:08:43 OpenWrt user.info kernel: mmc_spi spi32766.0: SD/MMC host mmc0, no DMA, no WP, no poweroff
    Feb 6 02:08:43 OpenWrt user.info kernel: gpio-mmc: MMC-Card "fonera" attached to GPIO pins di=1, do=3, clk=4, cs=7
    Feb 6 02:08:43 OpenWrt user.warn kernel: mmc_spi spi32766.0: can't change chip-select polarity
    Feb 6 02:08:44 OpenWrt user.info kernel: mmc0: new SDHC card on SPI
    Feb 6 02:08:44 OpenWrt user.info kernel: mmcblk0: mmc0:0000 SU04G 3979776KiB
    Feb 6 02:08:44 OpenWrt user.info kernel: mmcblk0:
    Feb 6 02:08:44 OpenWrt user.info kernel: p1

    Please compare this with your own logread output. If it matches, the 1st MMC card partition should be /dev/mmcblk0p1

    I juswondered, if there is a possibility to hook up a switch between GND and on of the unused gpio-pins, and if it would be possible to boot with different boot-scripts depending on if the switch is opened or close(either trying to get an internet-connection, or starting jasager) .How could I read out the signals on the gpio-pins? And the other pin might be used to connect a fourth LED that would show it the fon is connected to the internet or not.

    That's indeed a great idea - I have no experiences with it though. If you'll be able to come up with a reasonable solution, I'd be definitely willing to introduce your custom boot-scripts into upcoming Piranha versions - let me know please.

    Another thing I just realized, with wlanconfig it is possible get virtual devices running if you have madwifi installed. So if Jasager is running on the fon, shouldn't it be possible to get a bridge working over a second virtual device in ad-hoc mode, that is connected to a virtuall device in ad-hoc-mode in my Notebook?

    I flashed the new Piranha 2 on my fon, and have followed the instructions on the dimitar page there. I've been trying for about a week to get it working in Ubuntu on my laptop. I'm pretty sure I have everything set up on the Ubuntu side, but i think i'm missing something on the Fon. The instructions in the tutorial aren't for this LuCi interface.

    I think what i need to know is what the settings under Network -> LAN and WAN should be. DHCP, Bridged...? I have tried a lot of combinations. Clients connect, and get an IP (most of the time) but can't get it to dish out internet.

    To be honest, I have not that much of a clue about Jasager at all. I never used it by myself (yet) and just introduced it into Piranha 2 due to requests digininja and myself had out of the Hak5 community. digininja, would you please provide appropriate support to our fellow community members here?

    Thanks,

    orange

  5. thanks for the information. To be honest, I didn't try it without installing a new driver.

    You're welcome! I'm not sure if you got me right though... there's no need at all to install the driver. It's PRE-installed and PRE-configured. Just flash Piranha 2 and it should work without any other user interaction besides mounting the MMC card... supported filesystems are vfat and ext2.

  6. But one problem I've got is to get a working mmc-driver for kernel-version 2.6.26.5

    To be honest, this is a bit surprising to me. Piranha 2 ships with a working mmc-driver for kernel 2.6.26.5 pre-installed and even pre-configured for use with the Fonera. Thus it should just work out-of-the-box and is reported so by several other Piranha 2 users.

    Could you please give some more insight into the particular issue you have with it?

    The pre-configuration is based upon http://code.bastart.eu.org/files/fon_mmc/#instructions

  7. does hostapd need to be killed if wpa-psk has been removed and the fon is running with unencrypted wireless?

    no, hostapd just takes care of the wpa2-psk encryption. If you configured Piranha 2 with an unencrypted network instead, there shouldn't be any hostapd running at all. digininja, please correct this if an unencrypted wireless has an impact on proper Jasager functionality as well.

    Am I correct in assuming that I should be using the openwrt-atheros-root.squashfs file when flashing using the Piranha procedure? Because the procedure found here is using the jffs2 filesystem image. Under what circumstances would I use the jffs2 image instead of the squashfs image? I see their sizes are quite different.

    It's just a matter of choice whether you flash the squashfs or the jffs2 image - both images contain exactly the same packages.

    1. squashfs has a higher compression, thus smaller image size

    2. jffs2 is r/w, while squashfs is r/o with jffs2 overlay (thus pseudo r/w - google mini_fo for more information on this). If you know knoppix with aufs/unionfs... mini_fo is pretty much the same

    I never provided squashfs images in the past, but built them. To give the user the ultimate choice, I decided to upload both. Just decide on your personal preference which one to use!

    best,

    orange

  8. oh....so that's it?

    no more development for now?

    oh ok...maybe i'll just shelve the project for six months...

    I'm sorry, but I have no more time to care about it currently. Piranha 2 alpha3/alpha4 is pretty stable and thus usable though - so, you don't need to shelve it. The only known error with alpha4=Jasager edition currently is, that you need to "killall hostapd" to destroy the wpa2-psk encrypted wireless ap Piranha 2 ships with by default and you'll be ready to use Jasager.

    HTH orange

  9. Alright I got it working... Must have been the flasher... EasyFlash.

    tried it with FonFlash and it worked (took forever 20 mins)

    but it worked.

    Great, have fun with it! Jasager testing is highly appreciated.

    @all

    If you encounter any strange behaviour like jdogherman did, please report what method you used for flashing. The instructions at http://piranha.klashed.net/pub/inst are provided for a particular reason and I'd like to avoid wasting of time by "supporting" 3rd party tools like "EasyFlash" - that's imho the best example that the EASIEST way is to do it manually - the reason? it works!!!

    PS: if you urgently need a GUI based tool, I'd recommend Fon Flash from http://gargoyle-router.com/ - but to make this very clear - it's anyway the second best option to flash Piranha 2 as Fon Flash does e.g. NOT issue a full initialization flash and that might be urgently needed, especially if you're migrating from dd-wrt. Flashing manually is always preferred.

    Thanks in advance for considering this,

    orange

  10. @orange The Kismet Drone, does that need to connect to a Kismet server?

    Indeed, you need a kismet-server! The kismet-drone is fully preconfigured though for usage on the fon - it accepts connections on TCP port 3501 from all machines in range of 192.168.1.0/24

    To change this configuration please adjust /etc/firewall.user respectively /etc/kismet_drone.conf

    HTH

    orange

  11. Just brainstorming to the ether here:

    The thing is I had jasager beta firmware running on my 2201 without issue. but the piranha dosen't seem to work, I dont see that wireless ssid.

    Has anyone else tried this firmware on the 2201?

    @Orange

    The reason I was thinking of building it from OWRT 8.09 is that I could then find what breaks the router and be able to go back and find how to fix it.

    IC your point clearly. Let's try to find out what causes the issues you have. Have you flashed using the provided instructions? http://piranha.klashed.net/pub/inst

    Have you done a full initialization flash as described there? fis init -f

    Have you used fis create -l 0x00700000 rootfs while flashing the rootfs - Piranha 2 alpha4 differs here from stock OpenWrt (704kb kernel vs. 768kb kernel) while this is just a reason of the Archlinux GCC I'm using at my buildhost.

    I'm running it on 2201. Haven't had any issues with assigning IP addresses through a wired connection.

    As you see taiyed14 doesn't have the issues you encounter using exactely the same fon model. Please check everything you've done twice to be 100% sure it's not a user error - I'm sorry for the discomfort but it should work out-of-the-box. Never had an issue with alpha1..4, while running them on 2100 at least.

  12. Is there a list of tools built into Piranah2?

    Please have a look at http://piranha.klashed.net/pub/2.0/packages/ - the repository is a 1:1 mirror of the jffs2. If you have any particular questions about certain tools, feel free to ask. The release announcement for each Piranha 2 alpha release (including changelog) can be found within this thread http://www.fonerahacks.com/forums/viewtopi...p?f=3&t=320

    @jdogherman

    I'm sorry, but I'm not willing to support general "how to install whatever to 2201" questions - I hope you don't mind this statement cause there's definitely no offense intended - it's just that Piranha 2 is based on OpenWrt 8.09 branch and everything that's supported by OpenWrt 8.09 is supported the same way by Piranha 2 alpha4. I don't know about the 2201's model specifics - I'm running a bunch of 2100s here, but there's no difference in the 2100/2201 images from both OpenWrt and Piranha, it's actually just the same.

    For your reference: Piranha 2 alpha4 broadcasts a wpa2-psk encrypted SSID "default" with passwd "k4m1k4z3" while stock OpenWrt 8.09 does not - that's the only difference from an initial network setup perspective.

    can I load a openwrt and add the package reps from piranha to add the necessary packages and patches?

    While this might be possible, that does not make too much sense - I'd highly recommend installing Piranha 2 alpha4 instead of fiddling Piranha 2 alpha4 packages into stock OpenWrt 8.09. It's not just the packages cause e.g. digininja's karma patch is not applied to OpenWrt 8.09's stock madwifi nor are other Piranha 2 patches.

    HTH,

    orange

  13. Sorry for starting a new topic but I'd like to ensure this is placed prominently enough.

    It's Jasager time! Piranha 2 alpha4 got released today and this is the very first build that introduces Jasager 2.1 into my firmware. I'd like to take the opportunity to thank digininja for his support and great teamwork - he did a good job with the integration of Jasager and patching of madwifi. The full release announcement (with additional information) for Piranha 2 alpha4 can be found at http://www.fonerahacks.com/forums/viewtopi...mp;p=1844#p1844 as usual.

    I'd like to make very clear that the participation of the Hak5 community is mission-critical this time from a testing perspective. Nobody knows Jasager better than YOU, so please report bugs, either here, at http://fonerahacks.com/forums or at http://piranha.klashed.net

    The whole Hak5 community this certainly welcome to join the FoneraHacks testing team at #fonerahacks on irc.freenode.net - please support this collaboration between Piranha and Jasager the best that you can.

    Thanks for listening,

    orange

  14. I'd agree with that but I'd also suggest having a go by hand at some point. Once you've flashed by hand you can appreciate what the automated tool is doing and will help if you have any problems in the future.

    I'm completely on the same page here as digininja. Doing it manually is neither difficult nor not worth it. You learn a lot what you're actually doing.

  15. Hello everyone, I am in the process of purchasing my fon + for use with jaseger. So after some research i was looking at a few install methods. I have seen various auto flashing tools and some manual install methods, but which one would be the easiest for the person who is new to hardware flashing? I am looking to put the jaseger v2 on the fon+ simply put.

    thanks in advance

    Use Fon Flash available at http://www.gargoyle-router.com/download.php

  16. Not that much enthusiasm at once please :rolleyes:

    Ok, first step (not the most elegant but hopefully effective one) from my perspective would be to write kinda "nvram emulator" for all nvram variables autoap uses, i.e. a shellscript "nvram". It should just map all nvram calls to appropriate uci calls. Is there anyone interested in contributing? I'm on my way trying this currently - some support (especially with the GUI part) would be great though.

    thanks,

    orange

  17. Do you happen to have any other links to original firmware for 2201?

    I'm sorry but I neither have a 2201 myself nor do I know about restoring howtos for that particular model. Have you already tried to load stock openwrt, install chillispot and get the 32-digit string without a stock firmware? I mean getting the string from fon's radius server is all you need to do. I did it with a stock fonera, but (although this is untested) I see no real reason why this shouldn't work.

  18. In any case, restoring the stock firmware is described here http://www.fonerahacks.com/index.php/Tutor...l-Firmware.html and enabling ssh should be known to you. Otherwise you wouldn't have something 3rd party on your fonera currently. Obviously if you're going to restore the stock firmware onto that fonera you're going to run Piranha 2 on you do not need to go through the process at all - just register it as normal, reflash to Piranha 2 and run "thinclient start" and afterwards "/etc/init.d/cron start" or reboot. The described procedure is just in case you have at least two foneras: one with stock firmware to register the other one with Piranha 2 on it - hope this is clear.

×
×
  • Create New...