As regards preparing a jnos system: http://kf8kk.com/packet/jnos-linux/linux-jnos-setup-1.htm gives a 404
What port will the new gateway ip nee? Still 520 udp?
Thanks, jerome - ve7ass
On May 28, 2017, at 20:56, Brian Kantor Brian@UCSD.Edu wrote:
Hello. You are receiving this email because you are registered with portal.ampr.org as operating an IPIP encapsulating gateway, and there are changes coming that will affect the operation of your gateway.
We are replacing the equipment at the UCSD Internet-AMPRNet gateway with a newer, more capable device. In the process, the new equipment will be assigned a NEW IP ADDRESS. You will have to make changes in YOUR gateway configuration for your gateway to continue functioning.
The new equipment is already in service as amprgw.ucsd.edu and is on IP address 169.228.34.84. This replaces the old equipment, known as amprgw.sysnet.ucsd.edu, on IP address 169.228.66.251.
What you have to do to maintain the operability of your gateway:
- You must change the outgoing destination address of your gateway
from 169.228.66.251 to 169.228.34.84. You may do this immediately; the new equipment at UCSD is already operational.
- You must allow packets from the new address, 169.228.34.84, into
your gateway router software configuration. If you are running with a firewall, you must open a new path through it to your equipment. Packets (RIP44 transmissions) are already being sent to you from this address.
- You must continue to accept packets from the old address,
169.228.66.251, for a period of a few weeks as the changeover is being made. After a few weeks, packets will stop coming from that address and you may remove permission for them to enter your firewall, if you have one.
These are simple changes, involving editing a few configuration parameters, but because there are so many different types of gateway in operation on AMPRNet, how to make these changes cannot be detailed here. You may find more information regarding your particular configuration on https://wiki.ampr.org/ or on the 44net@hamradio.ucsd.edu discussion mailing list, which you should join if you are not already a subscriber.
Best wishes and 73,
- Brian
.
The only thing changing should be the IP. On Mon, May 29, 2017 at 1:01 AM jerome schatten romers@shaw.ca wrote:
(Please trim inclusions from previous messages) _______________________________________________ As regards preparing a jnos system: http://kf8kk.com/packet/jnos-linux/linux-jnos-setup-1.htm gives a 404
What port will the new gateway ip nee? Still 520 udp?
Thanks, jerome - ve7ass
On May 28, 2017, at 20:56, Brian Kantor Brian@UCSD.Edu wrote:
Hello. You are receiving this email because you are registered with portal.ampr.org as operating an IPIP encapsulating gateway, and there are changes coming that will affect the operation of your gateway.
We are replacing the equipment at the UCSD Internet-AMPRNet gateway with a newer, more capable device. In the process, the new equipment will be assigned a NEW IP ADDRESS. You will have to make changes in YOUR gateway configuration for your gateway to continue functioning.
The new equipment is already in service as amprgw.ucsd.edu and is on IP address 169.228.34.84. This replaces the old equipment, known as amprgw.sysnet.ucsd.edu, on IP address 169.228.66.251.
What you have to do to maintain the operability of your gateway:
- You must change the outgoing destination address of your gateway
from 169.228.66.251 to 169.228.34.84. You may do this immediately; the new equipment at UCSD is already operational.
- You must allow packets from the new address, 169.228.34.84, into
your gateway router software configuration. If you are running with a firewall, you must open a new path through it to your equipment. Packets (RIP44 transmissions) are already being sent to you from this address.
- You must continue to accept packets from the old address,
169.228.66.251, for a period of a few weeks as the changeover is being made. After a few weeks, packets will stop coming from that address and you may remove permission for them to enter your firewall, if you have one.
These are simple changes, involving editing a few configuration parameters, but because there are so many different types of gateway in operation on AMPRNet, how to make these changes cannot be detailed here. You may find more information regarding your particular configuration on https://wiki.ampr.org/ or on the 44net@hamradio.ucsd.edu discussion mailing list, which you should join if you are not already a subscriber.
Best wishes and 73, - Brian .
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Thanks Brian,
Just changed my scripts as per your instructions and all is working FB at this end!
--- 73 Δημήτρης - SV1UY 73 de Demetre - SV1UY IP Coordinator for AMPRNet in Greece e-mail: demetre.sv1uy@gmail.com Radio e-mail: sv1uy@winlink.org AMPRnet e-mail: sv1uy@sv1uy.ampr.org PACKET mail: SV1UY@SV1UY.ATH.GRC.EU WEB: http://www.qsl.net/sv1uy
On 29/05/2017 3:02 PM, Miguel Rodriguez wrote:
(Please trim inclusions from previous messages) _______________________________________________ The only thing changing should be the IP.
Yep all I had to do was change the IP in my startampr script (running on Linux).
-
Demetre - SV1UY -
jerome schatten -
Miguel Rodriguez -
Tony Langdon