Switch to 10 MHz channel plan ACTION REQUIRED
We will be switching the network from the 5 MHz channel plan to the 10 MHz channel plan. This affects sectors and client nodes. Client nodes that are live on the network and have shared administration enabled will be updated automatically. Other clients will need to update their own channel list. With the following channels configured in your modem, it will scan for the new channel as soon as the old channel disappears: /interface wireless channels # Current 5 MHz plan add band=5ghz-onlyn comment="Cell sites radiate this at 0 degrees (north)" frequency=5920 list=HamWAN name=Sector1 width=5 add band=5ghz-onlyn comment="Cell sites radiate this at 120 degrees (south-east)" frequency=5905 list=HamWAN name=Sector2 width=5 add band=5ghz-onlyn comment="Cell sites radiate this at 240 degrees (south-west)" frequency=5890 list=HamWAN name=Sector3 width=5 # New 5 MHz bandwidth in 10 MHz channel plan (first channel is identical to old 5 MHz plan) add band=5ghz-onlyn comment="Cell sites radiate this at 0 degrees (north)" frequency=5920 list=HamWAN name=Sector1-5 width=5 add band=5ghz-onlyn comment="Cell sites radiate this at 120 degrees (south-east)" frequency=5900 list=HamWAN name=Sector2-5 width=5 add band=5ghz-onlyn comment="Cell sites radiate this at 240 degrees (south-west)" frequency=5880 list=HamWAN name=Sector3-5 width=5 # New 10 MHz bandwidth in 10 MHz channel plan add band=5ghz-onlyn comment="Cell sites radiate this at 0 degrees (north)" frequency=5920 list=HamWAN name=Sector1-10 width=10 add band=5ghz-onlyn comment="Cell sites radiate this at 120 degrees (south-east)" frequency=5900 list=HamWAN name=Sector2-10 width=10 add band=5ghz-onlyn comment="Cell sites radiate this at 240 degrees (south-west)" frequency=5880 list=HamWAN name=Sector3-10 width=10 For optimal performance, some sectors will continue to use 5 MHz bandwidth on the new 10 MHz-plan center frequencies. Add all the above channels to ensure your modem will connect in this situation. This change will be implemented in 7 days, August 9th. Please update your configuration before then for a smooth transition. Tom KD7LXL
Are these commands correct for modems which already have the 5-in-5 set of channels programmed? Will it needlessly duplicate those channels? What if they aren't named "Sector[123]" before I start applying this set of commands? --Bart On 8/2/2014 10:49 AM, Tom Hayward wrote:
We will be switching the network from the 5 MHz channel plan to the 10 MHz channel plan. This affects sectors and client nodes. Client nodes that are live on the network and have shared administration enabled will be updated automatically. Other clients will need to update their own channel list. With the following channels configured in your modem, it will scan for the new channel as soon as the old channel disappears:
/interface wireless channels # Current 5 MHz plan add band=5ghz-onlyn comment="Cell sites radiate this at 0 degrees (north)" frequency=5920 list=HamWAN name=Sector1 width=5 add band=5ghz-onlyn comment="Cell sites radiate this at 120 degrees (south-east)" frequency=5905 list=HamWAN name=Sector2 width=5 add band=5ghz-onlyn comment="Cell sites radiate this at 240 degrees (south-west)" frequency=5890 list=HamWAN name=Sector3 width=5 # New 5 MHz bandwidth in 10 MHz channel plan (first channel is identical to old 5 MHz plan) add band=5ghz-onlyn comment="Cell sites radiate this at 0 degrees (north)" frequency=5920 list=HamWAN name=Sector1-5 width=5 add band=5ghz-onlyn comment="Cell sites radiate this at 120 degrees (south-east)" frequency=5900 list=HamWAN name=Sector2-5 width=5 add band=5ghz-onlyn comment="Cell sites radiate this at 240 degrees (south-west)" frequency=5880 list=HamWAN name=Sector3-5 width=5 # New 10 MHz bandwidth in 10 MHz channel plan add band=5ghz-onlyn comment="Cell sites radiate this at 0 degrees (north)" frequency=5920 list=HamWAN name=Sector1-10 width=10 add band=5ghz-onlyn comment="Cell sites radiate this at 120 degrees (south-east)" frequency=5900 list=HamWAN name=Sector2-10 width=10 add band=5ghz-onlyn comment="Cell sites radiate this at 240 degrees (south-west)" frequency=5880 list=HamWAN name=Sector3-10 width=10
For optimal performance, some sectors will continue to use 5 MHz bandwidth on the new 10 MHz-plan center frequencies. Add all the above channels to ensure your modem will connect in this situation.
This change will be implemented in 7 days, August 9th. Please update your configuration before then for a smooth transition.
Tom KD7LXL
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
The transition to the new channel plan is nearly complete. Channels are spaced 20 MHz apart (on 5880, 5900, and 5920 MHz). For now they are still 5 MHz wide each. The deadline I gave was tomorrow. After verifying 100% of the clients attached to our various Sector 3's had the new channels programmed, I moved them to 5880 MHz. This immediately improved signal-to-noise ratio for clients connected to Sector 2--this is a good thing! I then moved on to Sector 2. All except Paine-S2 (Snohomish County EOC) have been moved to 5900 MHz. AE7Q was not connecting at 5900 MHz, so Dean must not have added the new channels yet. I'll leave Paine-S2 on 5905 MHz until Aug 9th as previously promised. The rest of the clients reconnected successfully on the new frequency. I was not able to access any of the clients attached to any Sector 1. Luckily this frequency is the same in both the old and the new channel plan, so no change is needed on the clients until we increase bandwidth. We would like to increase bandwidth to 10 MHz on CapitolPark-S1 as soon as possible, so if you have a client here, please make sure it has the new channels configured. Tom KD7LXL P.S. Haystack is online! On Sat, Aug 2, 2014 at 10:49 AM, Tom Hayward <esarfl@gmail.com> wrote:
We will be switching the network from the 5 MHz channel plan to the 10 MHz channel plan. This affects sectors and client nodes. Client nodes that are live on the network and have shared administration enabled will be updated automatically. Other clients will need to update their own channel list. With the following channels configured in your modem, it will scan for the new channel as soon as the old channel disappears:
/interface wireless channels # Current 5 MHz plan add band=5ghz-onlyn comment="Cell sites radiate this at 0 degrees (north)" frequency=5920 list=HamWAN name=Sector1 width=5 add band=5ghz-onlyn comment="Cell sites radiate this at 120 degrees (south-east)" frequency=5905 list=HamWAN name=Sector2 width=5 add band=5ghz-onlyn comment="Cell sites radiate this at 240 degrees (south-west)" frequency=5890 list=HamWAN name=Sector3 width=5 # New 5 MHz bandwidth in 10 MHz channel plan (first channel is identical to old 5 MHz plan) add band=5ghz-onlyn comment="Cell sites radiate this at 0 degrees (north)" frequency=5920 list=HamWAN name=Sector1-5 width=5 add band=5ghz-onlyn comment="Cell sites radiate this at 120 degrees (south-east)" frequency=5900 list=HamWAN name=Sector2-5 width=5 add band=5ghz-onlyn comment="Cell sites radiate this at 240 degrees (south-west)" frequency=5880 list=HamWAN name=Sector3-5 width=5 # New 10 MHz bandwidth in 10 MHz channel plan add band=5ghz-onlyn comment="Cell sites radiate this at 0 degrees (north)" frequency=5920 list=HamWAN name=Sector1-10 width=10 add band=5ghz-onlyn comment="Cell sites radiate this at 120 degrees (south-east)" frequency=5900 list=HamWAN name=Sector2-10 width=10 add band=5ghz-onlyn comment="Cell sites radiate this at 240 degrees (south-west)" frequency=5880 list=HamWAN name=Sector3-10 width=10
For optimal performance, some sectors will continue to use 5 MHz bandwidth on the new 10 MHz-plan center frequencies. Add all the above channels to ensure your modem will connect in this situation.
This change will be implemented in 7 days, August 9th. Please update your configuration before then for a smooth transition.
Tom KD7LXL
Dean added the new channels right after your prior eMail. The radio is not connecting on any frequency for reasons unrelated to your changes. On 2014-08-08 15:42, Tom Hayward wrote:
The transition to the new channel plan is nearly complete. Channels are spaced 20 MHz apart (on 5880, 5900, and 5920 MHz). For now they are still 5 MHz wide each.
The deadline I gave was tomorrow. After verifying 100% of the clients attached to our various Sector 3's had the new channels programmed, I moved them to 5880 MHz. This immediately improved signal-to-noise ratio for clients connected to Sector 2--this is a good thing!
I then moved on to Sector 2. All except Paine-S2 (Snohomish County EOC) have been moved to 5900 MHz. AE7Q was not connecting at 5900 MHz, so Dean must not have added the new channels yet. I'll leave Paine-S2 on 5905 MHz until Aug 9th as previously promised. The rest of the clients reconnected successfully on the new frequency.
I was not able to access any of the clients attached to any Sector 1. Luckily this frequency is the same in both the old and the new channel plan, so no change is needed on the clients until we increase bandwidth. We would like to increase bandwidth to 10 MHz on CapitolPark-S1 as soon as possible, so if you have a client here, please make sure it has the new channels configured.
Tom KD7LXL
P.S. Haystack is online!
On Sat, Aug 2, 2014 at 10:49 AM, Tom Hayward <esarfl@gmail.com> wrote:
We will be switching the network from the 5 MHz channel plan to the 10 MHz channel plan. This affects sectors and client nodes. Client nodes that are live on the network and have shared administration enabled will be updated automatically. Other clients will need to update their own channel list. With the following channels configured in your modem, it will scan for the new channel as soon as the old channel disappears:
/interface wireless channels # Current 5 MHz plan add band=5ghz-onlyn comment="Cell sites radiate this at 0 degrees (north)" frequency=5920 list=HamWAN name=Sector1 width=5 add band=5ghz-onlyn comment="Cell sites radiate this at 120 degrees (south-east)" frequency=5905 list=HamWAN name=Sector2 width=5 add band=5ghz-onlyn comment="Cell sites radiate this at 240 degrees (south-west)" frequency=5890 list=HamWAN name=Sector3 width=5 # New 5 MHz bandwidth in 10 MHz channel plan (first channel is identical to old 5 MHz plan) add band=5ghz-onlyn comment="Cell sites radiate this at 0 degrees (north)" frequency=5920 list=HamWAN name=Sector1-5 width=5 add band=5ghz-onlyn comment="Cell sites radiate this at 120 degrees (south-east)" frequency=5900 list=HamWAN name=Sector2-5 width=5 add band=5ghz-onlyn comment="Cell sites radiate this at 240 degrees (south-west)" frequency=5880 list=HamWAN name=Sector3-5 width=5 # New 10 MHz bandwidth in 10 MHz channel plan add band=5ghz-onlyn comment="Cell sites radiate this at 0 degrees (north)" frequency=5920 list=HamWAN name=Sector1-10 width=10 add band=5ghz-onlyn comment="Cell sites radiate this at 120 degrees (south-east)" frequency=5900 list=HamWAN name=Sector2-10 width=10 add band=5ghz-onlyn comment="Cell sites radiate this at 240 degrees (south-west)" frequency=5880 list=HamWAN name=Sector3-10 width=10
For optimal performance, some sectors will continue to use 5 MHz bandwidth on the new 10 MHz-plan center frequencies. Add all the above channels to ensure your modem will connect in this situation.
This change will be implemented in 7 days, August 9th. Please update your configuration before then for a smooth transition.
Tom KD7LXL
PSDR mailing list PSDR@hamwan.org http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org
On Fri, Aug 8, 2014 at 4:33 PM, Dean Gibson AE7Q <hamwan.stuff@ae7q.com> wrote:
Dean added the new channels right after your prior eMail. The radio is not connecting on any frequency for reasons unrelated to your changes.
It's connected now, but right on the fringe. Maybe it was just having trouble re-associating after the frequency change. I'll try it again and see what happens... Still didn't connect. Back on 5905 MHz again, it took quite a while to connect. It's really on the fringe. Have you tried taking a chainsaw to the neighbors' trees? Can you check that your scan-list is set to "HamWAN" (so it's actually using the channel list)? /interface wireless set [find] scan-list=HamWAN Tom KD7LXL
On 2014-08-08 16:48, Tom Hayward wrote:
It's connected now, but right on the fringe. Maybe it was just having trouble re-associating after the frequency change. I'll try it again and see what happens...
Still didn't connect.
Back on 5905 MHz again, it took quite a while to connect. It's really on the fringe. Have you tried taking a chainsaw to the neighbors' trees?
I thought my $20/month was supposed to cover that service ... (grin). Actually, I think the problem is summer growth, more than a mile away. I've got a good gap in the trees in my immediate neighborhood. I spent an hour out on the roof this past week, trying to improve the sighting (as opposed to the siting), without much improvement. Scott Honaker has a crank-up antenna (to 40ft) which I am seriously considering. In the meantime, I'm resigned to having an intermittent connection.
Can you check that your scan-list is set to "HamWAN" (so it's actually using the channel list)?
/interface wireless set [find] scan-list=HamWAN
Tom KD7LXL
Ack, that was the problem. I had set it up that way a week ago, but due to the marginal conditions, I subsequently had specified the specific channel (as suggested by Bart early on). I'm back to using the entire list. I take it that once the conversion is complete, I can remove the three channels with the 15MHz spacing?
On 2014-08-08 22:22, Dean Gibson AE7Q wrote:
On 2014-08-08 16:48, Tom Hayward wrote:
Can you check that your scan-list is set to "HamWAN" (so it's actually using the channel list)?
/interface wireless set [find] scan-list=HamWAN
Tom KD7LXL
Ack, that was the problem. I had set it up that way a week ago, but due to the marginal conditions, I subsequently had specified the specific channel (as suggested by Bart early on). I'm back to using the entire list.
I take it that once the conversion is complete, I can remove the three channels with the 15MHz spacing?
An FYI: It turns out that you can specify multiple scan-lists (and/or channel names) in the "/interface wireless set wlan1-gateway scan-list=..." command (but apparently not in the individual channel declarations). So, here's what I use: /interface wireless channels remove [find] channels add band=5ghz-onlyn width=5 frequency=5920 list=HamWAN-360-all name=HamWAN-360-old comment="Sector 1/360 (300-060)" channels add band=5ghz-onlyn width=5 frequency=5905 list=HamWAN-120-all name=HamWAN-120-old comment="Sector 2/120 (060-180)" channels add band=5ghz-onlyn width=5 frequency=5890 list=HamWAN-240-all name=HamWAN-240-old comment="Sector 3/240 (180-300)" channels add band=5ghz-onlyn width=5 frequency=5920 list=HamWAN-360-all name=HamWAN-360-5MHz comment="Sector 1/360 (300-060)" channels add band=5ghz-onlyn width=5 frequency=5900 list=HamWAN-120-all name=HamWAN-120-5MHz comment="Sector 2/120 (060-180)" channels add band=5ghz-onlyn width=5 frequency=5880 list=HamWAN-240-all name=HamWAN-240-5MHz comment="Sector 3/240 (180-300)" channels add band=5ghz-onlyn width=10 frequency=5920 list=HamWAN-360-all name=HamWAN-360-10MHz comment="Sector 1/360 (300-060)" channels add band=5ghz-onlyn width=10 frequency=5900 list=HamWAN-120-all name=HamWAN-120-10MHz comment="Sector 2/120 (060-180)" channels add band=5ghz-onlyn width=10 frequency=5880 list=HamWAN-240-all name=HamWAN-240-10MHz comment="Sector 3/240 (180-300)" set wlan1-gateway band=5ghz-onlyn wireless-protocol=nv2 frequency-mode=superchannel ssid=HamWAN radio-name="AE7Q/MillCreek-Paine" To scan everything: /interface wireless set wlan1-gateway scan-list=HamWAN-120-all,HamWAN-240-all,HamWAN-360-all To scan just my sector: /interface wireless set wlan1-gateway scan-list=HamWAN-120-all To scan just one channel: /interface wireless set wlan1-gateway scan-list=HamWAN-120-5MHz Note that there is a potential "gotcha" in the naming scheme: If, instead of using "HamWAN-120-all" as a list name, I used just "HamWAN-120" in the relevant places, I get an (unhelpful) error message from the "/interface wireless set wlan1-gateway scan-list=..."command. Apparently a list name cannot be a substring of a channel name (probably an incorrect use of the "strncmp" function). I'm doing this because I have a marginal connection, and once it is lost, it takes some time to scan all the channels for a signal.
On Sat, Aug 9, 2014 at 12:16 PM, Dean Gibson AE7Q <hamwan.stuff@ae7q.com> wrote:
An FYI:
It turns out that you can specify multiple scan-lists (and/or channel names) in the "/interface wireless set wlan1-gateway scan-list=..." command (but apparently not in the individual channel declarations). So, here's what I use:
/interface wireless channels remove [find] channels add band=5ghz-onlyn width=5 frequency=5920 list=HamWAN-360-all name=HamWAN-360-old comment="Sector 1/360 (300-060)" channels add band=5ghz-onlyn width=5 frequency=5905 list=HamWAN-120-all name=HamWAN-120-old comment="Sector 2/120 (060-180)" channels add band=5ghz-onlyn width=5 frequency=5890 list=HamWAN-240-all name=HamWAN-240-old comment="Sector 3/240 (180-300)" channels add band=5ghz-onlyn width=5 frequency=5920 list=HamWAN-360-all name=HamWAN-360-5MHz comment="Sector 1/360 (300-060)" channels add band=5ghz-onlyn width=5 frequency=5900 list=HamWAN-120-all name=HamWAN-120-5MHz comment="Sector 2/120 (060-180)" channels add band=5ghz-onlyn width=5 frequency=5880 list=HamWAN-240-all name=HamWAN-240-5MHz comment="Sector 3/240 (180-300)" channels add band=5ghz-onlyn width=10 frequency=5920 list=HamWAN-360-all name=HamWAN-360-10MHz comment="Sector 1/360 (300-060)" channels add band=5ghz-onlyn width=10 frequency=5900 list=HamWAN-120-all name=HamWAN-120-10MHz comment="Sector 2/120 (060-180)" channels add band=5ghz-onlyn width=10 frequency=5880 list=HamWAN-240-all name=HamWAN-240-10MHz comment="Sector 3/240 (180-300)" set wlan1-gateway band=5ghz-onlyn wireless-protocol=nv2 frequency-mode=superchannel ssid=HamWAN radio-name="AE7Q/MillCreek-Paine"
To scan everything:
/interface wireless set wlan1-gateway scan-list=HamWAN-120-all,HamWAN-240-all,HamWAN-360-all
To scan just my sector:
/interface wireless set wlan1-gateway scan-list=HamWAN-120-all
To scan just one channel:
/interface wireless set wlan1-gateway scan-list=HamWAN-120-5MHz
Dean, Thanks. I like this technique. Tom
participants (3)
-
Bart Kus -
Dean Gibson AE7Q -
Tom Hayward