NEWS: New omni for Air-Stream-Woodville-West

Today I installed a shiny new 15dBi Omni Antenna and took down the WaveGuide. Hopefully this will give a good range for clients.

It also has the advantage of being lighter. The waveguide and dish was about the max weight that the pivot assy would support. Now at least 2 more dishes and another wrap or 2 ethernet devices could go up there.

Also in talks to fix the APANA to Woodville-West link, and possibly a Woodville-West-Ottoway link.


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

how frustrating

Just look how frustrating it can be to setup a link!
I did 2 sets of pings to APANA about 10 minutes apart. Changed nothing.

voyage:~# ping 10.121.128.97
PING 10.121.128.97 (10.121.128.97) 56(84) bytes of data.
64 bytes from 10.121.128.97: icmp_seq=1 ttl=255 time=6.87 ms
64 bytes from 10.121.128.97: icmp_seq=2 ttl=255 time=2.09 ms
64 bytes from 10.121.128.97: icmp_seq=3 ttl=255 time=2.09 ms
64 bytes from 10.121.128.97: icmp_seq=4 ttl=255 time=3.09 ms
64 bytes from 10.121.128.97: icmp_seq=5 ttl=255 time=2.09 ms
64 bytes from 10.121.128.97: icmp_seq=6 ttl=255 time=3.08 ms
64 bytes from 10.121.128.97: icmp_seq=7 ttl=255 time=2.99 ms
64 bytes from 10.121.128.97: icmp_seq=8 ttl=255 time=2.10 ms
64 bytes from 10.121.128.97: icmp_seq=9 ttl=255 time=2.96 ms
64 bytes from 10.121.128.97: icmp_seq=10 ttl=255 time=3.03 ms
64 bytes from 10.121.128.97: icmp_seq=11 ttl=255 time=4.10 ms
64 bytes from 10.121.128.97: icmp_seq=12 ttl=255 time=3.10 ms
64 bytes from 10.121.128.97: icmp_seq=13 ttl=255 time=3.09 ms
64 bytes from 10.121.128.97: icmp_seq=14 ttl=255 time=3.09 ms
64 bytes from 10.121.128.97: icmp_seq=15 ttl=255 time=2.10 ms
64 bytes from 10.121.128.97: icmp_seq=16 ttl=255 time=5.09 ms
64 bytes from 10.121.128.97: icmp_seq=17 ttl=255 time=2.10 ms
64 bytes from 10.121.128.97: icmp_seq=18 ttl=255 time=3.09 ms
64 bytes from 10.121.128.97: icmp_seq=19 ttl=255 time=3.01 ms
64 bytes from 10.121.128.97: icmp_seq=20 ttl=255 time=2.09 ms
64 bytes from 10.121.128.97: icmp_seq=21 ttl=255 time=2.10 ms
64 bytes from 10.121.128.97: icmp_seq=22 ttl=255 time=2.10 ms
64 bytes from 10.121.128.97: icmp_seq=23 ttl=255 time=3.09 ms
64 bytes from 10.121.128.97: icmp_seq=24 ttl=255 time=2.09 ms
64 bytes from 10.121.128.97: icmp_seq=25 ttl=255 time=2.09 ms
64 bytes from 10.121.128.97: icmp_seq=26 ttl=255 time=4.10 ms
64 bytes from 10.121.128.97: icmp_seq=27 ttl=255 time=2.95 ms
64 bytes from 10.121.128.97: icmp_seq=28 ttl=255 time=3.09 ms
64 bytes from 10.121.128.97: icmp_seq=29 ttl=255 time=2.09 ms

--- 10.121.128.97 ping statistics ---
29 packets transmitted, 29 received, 0% packet loss, time 28023ms
rtt min/avg/max/mdev = 2.090/2.932/6.876/1.044 ms

voyage:~# ping 10.121.128.97
PING 10.121.128.97 (10.121.128.97) 56(84) bytes of data.
64 bytes from 10.121.128.97: icmp_seq=1 ttl=255 time=26.6 ms
64 bytes from 10.121.128.97: icmp_seq=2 ttl=255 time=12.0 ms
64 bytes from 10.121.128.97: icmp_seq=3 ttl=255 time=3.07 ms
64 bytes from 10.121.128.97: icmp_seq=4 ttl=255 time=51.0 ms
64 bytes from 10.121.128.97: icmp_seq=5 ttl=255 time=2.09 ms
64 bytes from 10.121.128.97: icmp_seq=6 ttl=255 time=27.0 ms
64 bytes from 10.121.128.97: icmp_seq=7 ttl=255 time=111 ms
64 bytes from 10.121.128.97: icmp_seq=8 ttl=255 time=2.10 ms
64 bytes from 10.121.128.97: icmp_seq=9 ttl=255 time=44.0 ms
64 bytes from 10.121.128.97: icmp_seq=10 ttl=255 time=80.0 ms
64 bytes from 10.121.128.97: icmp_seq=12 ttl=255 time=3.10 ms
64 bytes from 10.121.128.97: icmp_seq=13 ttl=255 time=36.0 ms
64 bytes from 10.121.128.97: icmp_seq=14 ttl=255 time=16.0 ms
64 bytes from 10.121.128.97: icmp_seq=15 ttl=255 time=56.0 ms
64 bytes from 10.121.128.97: icmp_seq=16 ttl=255 time=11.0 ms
64 bytes from 10.121.128.97: icmp_seq=17 ttl=255 time=4.09 ms
64 bytes from 10.121.128.97: icmp_seq=18 ttl=255 time=7.10 ms

--- 10.121.128.97 ping statistics ---
19 packets transmitted, 17 received, 10% packet loss, time 18013ms
rtt min/avg/max/mdev = 2.096/29.006/111.082/30.213 ms

It shows a great link is possible but just needs some tweaking.

Im wondering what device is there...
I know it is a waveguide there for other clients to connect to, so I'm just wondering if it is possible, and if there is room on the router if there is one there, to put another device and a 19dBi or 25dBi directional antenna towards me for a backbone...

I think Steve said he might swing the waveguid a bit my way, not sure if he's had time yet, but just changing the channel made alot of difference.

Its great to see it working this much though!


Today I picked up my

Today I picked up my Air-Stream-Woodville-West omni when I was at Mitcham today :-) Right at the top of fullarton Road near the carrick hill turnoff.
also a SSID "BBanywhere" that I actually thought was in the same area as the woodville-west site.

Got Air-Stream-Ottoway as well up there.


Has anyone got KisWin to work?

Has anyone got KisWin to work?

Its available from sources such as http://www.churchofwifi.org/Project_Display.asp?PID=65 and renderman. It is just a kismet server and interface for connecting to a WRT54g droned AP.

Normally you need to d/l all of cygwin which is more than 100Mb, and make sure all the packages are in such as libncurses for the interface etc.

KisWin is just the files needed to run it and the gui stripped out of cygwin with a vbs script to run it.

I canmt get the damm thing to run, I am trying to run it to connect to the WRAP board over the internet, So it could be just access issues.

I cant see the kismet drone would be any different whatever it was run on, it would just spew out data to port 3501 and let whatever client connect and retrieve it.

Id be interested in any reports of it working, and any issues you had to overcome.


updates to blogs show up the

Seabird2k's picture

updates to blogs show up the same as new posts
so just as many ppl would read them, right ?

maybe
sb2k


gps

Seabird2k's picture

do u have gps ?
would be a nice addition if u dont

sb2k


just got home

4.20am.. tired..
on the way got 2603 networks.. some remote towns were wireless enabled..
the penthouse suite I was in had 28 visible from my rooftop :)
resisted the free inet, but did manage a few wep keys :)

now... beeeeedddd..


findon to ww a goer

Today I managed to get time to hold the minitar MNWAPB and new 19dBi grid towards woodville-west from the grange road site, and used the site survey tool.

The metal RHS is approx 7.5 metres and we initially tried it from the ground. Nothing.
So I took it up on the roof and held it up a bit back from the gutter. still nothing. I would have though 7.5m on top of there would be enough.

I then took it to the peak of the roof and finally got a signal to Woodville-West.

I didnt have time to log in and do any tests, but I still need to make some brackets for the guy wires.

It looks like to get anything happening when both sites are within a few KMs of each other you need major heightage.

I will swap the minitar for an UltraWAP (edimax)sometime in the next few days and see how it compares.


Pointing wrong

cougar's picture

HaQue,
I checked the map today with a compass and some of my old map and Nav skills which are a little rusty to say the least and I think I was pointing way too far east of T north for Woody West, though I dont know the exact location I used the hospital as a guide and it is 19deg magnetic from my location so I just scrambled up the tower and readjusted the pacmon so we will see what happens now. It a bit windy up there to dont think I will go up again today :)

Cougar


Aligning

Didz's picture

A stumbling rig is required for aligning at that distance and condidtions, a few millimetres and its the difference between great signal and no signal at all.


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.