Date   

Re: [amsat-bb] Dieter Schliemann, KX4Y SK

Nate Duehr <nate@...>
 

Dieter will be missed in the IRLP community also.

(Sending a copy of your announcement to the IRLP list, Frank. Thank you.)

Nate Duehr, WY0X

-----Original Message-----
From: amsat-bb-bounces@... [mailto:amsat-bb-bounces@...] On
Behalf Of Frank H. Bauer
Sent: Tuesday, February 10, 2009 11:16 AM
To: amsat-bb@...
Subject: [amsat-bb] Dieter Schliemann, KX4Y SK

All,

It is with great sadness that I announce the passing of Dieter Schliemann,
KX4Y.

Those that knew Dieter recognized that he was a "class act"---a great
gentleman and colleague who will be sorely missed by all. Dieter was
instrumental in leading and supporting many key activities in AMSAT and on
the ARISS program.

For ARISS, Dieter led the school contact IRLP/Echolink initiative. Through
this amateur radio VOIP system, Dieter and his team substantially extended
our reach of the school contacts. And through his efforts, tens of
thousands of school students and ham radio operators, world-wide, could
listen to other school contacts, enhancing education and giving all a better
understanding of what it is like to live and work on ISS. Dieter's
diplomacy, teambuilding skills and attention to the details were impeccable
and were well respected within the team. He rose to the challenge when I
asked him to lead the IRLP/Echolink team. At the time, there were strong,
divergent opinions on the use of IRLP and Echolink on ARISS. He
singlehandedly developed a cohesive team that is producing great results and
are enjoying working together.

Over the past couple of years, Dieter fought a long and courageous battle
with Cancer. A month ago, all of us thought he was on the road to recovery.
Unfortunately, that did not come to pass. Through it all, Dieter remained
the gentle, caring person that we all have grown to love. And during his
illness, he remained dedicated to his AMSAT and ARISS causes and
responsibilities. When he received the surprising news from the doctors
that he had only two weeks to live and despite being weak from a long
hospitalization, Dieter got on the e-mail and worked a transition plan to
ensure the IRLP/Echolink capabilities on ARISS continues. What a great,
compassionate, loving human being!

I first met Dieter behind the AMSAT Booth at Dayton, where he was one of the
mainstay individuals supporting AMSAT efforts at the Hamvention. Reflecting
on Dieter's support to AMSAT, AMSAT Board Member Gould Smith, WA4SXM,
stated, "Two years ago Dieter told me that the only reason he came to Dayton
was to work in the AMSAT booth and to talk with people about AMSAT". And he
supported AMSAT in many other ways, including his efforts as an Area
Coordinator, where he mentored a countless number of satellite enthusiasts.
We are eternally grateful for all Dieter has done for AMSAT and the ARISS
program. And will miss him dearly.

On behalf of the ARISS and AMSAT teams, we wish to express our deepest
sympathy to the Schliemann family and friends. Especially his wife Tina and
his good friend Ron Arsenault, N1NYR, who helped Dieter and the Schliemann
family throughout Dieter's long illness.

Frank H. Bauer, KA3HDO
AMSAT-NA V.P. for Human Spaceflight Programs
ARISS International Chairman
_______________________________________________
Sent via AMSAT-BB@.... Opinions expressed are those of the author.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb


Re: Node 3362, still trying to get it back on line.

wayne chapman <lk_side@...>
 

Hello Chad,
This is an interesting concept, but I am not sure I follow. If I set a static IP, the one Hughes has designated to the modem and in turn shows up on windows IPconfig? then just as Jason said use the router DMZ feature to forward all to the router address?
I will give this a try, but almost sure I have in the past but so many attempts have caused memory failure. I have copied what I sent to Jason, but may give this a try first.

Hello Jason,
Thanks again for your suggestions, the router is a WT54G ver 6, but last night while trying to sleep I had the same idea as you, connect the node directly to the modem, that did not work at all, could not get correct config on the node...So right or wrong I am going to make one more attempt to get Hughes to admit they have changed my service and if they can't get it back to the way it was I will cancel my service with them, they have done nothing but try to scam me and I think they are nothing more than a pack of liars!
I will post my results. The other problem is except for a possible alternative company by the name of Bluesky, Hughes is the only Internet service in my part of the country.
Thank You Again,
Wayne

----- Original Message -----
From: Chad Taylor
To: irlp@...
Sent: Monday, February 09, 2009 10:22 PM
Subject: [irlp] Re: Node 3362, still trying to get it back on line.


--- In irlp@..., Jason Stahls <jason@...> wrote:
>
> wayne chapman wrote:
> > Sorry Jason,
> > I tried what you said and had no success, Hughes swares all ports
are open, I have to assume both routers are no good, but if that is
the case I will never buy another Linksys piece of equipment.
> > I hate to spend the money in these times to , only find out I was
wrong but I may have to.
> > Thank you for your time and suggestion, it was much appreciated.
>
> Well I honestly don't think it's Linksys as a whole, possibly a
buggy
> firmware or something, but portforwarding is a fairly simplistic
task.
> What is the model of the router/firmware version? Have you tried
> putting the IRLP node on the WAN side aka direct to the modem? On
the
> upside, a lot of routers now a days you can install 3rd party FW
in :)
>
> --
> Jason Stahls
> VA3JSS
>

Double check the hughes modem. Satellite service is very picky at
times and when they do a force update of the internal firmware of the
Satellite receiver then you often loose programming. First be sure
that the settings are passing all ports and traffic to the Router. I
would not in a million years think that two routers are to blame. I
would infact believe that the Hughes receiver is no longer passing
the appropriate ports thru to the router! You could even set a
static IP on the router and set that IP in the Hughes receiver as the
DMZ IP addy. That will force all unknown ports to be sent to the
router. This is the best solution as you can then use the router to
manage the ports, forwarding, IP's etc. Hope that helps...


Re: Node 3362, still trying to get it back on line.

wayne chapman <lk_side@...>
 

Hello Jason,
Thanks again for your suggestions, the router is a WT54G ver 6, but last night while trying to sleep I had the same idea as you, connect the node directly to the modem, that did not work at all, could not get correct config on the node...So right or wrong I am going to make one more attempt to get Hughes to admit they have changed my service and if they can't get it back to the way it was I will cancel my service with them, they have done nothing but try to scam me and I think they are nothing more than a pack of liars!
I will post my results. The other problem is except for a possible alternative company by the name of Bluesky, Hughes is the only Internet service in my part of the country.
Thank You Again,
Wayne

----- Original Message -----
From: Jason Stahls
To: irlp@...
Sent: Monday, February 09, 2009 5:58 PM
Subject: Re: [irlp] Node 3362, still trying to get it back on line.


wayne chapman wrote:
> Sorry Jason,
> I tried what you said and had no success, Hughes swares all ports are open, I have to assume both routers are no good, but if that is the case I will never buy another Linksys piece of equipment.
> I hate to spend the money in these times to , only find out I was wrong but I may have to.
> Thank you for your time and suggestion, it was much appreciated.

Well I honestly don't think it's Linksys as a whole, possibly a buggy
firmware or something, but portforwarding is a fairly simplistic task.
What is the model of the router/firmware version? Have you tried
putting the IRLP node on the WAN side aka direct to the modem? On the
upside, a lot of routers now a days you can install 3rd party FW in :)

--
Jason Stahls
VA3JSS


Re: COS on an Alinco DR235T

Marshall Oldham
 

Chad,

Make sure that you have the COS jumper set to the low on the IRLP board.
Make sure that you do NOT have the radio in Data mode.
_ _
You should not see _||_||_ in the upper right corner of your Alinco LCD display.


Marshall - ke6pcv

-----Original Message-----
From: irlp@... [mailto:irlp@...] On Behalf Of Chad Taylor
Sent: Monday, February 09, 2009 9:11 PM
To: irlp@...
Subject: [irlp] COS on an Alinco DR235T

Hello everyone,
What could possibly be causing the problem of there being no COS
detection on the IRLP Board? The cables are premade and I have checked
all the solder points in the cable, the radio is set to [T] [SQ] with
100hz Tones. Is there something that I am missing? Thanks to everyone
for any help...



------------------------------------

--- IRLP-Owners YahooGroups List ---Yahoo! Groups Links











































































































































































Re: Node 3362, still trying to get it back on line.

Chad Taylor <chadrt78@...>
 

--- In irlp@..., Jason Stahls <jason@...> wrote:

wayne chapman wrote:
Sorry Jason,
I tried what you said and had no success, Hughes swares all ports
are open, I have to assume both routers are no good, but if that is
the case I will never buy another Linksys piece of equipment.
I hate to spend the money in these times to , only find out I was
wrong but I may have to.
Thank you for your time and suggestion, it was much appreciated.
Well I honestly don't think it's Linksys as a whole, possibly a
buggy
firmware or something, but portforwarding is a fairly simplistic
task.
What is the model of the router/firmware version? Have you tried
putting the IRLP node on the WAN side aka direct to the modem? On
the
upside, a lot of routers now a days you can install 3rd party FW
in :)

--
Jason Stahls
VA3JSS
Double check the hughes modem. Satellite service is very picky at
times and when they do a force update of the internal firmware of the
Satellite receiver then you often loose programming. First be sure
that the settings are passing all ports and traffic to the Router. I
would not in a million years think that two routers are to blame. I
would infact believe that the Hughes receiver is no longer passing
the appropriate ports thru to the router! You could even set a
static IP on the router and set that IP in the Hughes receiver as the
DMZ IP addy. That will force all unknown ports to be sent to the
router. This is the best solution as you can then use the router to
manage the ports, forwarding, IP's etc. Hope that helps...


COS on an Alinco DR235T

Chad Taylor <chadrt78@...>
 

Hello everyone,
What could possibly be causing the problem of there being no COS
detection on the IRLP Board? The cables are premade and I have checked
all the solder points in the cable, the radio is set to [T] [SQ] with
100hz Tones. Is there something that I am missing? Thanks to everyone
for any help...


Re: Node 3362, still trying to get it back on line.

Jason Stahls
 

wayne chapman wrote:
Sorry Jason,
I tried what you said and had no success, Hughes swares all ports are open, I have to assume both routers are no good, but if that is the case I will never buy another Linksys piece of equipment.
I hate to spend the money in these times to , only find out I was wrong but I may have to.
Thank you for your time and suggestion, it was much appreciated.
Well I honestly don't think it's Linksys as a whole, possibly a buggy firmware or something, but portforwarding is a fairly simplistic task. What is the model of the router/firmware version? Have you tried putting the IRLP node on the WAN side aka direct to the modem? On the upside, a lot of routers now a days you can install 3rd party FW in :)

--
Jason Stahls
VA3JSS


Re: Node 3362, still trying to get it back on line.

Jim WW4M
 

If your Hughes service is DSL I guess it's possible they reprogrammed
your DSL router and it's no longer in bridge mode, which would
effectively block the inbound ports without them actually actively
blocking any ports.

Jim WW4M

--- In irlp@..., "wayne chapman" <lk_side@...> wrote:

Sorry Jason,
I tried what you said and had no success, Hughes swares all ports
are open, I have to assume both routers are no good, but if that is
the case I will never buy another Linksys piece of equipment.
I hate to spend the money in these times to , only find out I was
wrong but I may have to.
Thank you for your time and suggestion, it was much appreciated.
Wayne

----- Original Message -----
From: Jason Stahls
To: irlp@...
Sent: Sunday, February 08, 2009 10:34 PM
Subject: Re: [irlp] Node 3362, still trying to get it back on line.


doberman20022003 wrote:
> Hopefully Some one has had a problem like this and can let me
know what
> they did to get back on line. I have been on this problem since
the 8th
> of January when Hughes net changed my IP address and just
destroyed my
> router configuration. I run a static port off of the Hughes HN7000S
> modem, into a linksys router, which up till now all was great for
> almost 2 years. Heres my question, I have got all the IRLP tests to
> pass except test #2, now the only ports "Not forwarding
correctly are
> 2073-2094" all the other ports are operating correctly. To make
matters
> worse I have 2 routers and both will not forward the 2073-2094
ports
> corectly, is it worth getting another router and trying it? or do I
> still have the IRLP configuration wrong? The biggest problem I
have is
> linksys has a name for a certain IP and Hughes has a name for it
and
> then Windows has another name for it, how does one figure out the
> bottom line when it comes to prgraming the IRLP in the 'root'
> command "netconfig"?

Well, first off get ahold of your ISP and drill them as to if they
are
doing any port blocking since you have two routers that give the same
problem. Next, did you forward UDP or TCP for those ports? Now, for
netconfig, use a static configuration where you have to input the
info
instead of DHCP just so that the address doesn't change in the
future.
I'd say set the IP to be x.x.x.2 where x.x.x is the class-c range
your
router is using on the LAN side, the router is probably x.x.x.1 so
set
the default gateway and DNS servers to be x.x.x.1, and subnet mask of
255.255.255.0 that's all you should have to do on the IRLP box.
Then in
your router either a) put .2 in the DMZ, or forward the ports you
need
as per the IRLP install guide to .2

Hope that reads ok....

--
Jason Stahls
VA3JSS



[Non-text portions of this message have been removed]


Re: Node 3362, still trying to get it back on line.

wayne chapman <lk_side@...>
 

Sorry Jason,
I tried what you said and had no success, Hughes swares all ports are open, I have to assume both routers are no good, but if that is the case I will never buy another Linksys piece of equipment.
I hate to spend the money in these times to , only find out I was wrong but I may have to.
Thank you for your time and suggestion, it was much appreciated.
Wayne

----- Original Message -----
From: Jason Stahls
To: irlp@...
Sent: Sunday, February 08, 2009 10:34 PM
Subject: Re: [irlp] Node 3362, still trying to get it back on line.


doberman20022003 wrote:
> Hopefully Some one has had a problem like this and can let me know what
> they did to get back on line. I have been on this problem since the 8th
> of January when Hughes net changed my IP address and just destroyed my
> router configuration. I run a static port off of the Hughes HN7000S
> modem, into a linksys router, which up till now all was great for
> almost 2 years. Heres my question, I have got all the IRLP tests to
> pass except test #2, now the only ports "Not forwarding correctly are
> 2073-2094" all the other ports are operating correctly. To make matters
> worse I have 2 routers and both will not forward the 2073-2094 ports
> corectly, is it worth getting another router and trying it? or do I
> still have the IRLP configuration wrong? The biggest problem I have is
> linksys has a name for a certain IP and Hughes has a name for it and
> then Windows has another name for it, how does one figure out the
> bottom line when it comes to prgraming the IRLP in the 'root'
> command "netconfig"?

Well, first off get ahold of your ISP and drill them as to if they are
doing any port blocking since you have two routers that give the same
problem. Next, did you forward UDP or TCP for those ports? Now, for
netconfig, use a static configuration where you have to input the info
instead of DHCP just so that the address doesn't change in the future.
I'd say set the IP to be x.x.x.2 where x.x.x is the class-c range your
router is using on the LAN side, the router is probably x.x.x.1 so set
the default gateway and DNS servers to be x.x.x.1, and subnet mask of
255.255.255.0 that's all you should have to do on the IRLP box. Then in
your router either a) put .2 in the DMZ, or forward the ports you need
as per the IRLP install guide to .2

Hope that reads ok....

--
Jason Stahls
VA3JSS


Re: check out this antenna problem

Mike Morris WA6ILQ <wa6ilq@...>
 

Naah. Roast woodpecker.

Mike

At 09:38 PM 02/08/09, you wrote:

I thought it was chestnuts that were supposed to be roasted.?.

Rick WA6NHC

www.HappyMoosePhoto.com

Wildlife and scenic images

_____

From: <mailto:irlp%40yahoogroups.com>irlp@...
[mailto:irlp@...] On Behalf Of Kent
Roberts
Sent: Sunday, February 08, 2009 10:20 AM
To: <mailto:irlp%40yahoogroups.com>irlp@...
Subject: [irlp] check out this antenna problem

Though this was worth sharing, this is about 25 miles from where Nate
and I live.

<http://home.>http://home. <http://home.pacbell.net/dredmo1/acorns/acorns.wmv>
pacbell.net/dredmo1/acorns/acorns.wmv




Re: check out this antenna problem

Rick Bates <HappyMoosePhoto@...>
 

I thought it was chestnuts that were supposed to be roasted.?.

Rick WA6NHC

www.HappyMoosePhoto.com

Wildlife and scenic images

_____

From: irlp@... [mailto:irlp@...] On Behalf Of Kent
Roberts
Sent: Sunday, February 08, 2009 10:20 AM
To: irlp@...
Subject: [irlp] check out this antenna problem



Though this was worth sharing, this is about 25 miles from where Nate
and I live.

http://home. <http://home.pacbell.net/dredmo1/acorns/acorns.wmv>
pacbell.net/dredmo1/acorns/acorns.wmv


Re: forgotten password

Gary - AG0N
 

On Mon, 09 Feb 2009 04:33:43 -0000, va3rzs wrote:


Thank you .. I will write down the PW this time :)

I shall try Monday and let you know how it went !

Have a look at my web page if you haven't. I don't know if there is
anything there you might not already have or not.
http://garymcduffie.com/irlp/password.html#passwordrecovery

73, Gary
--
http: //garymcduffie .com
3055: http: // garymcduffie.com /irlp/ 3055
NodeOp Help Page: http:// garymcduffie. com /irlp


Re: Node 3362, still trying to get it back on line.

Jason Stahls
 

doberman20022003 wrote:
Hopefully Some one has had a problem like this and can let me know what they did to get back on line. I have been on this problem since the 8th of January when Hughes net changed my IP address and just destroyed my router configuration. I run a static port off of the Hughes HN7000S modem, into a linksys router, which up till now all was great for almost 2 years. Heres my question, I have got all the IRLP tests to pass except test #2, now the only ports "Not forwarding correctly are 2073-2094" all the other ports are operating correctly. To make matters worse I have 2 routers and both will not forward the 2073-2094 ports corectly, is it worth getting another router and trying it? or do I still have the IRLP configuration wrong? The biggest problem I have is linksys has a name for a certain IP and Hughes has a name for it and then Windows has another name for it, how does one figure out the bottom line when it comes to prgraming the IRLP in the 'root' command "netconfig"?
Well, first off get ahold of your ISP and drill them as to if they are doing any port blocking since you have two routers that give the same problem. Next, did you forward UDP or TCP for those ports? Now, for netconfig, use a static configuration where you have to input the info instead of DHCP just so that the address doesn't change in the future. I'd say set the IP to be x.x.x.2 where x.x.x is the class-c range your router is using on the LAN side, the router is probably x.x.x.1 so set the default gateway and DNS servers to be x.x.x.1, and subnet mask of 255.255.255.0 that's all you should have to do on the IRLP box. Then in your router either a) put .2 in the DMZ, or forward the ports you need as per the IRLP install guide to .2

Hope that reads ok....

--
Jason Stahls
VA3JSS


Node 3362, still trying to get it back on line.

doberman20022003 <lk_side@...>
 

Hopefully Some one has had a problem like this and can let me know what
they did to get back on line. I have been on this problem since the 8th
of January when Hughes net changed my IP address and just destroyed my
router configuration. I run a static port off of the Hughes HN7000S
modem, into a linksys router, which up till now all was great for
almost 2 years. Heres my question, I have got all the IRLP tests to
pass except test #2, now the only ports "Not forwarding correctly are
2073-2094" all the other ports are operating correctly. To make matters
worse I have 2 routers and both will not forward the 2073-2094 ports
corectly, is it worth getting another router and trying it? or do I
still have the IRLP configuration wrong? The biggest problem I have is
linksys has a name for a certain IP and Hughes has a name for it and
then Windows has another name for it, how does one figure out the
bottom line when it comes to prgraming the IRLP in the 'root'
command "netconfig"?
Please Help if you can,
Wayne


Re: forgotten password

Rick Szajkowski
 

--- In irlp@..., Jason Stahls <jason@...> wrote:

va3rzs wrote:
--- In irlp@..., Jason Stahls <jason@> wrote:

va3rzs wrote:

Hello to the group

I have forgotten the root password
I do know the repeater password

is there a way to get to the root password from repeater ?

Its been a while from we upgraded to the new OS
No you can't recover the root password from repeater, you would
need to
know the root password to change it. What you need to do is boot
into
single user mode, here's the docs for CentOS 4.7


http://www.centos.org/docs/5/html/Installation_Guide-en-US/s1-rescuemode-booting-single.html

--
Jason Stahls
VA3JSS

ok I read the doc .. then what ???
Change the password :) Sorry I assumed too much, the command is passwd
it's used for changing passwords. When booted to single-user mode you
will be loged in by default as root and passwd will not ask for the
original password, it will just ask for a new password and set it for
you. You can then reboot and all should be good.

--
Jason Stahls
VA3JSS
Thank you .. I will write down the PW this time :)

I shall try Monday and let you know how it went !


Re: forgotten password

Jason Stahls
 

va3rzs wrote:
--- In irlp@..., Jason Stahls <jason@...> wrote:

va3rzs wrote:

Hello to the group

I have forgotten the root password
I do know the repeater password
is there a way to get to the root password from repeater ?

Its been a while from we upgraded to the new OS
No you can't recover the root password from repeater, you would need to know the root password to change it. What you need to do is boot into single user mode, here's the docs for CentOS 4.7


http://www.centos.org/docs/5/html/Installation_Guide-en-US/s1-rescuemode-booting-single.html

--
Jason Stahls
VA3JSS

ok I read the doc .. then what ???
Change the password :) Sorry I assumed too much, the command is passwd it's used for changing passwords. When booted to single-user mode you will be loged in by default as root and passwd will not ask for the original password, it will just ask for a new password and set it for you. You can then reboot and all should be good.

--
Jason Stahls
VA3JSS


Re: forgotten password

Rick Szajkowski
 

--- In irlp@..., Jason Stahls <jason@...> wrote:

va3rzs wrote:
Hello to the group

I have forgotten the root password
I do know the repeater password

is there a way to get to the root password from repeater ?

Its been a while from we upgraded to the new OS
No you can't recover the root password from repeater, you would need to
know the root password to change it. What you need to do is boot into
single user mode, here's the docs for CentOS 4.7

http://www.centos.org/docs/5/html/Installation_Guide-en-US/s1-rescuemode-booting-single.html

--
Jason Stahls
VA3JSS
ok I read the doc .. then what ???


Re: forgotten password

Jason Stahls
 

va3rzs wrote:
Hello to the group

I have forgotten the root password
I do know the repeater password
is there a way to get to the root password from repeater ?

Its been a while from we upgraded to the new OS
No you can't recover the root password from repeater, you would need to know the root password to change it. What you need to do is boot into single user mode, here's the docs for CentOS 4.7

http://www.centos.org/docs/5/html/Installation_Guide-en-US/s1-rescuemode-booting-single.html

--
Jason Stahls
VA3JSS


forgotten password

Rick Szajkowski
 

Hello to the group

I have forgotten the root password
I do know the repeater password

is there a way to get to the root password from repeater ?

Its been a while from we upgraded to the new OS

Thanks for any and all help

Rick
Node 2120


File - 2-Week Reminder

irlp@...
 

This Yahoolist was created for node owners to gather and share technical information and discuss the operation of their IRLP nodes. It has also become an official means for the IRLP Project Team to send out important announcements to node owners.

**NEW** SPAM SPAM SPAM
Yes - the occassional SPAM message will make it to the list. P L E A S E - DO NOT respond, comment or start a thread about same. This rule is critical to keeping sanity on the list.

SEARCH FOR TOPICS BEFORE POSTING THEM
Yahoogroups has a very nice Advanced Search feature which allows you to search the whole archive of messages in one search. Please type some keywords from your question in the "Message Body" and "Message Subject" to look for answers before asking them in the group. Thank you.

NODE PASSWORDS
Several nodes have been hacked as a result of brute force attacks. In each case these breaches were a result of password that was a common persons name or callsign. A brute force attack is one in which all possible words of a certain length are attempted until a correct one is found. Crack dictionaries which contain a list of common words and phrases can easily be found on the Internet. Many crack dictionaries contain entire scripts to popular movies and entire sets of song lyrics - so be warned.

A strong password is as long as possible. Always use at least six characters in your password. The longer the password, the more difficult it is to attack with a brute-force search.

STRONG PASSWORDS...
- Have both upper and lower case letters.
- Have digits and/or punctuation characters as well as letters.
- Are easy to remember, so they do not have to be written down.
- Are AT LEAST six or more characters long.

YOUR SSH PORT
Most attempts to compromise any box or done on the standard FTP/SFTP port numbers of 22 and 23. It is advisable to change the SSH port of your node to something other than 22. To do this log into your box as root and edit the file.... /etc /ssh/sshd_config

Uncomment out the port and change it to whatever you wish as long nothing else is using that port. You will need to restart SSH so as long as you are logged right at the node and NOT via ssh, enter the following commands -
service sshd stop
service sshd start

The new port will now be in effect. Remember to change your routers port forwarding or you will not be able to remotely access the node. And like your new secure password, remember the new port number.

MAIL VOLUME
NOTE: If you are overwhelmed by the traffic on this list do not choose the No Email option but rather configure your list membership using the following option: Special notices. Only send me important update emails from the group moderator. This option will assure you still receive infrequent yet important emails from the moderators.

YOUR RIGHTS
It is "NOT" your right as a node owner to have access to this list.
Node owners who cannot get along with the majority of this group will be unsubscribed .

This reminder is sent every two weeks to the list.

Thank you,
Dave VE7LTD