Communication

From Seamonster
Jump to: navigation, search


2008/05/27 Cairn-MendPen Comm test

After some cable and antenna wrestling, we got it working. Logan and Marijke were up at Cairn Comm site, Matt on his roof out Mend Pen. One good trick was having a mirror to do the sunlight-location. A signal mirror needs to be part of our regular comm-kit! We communicated over cell phones (and didn't have luck w/ VHF--we should trouble shoot this. It may have been batteries on Matt's radio, but shouldn't have been.. I only had one LED lit, but I could tune into NOAA weather..)

Matt logged in from his MacBook Air laptop on MendPen roof (no external wifi, no antenna, no nothin') to Cairn. My understanding was that at Cairn there was the directional antenna, the 1W amp, and the Vaio. By ethernet this was plugged into the brick, into which I was able to telnet as brick/brick.

First, using iStumble on my Air (internal wifi only), I saw this nsrl SSID (and I think this was the vaio laptop, through the usb/wifi, amp, and directional, as via Logan, when Marijke turned it off, it quite answering):

http://seamonsterak.com/20080527wifi/20080527_wifi_sm_nsrl.png

Then a bit later (maybe this is the bridge on the brick or the router?)

http://seamonsterak.com/20080527wifi/20080527_wifi_sm_jnu.png

(The above also shows the router "juneauwireless" in adhoc mode on channel 11)

Logan thought he could see me, but with an odd MAC address: 02:18:DE:00:00:C7. Then finally I think what we had was, just my laptop, and on Cairn, maybe the vaio, with the usb/wifi, through the amp and directional, also ethernetted into the router, with the brick in the router (LOGAN: IS THIS CORRECT?). I was able to ping one machine (the vaio?) and then telnet into another, when I was on machine-to-machine (or adhoc) mode to seamonster. The session is:

http://seamonsterak.com/20080527wifi/20080527_wifi_login_userver.png

So, here's the new plan down at Mend Pen: keep the two routers in managed mode, but change the SSID to juneauwireless on Channel 6. put a third router (NEW MAC to come) in adhoc mode on the big omni with the amp--this will be seamonster on Channel 11 and ready to connect to Cairn (hopefully!)..

Heavner 18:02, 27 May 2008 (PDT)

Working 3 WRT54Gs doing WDS

Got it working. I need to label the specific WRT54Gs. Two are running openwrt (White Russian) and one is dd-wrt (I think I like this one better..)

Minor Issue: The G (running dd-wrt) doesn't have any working network ports. hmmm.... either fix or swap out the wrt54


For the record:

The working 2008 primary object map is:

pressure transducer > Campbell 1000 >(via serial) > VuS > wet54 > Cairn met/cam VuS (wrt54g) > Cairn comms VuS (wrt54g) > Matt's Wired Tree (wrt54g)

In this spirit, Matt is working on wrt54g > wrt54g > wrt54g comms

We plan on having potential for 900 MHz "backup backbone" and also a pressure transducer Iridium "total backup" comm path

So, start with three wrt54g*'s (one wrt54g, one wrt54gs, and one wrt54gl!) and take inventory:

wrt54gs

The wrt54gs upon power up, just goes to blinking power led (about twice a second) and blinking DMZ (on 4 seconds, off 4 seconds). This has masking tape that it was the "ValleyZero" node and was hence up in "matt's old wired tree" for two winters.

it also has "bricked?" on the tape.  No wifi ssid broadcast (even after ~15 minutes).  Working assumption: bricked.  onto next one

wrt54g

This says "192.168.1.1" with admin and "regular" password, essid nsrl, dhcpd, ap

upon boot, power LED is solid (progress from above!), all ethernet ports and WLAN and internet LEDs also solid lit--hmmm... no ssid broadcast. try ethernet connect next. none of the ports (1-4 or internet) produce any connection (diagnosed w/ Macbook/SystemPreferences>Network). working guess: bricked


ok, back to the g (after the wild successes with the gl below): doing the "hold reset for 30 seconds" I now get all led's still lit, but the WLAN light blinks "appropriately". I get the SSID dd-wrt and an IP address of 192.168.1.104 (I can't get an ethernet connection though), aha! Bricked no more. at http://192.168.1.1/ I know get the dd-wrt control panel and it is runing dd-wrt v23 sp2 (9/15/06) in AP mode on channel 6. Wireless MAC is 00:40:10:10:00:03, this is V5 hardware, so only 2MB flash! admin/"regular" isn't working... hmm.. did reset fix that? regular linksys didn't seem to work. google up dd-wrt default. (it isn't <blank>/admin anymore, now root/admin, and it worked)

about to enable WDS between this g and the gl below. on the WDS config page, dd-wrt offers me "wireless MAC" options of "disable", "point-to-point" or "LAN". I know I don't want the first, and I think I want the third, but off to read a bit and educate myself. going with LAN and added 00:1c:10:9e:7c:f5 (gl)

switched SSID to seamonster

wrt54gl

solid power LED, WLAN led blinks appropriately, no tape/notes w/ info. looks promising though...

nsrl SSID shows up! handed out 192.168.1.104, http connect to 192.168.1.1 and get openWrt admin.. says white russian, admin and standard password works. aha! a warm glow of progress is filling my office now.

I don't see any additional installed packages (usually I throw ntpdate on quickly, I see wireless-tools, haserl? is that standard?)

on Channel 6, AP mode, (mode options are access point, client, client (bridge), ad-hoc), no WDS and on diversity antenna,

this one looks ready to have WDS turned on, and be thrown to the field. I need the other MAC addresses (I've only seen negative (bandwidth impacts) regarding "Lazy WDS"--but wringing that out would be a good student project!)

WDS status

the wrt54g and wrt54gl described above are sharing the seamonster SSD and routing between each other and to the world. I need to really test out the WDS connection, but I believe it is working. Now to commune with the wrt54gs that is "Bricked"...

I can ping the wrt54gs (it is a v2.0 box) over one of the ethernet jacks--hope remains. Downloaded the White Russian openwrt image (openwrt-wrt54gs-squashfs.bin) pushed it using tftp (binary; trace; rexmt 1; timeout 90; put openwrt-wrt54gs-squashfs.bin) then let it reboot, and the friendly interface at http://192.168.1.1/ comes up..)

reset the ssid (seamonster) give it the regular password, add the two other MACS to the WDS list (g 00:40:10:10:00:03 ; gl 00:1c:10:9e:7c:f5)


Rearrange WRT54 WDS

The three WRT54s are currently set so that 192.168.1.3 is the gateway, with ---.2 being the relay, and ---.1 being the Cairn Met Station. There are a couple of ways to potentially improve this setup. First, ---.1 supposedly does not having any working Ethernet connections and thus it will be difficult to plug the Cairn Met brick into the unit. Second, we have a WRT54 running White Russian already installed in a pelican case and thus this unit would work well at Matt's house. Third, it seems like it would work better to have ---.1 be the gateway at Matt's house, with ---.2 as the relay, and ---.3 as Cairn Met. This would make it so that router ip addresses would increase as one moved away from Matt's house, thereby making it a little more intuitive. As such I propose these changes:

1. Replace the WRT54g with WRT54 already in the pelican case
2. Set the WRT54-pelican as the gateway with 192.168.1.1
3. Make ---.3 the Cairn Met router

Logan 10:11, 23 April 2008 (PDT)

WRT54 WDS info

Cairn Relay, 192.168.1.2, 00:1C:10:9E:7C:F5
Cairn Met, 192.168.1.3, 00:0F:66:52:83:C1
Default Gateway = 192.168.1.1
The MAC address given under the 'info' section of each router is not the address that should be put into the Network --> Advanced Wireless --> WDS Connections address slot on the other routers. Instead, the MAC address of the Access Point from under Status --> Wireless should be input into the WDS slots of of the other routers. The general MAC addresses endings are DC, F3, and BF, for .1, .2, and .3, respectively.

Logan 12:26, 23 April 2008 (PDT)

SM001

tape says "client mode", at 192.168.11.2

goal: get this "normal" (for lab testing/devel) and have it WDS w/ SM_WRT_25 and grab ntp data from the SM_WRT_25 ntpd

need root password... ug. This is running White Russian RC5 (test to confirm broken WDS (like at met station) and check nvram OS id.

MAC 00:13:10:00:3D:C8

SM_WRT_15

RIP

SM_WRT_16

10.124.1.2, SSID juneauwireless, standard password, White Russian, backports, wl and wiviz

Added SM_WRT_15 MAC to WDS ("automatic/Lazy WDS" means you only have to do one set of MAC addresses... not both.)

SM_WRT_18 is plugged into an ethernet port. It currently is using 10.124.1.XXX as its IP address from SM_WRT_16

This is in the roof at Matt's house. Here's how it looked..

SM WRT 16 20080707.png

This looked like the left antenna to me (left as viewed from the front). So I switched the web interface antenna setting (under network, advanced Wireless) to left, and.. no more network! I climbed up, switched the physical antenna connection to the other port (DIFFERENT THAN THE ABOVE PICTURE!) and the network is back (with the web interface antenna setting on left). This is a WRT54GL. (reading online makes me think maybe wrt54gl and wrt54gs and wrt54g are different?!) UG! We have to be careful here!

SM_WRT_17_MGT

Physical Location

Inside VuS 58 at Mendenhall Glacier Terminus MET

192.168.10.8 00:13:10:43:CC:93 (ethernet) 00:13:10:43:CC:93 (wifi)

openWrt White Russian 0.9

ssh with root is the standard passwd.. no seamonster user..

upgraded from White Russian RC2 with

mtd write openwrt-brcm-2.4-squashfs.trx linux && reboot

set the antenna on right (the nvram setting for this is)

wl0_antdiv="1"

right now the SSID is OpenWRT, but Nick will be fixing this..

SM_WRT_18

Physical Location: Roof out on the end of Mendenhall Peninsula

This is "roof" and is SM_MendPen, from nsrl1, root@roof will get you in

192.168.1.1 00:18:39:EC:BC:0C (ethernet) 00:18:39:EC:BC:0E (wifi) SSID: seamonster VPN: 10.8.1.54, adhoc

The ethernet is plugged into another linksys WRT54G's network port on Matt's MendPenJW_Roof router which is then plugged into the WiMax box on the roof.

This has a single amplifier and directional on the roof from the antenna port by the power (NEED TO CONFIRM THIS VIA PICTURE!)

SM_WRT_19

Physical Location

On the desk at NSRL

at 192.168.1.10 00:1E:E5:57:73:32 (ethernet) 00:1E:E5:57:73:34 (wifi)

in adhoc on Ch1 (auto) at SSID Seamonster at NSRL--this is a "placeholder" for SM_WRT_18 in adhoc at Matt's house

installed openvpn (for SM_WRT_19) and need to install ntpdate! at 10.8.1.50 on the VPN

did ntpclient -s -h ntp.alaska.edu (but should do this at each reboot.. otherwise vpn won't come up.)

SM_WRT_20

Physical Location: Sobellof Annex Hall

This is the "old MGVC Roof" unit, is running White Russian, it is serving as a bridge

Ethernet MAC 00:16:B6:DA:CE:61 Wifi MAC 00:16:B6:DA:CE:63

SM_WRT_21

Physical Location: ??

SSID kraken, MAC 00:1C:10:9E:7C:F5 (wifi), 10.0.0.1, white russian 0.9, has wiviz

was in Matt's office, but no longer... Heavner 11:46, 18 June 2009 (PDT) (maybe at Cairn/Relay? the MAC address is listed on Roof/WRT_18)

SM_WRT_22

This was out at MGT (on M&M) and went on the fritz--possibly shorted out (as the board was out of the case and contacts a metal plate in the brick). Next the LEDs all went to constant on state.

Fired up (2008/07/28) and it is working fine: conclusion? OK for testing things in NSRL, but not to be trusted for field deployments yet. 00:1C:10:34:31:DC (ETH MAC address)

openWRT - has wl but not wiviz

when "liberated" from the case, this is the smaller "quarter of the board cut out" version. It does appear to have the "push switch" for the CISCO "zeroconf"". I believe this is a WRT54GL v1.1

The case clips are snapped off.

Has SSID of c_monster and IP 192.168.10.8 (the MGT router IP)

SM_WRT_23

Physical Location

On the desk at NSRL

Specifications

Linksys WRT54GL v1.1
S/N CL7C1H58282
MAC 00:21:29:A5:80:B0
Firmware Version WHITE RUSSIAN (0.9)
Kernel Version Linux version 2.4.30 (nbd@ds10) (gcc version 3.4.4 (OpenWrt-1.0)) #1 Sat Feb 3 13:16:08 CET 2007
ESSID SMdev (login as root with standard password), White Russian, backports, wl, wiviz, ntpclient, and openvpn

Sm wrt 23.JPG

I found these 20081106_LabNotes (taken by Matt and Nick) which seem to be related to this critter.

SM_WRT_24

Physical Location

Inside VuS 53 at Cairn Peak Relay Station

Specifications

Linksys WRT54GL v1.1
S/N CL7C1H519505
MAC 00:21:29:A5:8F:05
Firmware Version WHITE RUSSIAN (0.9)
Kernel Version Linux version 2.4.30 (nbd@ds10) (gcc version 3.4.4 (OpenWrt-1.0)) #1 Sat Feb 3 13:16:08 CET 2007
ESSID SMrouter1 (login as root with standard password), White Russian, backports, wl, wiviz, ntpclient, and openvpn

DSC02240.JPG

Arrived pristine on my desk last week. Flashed with White Russion 0.9 on 2009/02/23 using the following method:

Download the white russian firmware openwrt-wrt54g-squashfs.bin from http://downloads.openwrt.org/whiterussian/newest/default/.

Log in to the linksys web console with a blank username and password admin then go to Administration > Firmware Upgrade or paste http://192.168.1.1/Upgrade.asp into your browser. That should bring you to this screen.

Linksysadmin.jpg

Select openwrt-wrt54g-squashfs.bin and hit the upgrade button. DO NOT INTERRUPT the upgrade process. Once you get the screen shown below hit continue.

Success.jpg

That should take you to this page:

Openwrtadmin.jpg

Congrats.

SM_WRT_25

Physical Location Matt's campus office

Specifications

Linksys WRT54GL v1.1
S/N CL7C1H519436
MAC 00:21:29:A5:8E:36
Firmware Version WHITE RUSSIAN (0.9)
Kernel Version Linux version 2.4.30 (nbd@ds10) (gcc version 3.4.4 (OpenWrt-1.0)) #1 Sat Feb 3 13:16:08 CET 2007
ESSID SMrouter2 (login as root with standard password), White Russian, backports, wl, wiviz, ntpclient, and openvpn, openntpd
, Sm wrt 25.jpg

Flashed 2009/02/24

SM_WRT_26

Specifications

Linksys WRT54GL v1.1
S/N CL7C1H610535
MAC 00:21:29:B5:90:9C
Firmware Version WHITE RUSSIAN (0.9)
Kernel Version Linux version 2.4.30 (nbd@ds10) (gcc version 3.4.4 (OpenWrt-1.0)) #1 Sat Feb 3 13:16:08 CET 2007
ESSID SMrouter3 (login as root with standard password), White Russian, backports, wl, wiviz, ntpclient, and openvpn

Sm wrt 26.jpg

Flashed on 2009/02/24

SM_WRT_27

Physical Location:

In VuS 60, at NSRL

Specifications

Linksys WRT54GL v1.1
S/N CL7C1H606092
MAC 00:21:29:B5:5C:8B
Firmware Version WHITE RUSSIAN (0.9)
Kernel Version Linux version 2.4.30 (nbd@ds10) (gcc version 3.4.4 (OpenWrt-1.0)) #1 Sat Feb 3 13:16:08 CET 2007
ESSID SMrouter4 (login as root with standard password), backports, wl, wiviz, ntpclient, and openvpn

Sm wrt 27.jpg

Flashed on 2009/02/25.

SM_WRT_28

Physical Location

In the wireless drawer at NSRL

Specifications

Linksys WRT54GL v1.1
S/N CL7C1H606094
MAC 00:21:29:B5:5C:91
Firmware Version WHITE RUSSIAN (0.9)
Kernel Version Linux version 2.4.30 (nbd@ds10) (gcc version 3.4.4 (OpenWrt-1.0)) #1 Sat Feb 3 13:16:08 CET 2007
ESSID SMrouter5 (login as root with standard password), openvpn, rsync, ntpclient, backports, wl, and wiviz

Sm wrt 28.jpg

Flashed on 2009/02/25.

Had a nice adventure setting this critter up on the Seamonster_VPN. Followed the instructions for Adding_a_machine_to_OpenVPN. I think when it comes to transferring the keys and certificates you'll find that it's worth it to add rsync to the router's repertoire via:

root@SM_WRT_28:~# ipkg update
root@SM_WRT_28:~# ipkg install rsync

Once you've finished following the instructions for adding a machine and get to the "Testing the Connection" step you'll get the following error:

Sat Jan  1 00:01:32 2000 VERIFY ERROR: depth=1, error=certificate is not yet valid: /C=US/ST=AK/L=Juneau/O=Seamonster/CN=seamonster/emailAddress=eknuth@gmail.com
Sat Jan  1 00:01:32 2000 TLS_ERROR: BIO read tls_read_plaintext error: error:14090086:lib(20):func(144):reason(134)
Sat Jan  1 00:01:32 2000 TLS Error: TLS object -> incoming plaintext read error
Sat Jan  1 00:01:32 2000 TLS Error: TLS handshake failed
Sat Jan  1 00:01:32 2000 Fatal TLS error (check_tls_errors_co), restarting
Sat Jan  1 00:01:32 2000 TCP/UDP: Closing socket

The reason the certificate isn't valid is because the date on the router is out of the validity range. So you need to install ntpclient:

root@SM_WRT_28:/etc/openvpn# ipkg install ntpclient
root@SM_WRT_28:/etc/openvpn# reboot

Log back in after the router has restarted, check the date, and then test the connection again. The output I got was:

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 WHITE RUSSIAN (0.9) -------------------------------
  * 2 oz Vodka   Mix the Vodka and Kahlua together
  * 1 oz Kahlua  over ice, then float the cream or
  * 1/2oz cream  milk on the top.
 ---------------------------------------------------
root@SM_WRT_28:~# date
Sat Feb 28 00:59:28 UTC 2009
root@SM_WRT_28:~# openvpn /etc/openvpn/client.conf
Sat Feb 28 00:59:53 2009 OpenVPN 2.0.8 mipsel-linux [SSL] [LZO] [EPOLL] built on Jan 30 2007
Sat Feb 28 00:59:53 2009 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Sat Feb 28 00:59:54 2009 LZO compression initialized
Sat Feb 28 00:59:54 2009 Control Channel MTU parms [ L:1560 D:140 EF:40 EB:0 ET:0 EL:0 ]
Sat Feb 28 00:59:54 2009 Data Channel MTU parms [ L:1560 D:1450 EF:60 EB:135 ET:0 EL:0 AF:3/1 ]
Sat Feb 28 00:59:54 2009 Local Options hash (VER=V4): 'bc07730e'
Sat Feb 28 00:59:54 2009 Expected Remote Options hash (VER=V4): 'b695cb4a'
Sat Feb 28 00:59:54 2009 Attempting to establish TCP connection with 137.229.208.19:8084
Sat Feb 28 00:59:54 2009 TCP connection established with 137.229.208.19:8084
Sat Feb 28 00:59:54 2009 TCPv4_CLIENT link local: [undef]
Sat Feb 28 00:59:54 2009 TCPv4_CLIENT link remote: 137.229.208.19:8084
Sat Feb 28 00:59:54 2009 TLS: Initial packet from 137.229.208.19:8084, sid=fd914cc5 64b5726e
Sat Feb 28 00:59:54 2009 VERIFY OK: depth=1, /C=US/ST=AK/L=Juneau/O=Seamonster/CN=seamonster/emailAddress=eknuth@gmail.com
Sat Feb 28 00:59:54 2009 VERIFY OK: depth=0, /C=US/ST=AK/L=Juneau/O=Seamonster/CN=server/emailAddress=eknuth@gmail.com
Sat Feb 28 00:59:55 2009 Data Channel Encrypt: Cipher 'AES-128-CBC' initialized with 128 bit key
Sat Feb 28 00:59:55 2009 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Feb 28 00:59:55 2009 Data Channel Decrypt: Cipher 'AES-128-CBC' initialized with 128 bit key
Sat Feb 28 00:59:55 2009 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Feb 28 00:59:55 2009 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Sat Feb 28 00:59:55 2009 [server] Peer Connection Initiated with 137.229.208.19:8084
Sat Feb 28 00:59:57 2009 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Sat Feb 28 00:59:57 2009 PUSH: Received control message: 'PUSH_REPLY,route 10.8.1.0 255.255.255.0,ifconfig 10.8.1.70 10.8.1.69'
Sat Feb 28 00:59:57 2009 OPTIONS IMPORT: --ifconfig/up options modified
Sat Feb 28 00:59:57 2009 OPTIONS IMPORT: route options modified
Sat Feb 28 00:59:57 2009 TUN/TAP device tun0 opened
Sat Feb 28 00:59:57 2009 /sbin/ifconfig tun0 10.8.1.70 pointopoint 10.8.1.69 mtu 1500
Sat Feb 28 00:59:57 2009 /sbin/route add -net 10.8.1.0 netmask 255.255.255.0 gw 10.8.1.69
Sat Feb 28 00:59:57 2009 Initialization Sequence Completed

This router's address on the VPN is 10.8.1.70

Follow the instructions for "Starting OpenVPN on Boot" to ensure that OpenVPN will run on the router after it has been rebooted.

SM_WRT_29

Physical Location

On the desk an NSRL

Specifications

Linksys WRT54GL v1.1
S/N CL7C1J313815
MAC 00:23:69:82:AB:46
Firmware Version WHITE RUSSIAN (0.9)
Kernel Version Linux version 2.4.30 (nbd@ds10) (gcc version 3.4.4 (OpenWrt-1.0)) #1 Sat Feb 3 13:16:08 CET 2007
ESSID seamonster (login as root with standard password), openvpn, rsync, ntpclient, backports, wl, and wiviz