bismark

Thanks, just found your other thread, posted before I looked.

Why the 3G router instead of directly attaching the 3G modem to the Pineapple? I'd see that as adding unnecessary steps/links in your comm chain not too mention adding more battery drain or does this setup give you extra control over the 3G connection?

Are you taking power from that battery pack in your picture? Might I request a labeled picture so I can understand how you have that nice bag setup? I'll try a powered USB hub tomorrow to see if that is the issue, it might be but I do know when I had the modem plugged straight into the Pineapple it was giving me troubles.

I have a 4 port usb "hub", actually I think it's this one specifically. Alone with the modem is a Sandisk Cruzer Fit 16GB, I was going to go with the 32GB but saw everyone using the 16GB and opted for it not knowing if there was an issue with the 32GB version.

Interesting, considering I'm using the wallwart right now for testing and I'm having problems with it. Here is a snippet from my logs overnight: 60318.640000] usbcore: deregistering interface driver usbserial_generic [60318.640000] generic ttyUSB0: generic converter now disconnected from ttyUSB0 [60318.650000] generic ttyUSB1: generic converter now disconnected from ttyUSB1 [60318.660000] generic ttyUSB2: generic converter now disconnected from ttyUSB2 [60318.660000] generic ttyUSB3: generic converter now disconnected from ttyUSB3 [60318.670000] usbserial_generic 1-1.2:1.0: device disconnected [60318.670000] USB Serial deregistering driver generic [60318.680000] usbcore: deregistering interface driver usbserial [60321.710000] usbcore: registered new interface driver usbserial [60321.720000] USB Serial support registered for generic [60321.720000] usbserial_generic 1-1.2:1.0: generic converter detected [60321.730000] usb 1-1.2: generic converter now attached to ttyUSB0 [60321.730000] usb 1-1.2: generic converter now attached to ttyUSB1 [60321.740000] usb 1-1.2: generic converter now attached to ttyUSB2 [60321.740000] usb 1-1.2: generic converter now attached to ttyUSB3 [60321.750000] usbcore: registered new interface driver usbserial_generic [60321.760000] usbserial: USB Serial Driver core [61518.660000] usbcore: deregistering interface driver usbserial_generic [61518.670000] generic ttyUSB0: generic converter now disconnected from ttyUSB0 [61518.670000] generic ttyUSB1: generic converter now disconnected from ttyUSB1 [61518.680000] generic ttyUSB2: generic converter now disconnected from ttyUSB2 [61518.690000] generic ttyUSB3: generic converter now disconnected from ttyUSB3 [61518.690000] usbserial_generic 1-1.2:1.0: device disconnected [61518.700000] USB Serial deregistering driver generic [61518.700000] usbcore: deregistering interface driver usbserial [61521.740000] usbcore: registered new interface driver usbserial [61521.740000] USB Serial support registered for generic [61521.750000] usbserial_generic 1-1.2:1.0: generic converter detected [61521.760000] usb 1-1.2: generic converter now attached to ttyUSB0 [61521.760000] usb 1-1.2: generic converter now attached to ttyUSB1 [61521.770000] usb 1-1.2: generic converter now attached to ttyUSB2 [61521.770000] usb 1-1.2: generic converter now attached to ttyUSB3 [61521.780000] usbcore: registered new interface driver usbserial_generic [61521.780000] usbserial: USB Serial Driver core [62718.680000] usbcore: deregistering interface driver usbserial_generic [62718.690000] generic ttyUSB0: generic converter now disconnected from ttyUSB0 [62718.700000] generic ttyUSB1: generic converter now disconnected from ttyUSB1 [62718.700000] generic ttyUSB2: generic converter now disconnected from ttyUSB2 [62718.710000] generic ttyUSB3: generic converter now disconnected from ttyUSB3 [62718.720000] usbserial_generic 1-1.2:1.0: device disconnected [62718.720000] USB Serial deregistering driver generic [62718.730000] usbcore: deregistering interface driver usbserial [62721.760000] usbcore: registered new interface driver usbserial [62721.760000] USB Serial support registered for generic [62721.770000] usbserial_generic 1-1.2:1.0: generic converter detected [62721.780000] usb 1-1.2: generic converter now attached to ttyUSB0 [62721.780000] usb 1-1.2: generic converter now attached to ttyUSB1 [62721.790000] usb 1-1.2: generic converter now attached to ttyUSB2 [62721.790000] usb 1-1.2: generic converter now attached to ttyUSB3 [62721.800000] usbcore: registered new interface driver usbserial_generic [62721.800000] usbserial: USB Serial Driver core Hmmm crap, this is the only usb modem that Ting has too. Yes this is exactly what I want, I do not want any targets data going across the 3G link, I only want it going across the bridge and out eth0 (which hopefully would be plugged into a PoE port, say inline with an IP phone). You bag setup looks awesome. I was planning on putting mine into a Pelican box or such but that bag is nice.

So far I have it sort of working without IPTABLES at all. Part of my issue is figuring out the format of the /etc/config/network. I can get it to bring up the default bridge (br-lan) on LAN/PoE and add wlan0 to it automatically but I have to manually add WAN (eth1) config interface 'loopback' option ifname 'lo' option proto 'static' option ipaddr '127.0.0.1' option netmask '255.0.0.0' config interface 'lan' option ifname 'eth0' option type 'bridge' config interface 'wan' option ifname 'eth1' config switch 'eth0' option enable_vlan '1' config switch_vlan option device 'eth0' option vlan '1' option ports '0 1 2' Once the Pineapple starts up I then do the following # brctl addif br-lan eth1 Which gives me the following # brctl show bridge name bridge id STP enabled interfaces br-lan 8000.00c0ca632d08 no wlan0 eth0 eth1 # ifconfig br-lan Link encap:Ethernet HWaddr 00:C0:CA:63:2D:08 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15150 errors:0 dropped:1146 overruns:0 frame:0 TX packets:129 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1651368 (1.5 MiB) TX bytes:14055 (13.7 KiB) eth0 Link encap:Ethernet HWaddr 00:C0:CA:63:2D:09 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15440 errors:0 dropped:30 overruns:0 frame:0 TX packets:157 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1956748 (1.8 MiB) TX bytes:17702 (17.2 KiB) Interrupt:5 eth1 Link encap:Ethernet HWaddr 00:C0:CA:63:2D:08 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:288 errors:0 dropped:9 overruns:0 frame:0 TX packets:980 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:85937 (83.9 KiB) TX bytes:145669 (142.2 KiB) Interrupt:4 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:73 errors:0 dropped:0 overruns:0 frame:0 TX packets:73 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3946 (3.8 KiB) TX bytes:3946 (3.8 KiB) mon.wlan0 Link encap:UNSPEC HWaddr 00-C0-CA-63-2D-0A-00-48-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:31772 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:5070294 (4.8 MiB) TX bytes:0 (0.0 B) wlan0 Link encap:Ethernet HWaddr 00:C0:CA:63:2D:0A UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:938 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:0 (0.0 B) TX bytes:162034 (158.2 KiB) # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface I'm connecting through the USB serial so there is no IP on the device as of right now (routing table blank). I connect a laptop up to the WAN port and it gets a DHCP lease just fine and can browse/ssh/apt-get/etc. just fine. My switch also doesn't notice the Pineapple as I have the basic NAC enabled on the port locked to the laptop's MAC address. Score! I have the firewall disabled and only ip_forwarding enabled. Next is trying to get the 3G modem to work, which the device itself (Ting's Sierra Wireless 598U) is giving me headaches as it's there then it's not. When it is there even though I have set the /www/pineapple/3g/3g.sh and /etc/config/network to NOT replace the default route it still becomes the default route and all traffic then goes through it... DOH. I need to figure out how to get the 3G modem handle only 1 or 2 ip addresses and then everything else just gets tossed at the bridge.

Pineapple Hardware Version: Mark IV Pineapple Software Version: 2.3.1 OS Used: Ultimately none, otherwise OS X & Backtrack So I'm poking around the innards (software) of the Wifi and I have a few questions. What is the difference/benefit of the /www/pineapple/ssh/ AutoSSH connection script versus the built in one under /etc/init.d/autossh & /etc/config/autossh? Has anyone gotten the Ting 598U microsd storage to work reliably? I saw the post about mounting /dev/sda twice and then it would see it. I've found however that even it if sees it initially it will eventually disappear and then not come back until a reboot of the Pineapple. Network setup. Was looking to setup the WLAN (Karma) and LAN ports as pass through from the network connection given to the WAN. Basically bridging the connection and becoming a passthrough AP for the target network. Then using the 3G modem as the egress point for AutoSSH. Possible with the current hardware?

Thanks inTheDMZ that worked perfectly, the ADA Fruit cable worked, just had to remove the correct pins and connect them up.

So yeah I was resetting the root password and I fat fingered my entry somehow and now I can't get into my Mark IV. Is there a way to go into the equivalent of single user mode on it to reset the root password or am I going to need to reflash it as if I bricked it? If reflashing is the case then will the following cable work from Adafruit work? https://www.adafruit.com/products/70 Feeling dumb now, going to go have a beer.

I finally have a serial cable connection and I'm able to see what is going on. On boot up after flashing the OM1P, version MR3201P, keeps repeating the following line: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000: 0x2d51 instead .... Finally ending at with the following: Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes empty_blocks 91, bad_blocks 0, c->nr_blocks 112 VFS: Cannot open root device "<NULL>" or unknown-block(31,1) Please append a correct "root=" boot option; here are the available partitions: Can anyone offer any insight or point me in a direction? I'd really like to get a greedy AP up and running for wireless assessments.

s/and\ so\ now/and\ so\ none/

I'm trying to install the Jasager firmware v2 onto a new Open-Mesh OM1P and currently I'm having no luck. I'm running OSX and so now of the easy/pretty tools work for loading, at least in my experience so far, but I'm not afraid of a little command line work in RedBoot. So I can get access to RedBoot on the device @ 192.168.0.1 and I'm able to upload firmware through tftp on my system. I've successfully installed OpenWRT 8.09.2 and the last build of Piranha. Unfortunately I'm looking to work with the Jasager Karma modifications which do not work with the prior version and though the later seems to have the madwifi patches from DigiNinja built it, Jasager doesn't run on it. So I'm stuck on trying to get the device to boot after loading the Jasager firmware. The firmware and kernel load itself goes fine no error messages or problems, the boot script is set to execute but when I issue reset, nothing happens it just hangs and never comes up on 192.168.1.1. I do see 192.168.0.1 appear again and can get back into RedBoot but never into OpenWRT. I've read each of the stuck topics and searched through other forums but no luck, even tried remote gdb debugging which never connected (would be interested in this just for the curiosity factor alone (Lines of scrolling text always makes one feel better). Does anyone have any suggestions or directions that I may have missed? Thanks, Bismark

I've tried the instructions listed with my recently received OM1P but it does not respond on any of the IP addresses that have been listed for possible defaults throughout this forum. Installing the latest release of OpenWRT straight from them works though this doesn't have Jasager working on it so it doesn't work for me. Also I've been unable to use ap51-flash-osx binary to flash the OM1P and have had to use a second Windows laptop, it starts and detects the device in Redboot mode but just hangs on the first flashing device status line. Are their different versions of the OM1P that might preclude the Jasager firmware from working on it?