<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Dylan,</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Were you able to access the Pi for programming the radios? </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Thanks</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Kenny</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jun 7, 2020 at 10:04 AM Dylan Ambauen <<a href="mailto:dylan@ambauen.com">dylan@ambauen.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Sounds like a long day Bart. The local LAN has been a dream up there for years. <div><br><div>You put the DMR router on the routing protocol now too, great.<div><div>And the old SXT5 link to Baldi sector is gone: <span style="color:rgb(51,51,51);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14px"><a href="http://wlan1.baldi.af7pr-baldi.hamwan.net" target="_blank">wlan1.baldi.af7pr-baldi.hamwan.net</a> (44.24.240.219) </span><span style="color:rgb(51,51,51);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14px"><a href="http://ether1.baldi.af7pr-baldi.hamwan.net" target="_blank">ether1.baldi.af7pr-baldi.hamwan.net</a> (44.25.137.34)</span></div><div><br></div><div>Mike, Rob, Rod, the local DHCP server for <span style="font-variant-ligatures:no-common-ligatures;background-color:rgba(12,12,11,0.88);color:rgb(242,242,242);font-family:Monaco;font-size:10px"><a href="http://44.25.137.33/28" target="_blank">44.25.137.33/28</a></span> was on the link radio.</div><div>Additionally, the switch ports are now bridged to the local LAN. Devices should be up, but will have new ip addresses on the Baldi LAN, instead of in <a href="http://44.25.137.22/38" target="_blank">44.25.137.22/38</a></div><div>Bart says the VHF repeater didnt pull a DHCP address from Baldi LAN, it was being used as a master for a while, so it's config required a static ip address. I put theVHR repeaters switch port8 into the bridge for .33/28, now called Building2.</div><div>And <span style="color:rgb(51,51,51);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14px"><a href="http://vhf.af7pr-baldi.hamwan.net" target="_blank">vhf.af7pr-baldi.hamwan.net</a> is now back online.</span></div><div><font color="#333333" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span style="font-size:14px">There is very little necessity in maintaining <a href="http://44.25.137.33/28" target="_blank">44.25.137.33/28</a> address space anymore, there is plenty of space on baldi LAN. </span></font><span style="font-size:14px;color:rgb(51,51,51);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif">Perhaps there are some reasons I'm not anticipating?</span></div><div><font color="#333333" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span style="font-size:14px">We can still use that block, moving the old devices back to how they were numbered. Otherwise, we can find the new addresses and update DNS.</span></font></div><div><div><div dir="ltr"><br>---<br>Dylan Ambauen<br>360-850-1200</div></div><br></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jun 6, 2020 at 11:59 PM Bart Kus <<a href="mailto:me@bartk.us" target="_blank">me@bartk.us</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
We deployed stuff @ Baldi today. First, the good news:<br>
<br>
1) We installed the cable between the buildings, and got all of them on <br>
the gigabit LAN.<br>
2) The 24-port switch for the middle building didn't arrive on time, so <br>
we're using the full switch that was there already.<br>
3) We aligned the Beacon.Baldi dish and managed to get another 10dB of <br>
signal out of it now that it's focused solely on Beacon.<br>
4) We got access points deployed into all the buildings.<br>
5) We got the link to CampMurray working at last. The 3ft dish was <br>
discovered to be damaged and had to be replaced with a 2ft from my <br>
personal inventory. This will need an RF Armor shield, and an <br>
additional expense report for the Baldi deploy budget to cover the cost <br>
of the dish itself.<br>
<br>
Now for not great news:<br>
<br>
1) The Ethernet link between the northernmost building and the new <br>
Rattlesnake.Baldi dish seems to be faulty. It was raining hard when we <br>
were installing this, so maybe there's water in the connector. It's also <br>
deployed pretty close to lots of VHF/UHF antennas, so maybe the RFI is <br>
killing the Ethernet. We need to go back on a dry day, hopefully with a <br>
cable analyzer, and examine the situation. If it's VHF/UHF RFI, then <br>
we'll need to run fiber to the modem. I have disabled the power to the <br>
dish for now, on the theory that water is causing PoE arcing at the <br>
modem contacts and we don't want that electrolysis process to continue. <br>
Power draw to the modem is not unusual, about 3.2W, although it has been <br>
observed to be quite variable at times, from 3W to 4W.<br>
<br>
2) The AP in the northernmost building appears to have really bad <br>
performance. I had a hard time pinging it over WiFi from within the <br>
shack. Had to resort to using wired Ethernet to get any packets moving <br>
and work done. I've no idea the cause of this. Perhaps a spectrum scan <br>
is required.<br>
<br>
3) The VHF DMR up there appears to have been static-IP configured and <br>
didn't migrate properly. We'll need some follow-up remote work to <br>
re-program the repeater for DHCP.<br>
<br>
I think that's everything noteworthy.<br>
<br>
--Bart<br>
<br>
_______________________________________________<br>
PSDR mailing list<br>
<a href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a><br>
<a href="http://mail.hamwan.net/mailman/listinfo/psdr" rel="noreferrer" target="_blank">http://mail.hamwan.net/mailman/listinfo/psdr</a><br>
</blockquote></div>
_______________________________________________<br>
PSDR mailing list<br>
<a href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a><br>
<a href="http://mail.hamwan.net/mailman/listinfo/psdr" rel="noreferrer" target="_blank">http://mail.hamwan.net/mailman/listinfo/psdr</a><br>
</blockquote></div>