Recent Updates and Important News Flashes...
This section will be reserved on the web site for any important late breaking news or announcements that would have a direct bearing on ARES members in general and Renfrew County ARES members as a group. I will date the items as of the posting date. Some items may remain posted even after their respective operational dates.
The IRLP node 2520 is back on the air from it's new location in the Petawawa Civic Centre. Problems with the Civic Centre's router, cabling from the radio to the computer and changes in squelch settings etc were resolved and the node seems to be working well. It can now be connected to the Ontario Emergency Reflector 9035 for ARES nets.
Thur. Oct 29, 2009
The web page for the Renfrew County Amateur Club has been moved to this ARES site. The link is in the list of links on the left pane.
The IRLP system is presently in it's new home at the Petawawa Civic Centre. There are problems with the internet connections that we hope can be resolved before too long.
An APRS digi has been installed at VA3RBW (VA3RBW-3). It is extending the APRS coverage up the valley toward Bisset Creek. It comunicates through VA2REH to the rest of the network.
Wed. May 13, 2008
VE3UCR is back on the air at Foymount. Freq. is 145.430-, PL tone out is 114.8. There is no tone input requirement. The repeater can be linked to VE3NRR in Pembroke with CTCSS code 521 (unlink 520). So far, the range appears to be very good.
A packet node (X1J4) named FOY was also installed at Foymount. Freq. is 145.010. Call is VE3UCR-1. So far, it's performance has been disappointing. The ARX-2B antenna is mounted near the tower and just above the building. Vertical separation is being used to isolate it from the input to the voice repeater on 144.830. The antenna for VE3UCR voice is at about 420 ft on the tower. The station will be checked at a later date (when the bugs have gone!) to look for problems.Bob VE3YX
Sunday, September 30, 2007 -- IRLP Update.
The short version ....
After many unsuccessful attempts and many late hours trying to put the Pembroke IRLP node back on the air at the new location on Joe Street (space and internet connection made available by club member John - VA3AJT) the node has been re-installed in it's original location at the shack of VE3PL and is once again fully operational.
For those who want the nitty gritty facts ... read on.
Although the installation at Joe Street should have been a straight forward re-locate and energize of the IRLP node, this was not the case. After installation and power up, I was indeed dismayed to find that we were not connecting to the internet. Several attempts later (and many many days due to limited time available to work on the system) and some serious re-routing and re-configuring of the host network the internet was finally available to the IRLP box. This should have been the end of the troubles right?? Wrong...
The irlp-troubleshoot script clearly indicated that port 15425, a necessary port for the IRLP function, was not allowing any incoming TCP traffic. The usual re-configuration of the D-Link DI-604 router to allow port traffic was completed, but to no avail. The incoming TCP connection on 15425 was blocked, and that was that. Help files on the internet indicated that perhaps the ISP was blocking the port. A phone call was made, and we were told that the ISP was NOT blocking any ports, so our troubles may lie elsewhere.
As with any situation, two heads are often better than one, and with the help of Ron (VA3KRY) we began to troubleshoot the network. After exchanging the existing router for one that Ron had (Linksys) and setting up the port forwarding as required, we still had the same problem. The IRLP troubleshooting script reported that the port was still blocked. Again, we had full access to the internet on port 80, allowing us to surf the net, and the required UDP ports were being reported as fully functional.
The next obvious thing was to remove the router from the equation entirely and attempt to operate IRLP directly through Bell's High Speed MoDem. It was necessary to once again reconfigure the IRLP network setup to allow this new configuration via the net addressing on the IRLP box. Upon completion of these changes we had internet capability as before, but still could not receive any input on the incoming side of the port in question.
One thing that we did realize during this last exercise was that the MoDem had assigned a new DHCP address to our laptop, which we had on site and were using as a second access to the internet allowing us to surf the net for troubleshooting purposes while addressing the issues with the IRLP Linux box. This indicated to us that the MoDem itself housed a DHCP server. The next realization is then if it is assigning a dynamic address to our host, it is a firewall of sorts.
Ron set up his laptop as a server and connected directly to the high speed MoDem. I attempted to connect to his server from an outside line on both port 80 and also the port in question, and could not connect either way. When Ron did the same experiment with his laptop from his home QTH, I was able to connect immediately to his server from my home QTH.
I packed up the IRLP box and cabling and all the required paraphernalia and brought it back to my home QTH were it had resided previously since May 2002. I plugged it in, hooked it up, set the IRLP networking address and we were on the air... just like that.
This certainly implies that the MoDem is the culprit in all of this, OR, the ISP is indeed blocking the port. I suspect that the MoDem is at fault.
Our intention at this point in time is to leave the IRLP functional at the current location (home of VE3PL) and sort out the MoDem issue at the Joe Street location. I will attempt to keep club members posted on the progress on this page.
I thank all club members for their patience, and wish all best '73.
de Les VE3PL