@bodhi Of course I'll share the code when I have something usable & stable, but keep in mind that I have just implemented webconfig for network related tools. I'll upload files to github (just webconfig, boot-scripts and buildroot & kernel patches; all the rest is based on buildroot) when I finished some javascript related issues. If you want a current screenshot check theby pazos - Debian
CONGRATULATIONS!!! Sometimes it is better to 'Keep It Simple' If you planned to attach usb storage why don't you get a spooling printer server like cups instead of p910nd ( that is a great piece of software for embedded devices like routers, but it lacks some exciting features of common unix printer system) I'm working in a really interesting mod for my pink-pogo (sometiby pazos - Debian
I have an AP working with Debian & hostapd with an ath9k usb card and a SINGLE ethernet port (both bridged); the hardware is NOT a plug device, but it is the same; My configuration is: ADSL Router: static IP -> 192.168.0.254/24 Wireless AP: static IP -> 192.168.0.254/24 with gateway: 192.168.254/24. I also edit /etc/resolv.conf to point to my wired router: nameserver 192.168.by pazos - Debian
I have an AP working with Debian & hostapd with an ath9k usb card and a SINGLE ethernet port (both bridged); the hardware is NOT a plug device, but it is the same; My configuration is: ADSL Router: static IP -> 192.168.0.254/24 Wireless AP: static IP -> 192.168.0.254/24 with gateway: 192.168.254/24. I also edit /etc/resolv.conf to point to my wired router: nameserver 192.168.by pazos - Debian
OK! If you want to have a router on your device you'll need to activate ip_forward. The easiest way is type on your prompt: echo "1" > /proc/sys/net/ipv4/ip_forward The other thing needed is activate NAT: iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE Everything works now... Or it should work :)by pazos - Debian
Your wireless device needs to have a satic ip like: 192.168.1.1 netmask 255.255.255.0 Your dhcp server needs the following parameters: subnet: for example 192.168.1.0/24 gateway: that gives you internet connection; for example; 192.168.1.254 and a range to give ip's; example: 192.168.1.10 192.168.1.20. If you don't specify domain-name-servers on the dhcp server configurationby pazos - Debian
Hi hack247, sorry but I had no time to give you a response!. I just check your post and it is wonderfull, but it seems that you have the original bootloader on your device (at least putty screen shows that). In order to install another linux distro I would recommend you to install jeff bootloader http://jeff.doozan.com/debian/uboot . If you want to install Openwrt this is not neccesary (as seen hby pazos - Debian
Or you can install uboot-mkimage on your host machine and just compile the "u-boot kernel" with: make uImage # just the kernel make uImage modules # kernel & modules Works in the same way as x86 classic 'make bzImage' but you need to install mkimage before proceed.by pazos - Debian
Ok! First of all; Did you hook a serial connection to your pogo device? It would be a good idea to have serial access before touch anything in nand partition. Second thing: you must check if Openwrt doesn't suit for you needs. Openwrt is a great piece of software and can fit in 4 - 8MB, leaving free space for all stuff needed. I installed emdebian after trying openwrt. Reasons? My pby pazos - Debian
It is the same. I have one pink pogo and Jeff script works wonderfully! But you've noticed that the pogo-e02 has only 128MB of flash memory (maybe less if you are using the stock pogo firmware or jeff's rescue system). I removed all mtd partitions except the first (u-boot), and create another two partitions (the first one for a stripped down kernel:3MB) and the last one for the UBITby pazos - Debian
If you want to set static ip for wireless you can try DHCP Static leases for your device (attaching your wireless interface MAC to an IP). I really think that is a configuration problem, not a kernel or device problem. When I started to play with embedded devices like pogo I found that worked better if I declare only wired interfaces in /etc/network/interfaces and then make a script at the endby pazos - Debian
>And the issue persists. As soon as I unplug the wired interface, I can no longer ping the wireless IP But, can you associate with the AP?. Cause maybe your wireless iface doesn't connect and the only way to see it and to ping it is via wired connection. Anyways,if you use Dinamic IP on your wireless connection & Static IP on your wired connection, both dhcpcd & dhclient manby pazos - Debian
Hi Davygravy. Could you post some images of your hardware? I'm too interested in build a indoor weather station based on pogo, like yours... But I have not knowledge about 1-wire stuff... Thanksby pazos - Debian
hi rawsted... please post the output of 'route -n' Your interfaces file has redundant information... I would try to change it to: auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.1.101 netmask 255.255.255.0 gateway 192.168.1.1 auto wlan0 iface wlan0 inet static wpa-driver wext wpa-ssid calvin wpa-bssid wpa-psk "" wpa-keby pazos - Debian
I don't know so much about Debian specific kernel configuration but the error said: illegal package name linux-2.6.38.4-dockstar-pogo_e02 and you used --append-to-version=-dockstar while default kernel config said local_version=pogo_e02 . Maybe it could work if you leave the --append-to-version= fields in blank Something like: make-kpkg --rootcmd fakeroot --arch armel --cross-compileby pazos - Debian
If you still want led support for the pink pogo you'll find it here >> http://forum.doozan.com/read.php?2,5579by pazos - Debian
Of course. Try to patch your 2.6.38.x kernel. If you'll find hunk failed messages then look at the patch itself and modify your files to look the same! Don't forget you choose support for Dockstar/Sheevaplug devices in order to boot the kernel with default dockstar arcNumber. Try if the kernel works before change the arcNumber, and then type on your terminal fw_setenv arcNumber 'by pazos - Debian
Hey folks! Many of us want a kernel with full support for our pogoplugs. Until now we use a default kernel (from sheevaplug or dockstar) but now pogoplug have its own machine id and it is the time to make a kernel just for pogo.There is not a hard work to do some changes cause pogoplugs & dockstar are identical, except for mtd partitions and led-gpio arrangements. The patch here is forby pazos - Debian