I relay don't know why you are so objecting a gateway with CISCO I used to work a lot with Cisco when i have worked at the System team of Israel largest ISP .
Because a Cisco is not suitable for setting up an IPIP gateway. It is reliable, but it cannot do this job. It can do other jobs but that is not relevant. You would not recommend a truck when someone asks what car to use to get to the office, either.
Indeed it is much more complicated these days that UCSD dont do anymore 44 net forwarding and a routing line needed for every gateway ..
This is crucial. And also, the fact that more people now use dynamic addresses.
I get a very reliable solution with Zero money (my Cisco 1005 was taken from the trash cost me nothing)
I recommend you to put it back there... and I think most people here will agree. The Raspberry Pi was developed 15 years after this box, has a 10 times faster CPU, 10 times more memory and uses a lot less power. (and costs less than a 10th of what this thing must have cost when it was new)
However im willing to listen to your advice and test the Rasberry Pi If there is someone here that can direct me step by step until a working system and then i may consider testing it
As I said, it can be found on www.ampr.org More specific, on this page: http://wiki.ampr.org/index.php/Ubuntu_Linux_Gateway_Example
I have a Raspberry Pi running as a gateway for over 2.5 years now and it has been without any problem. It has never crashed. Good, because I have never touched it nor ever seen it. It has been mail-ordered and directly sent to a datacenter where it was powered up may 25, 2013 and has worked ever since (of course sometimes rebooted for updates). The above example was written by someone partly drawing from the example configuration I posted on this mailinglist some years ago.
Im not familiar with what have been told about the multi tunnel that a Cisco can not do ... (actually im not understand what the problem or the limitation is )
It is clear from your posted example (btw, it is not a good idea to post Cisco config files because now everyone can log in to your router, the passwords are in the config!).
In a Cisco, a Tunnel interface has a "tunnel destination". One. But there are 324 tunnel destinations in the network. So you need 324 tunnel interfaces. In Linux, a single tunnel interface can serve as many destinations as you want, by setting a route with a nexthop that serves the function of the "tunnel destination" in Cisco. Every route has its own nexthop (gateway). And this route table can be updated automatically with ampr-ripd, so you never need to download any encap file.
I know that at least two gateways are running and operating currently with CIsco
But most likely not a 1005!
Rob
Dear Rob And Thank also Antonio I have read carefully and start to understand ,, First of all about sending config files and Passwords Passwords are encrypted .. however im count on the hams and even if not so i can make reset and load the router again It is not a Company that something will happen if they will crack its router .... as for my Cisco there are solutions for the limitations one is to forward to a Tunnel peer that can handle all the necessary routes However i have more two routers on the way as a donation one is 2600 and other 2800 i will check if they can handle the 300 tunnels needed and i will ask the local hams to help me to build a Raspbarry pi system .. if you say it work for years (for me months is also enough) i may consider it as a good solution anyway i still need the Cisco to Connect our P25 Repeater to a WorldWide Ham -Network this can be done only with Cisco (minimum requirements for this connection is Cisco 2600) so if this Cisco will be able to do the AMPR gateway as well ill do it if not looks like the Rapbarry will be the solution Best 73;s Ronen - 4Z4ZQ http://www.ronen.org
________________________________________ From: 44Net 44net-bounces+ronenp=hotmail.com@hamradio.ucsd.edu on behalf of Rob Janssen pe1chl@amsat.org Sent: Monday, February 22, 2016 2:00 PM To: 44net@hamradio.ucsd.edu Subject: Re: [44net] route lines from encap file for CISCO Router
(Please trim inclusions from previous messages) _______________________________________________
I relay don't know why you are so objecting a gateway with CISCO I used to work a lot with Cisco when i have worked at the System team of Israel largest ISP .
Because a Cisco is not suitable for setting up an IPIP gateway. It is reliable, but it cannot do this job. It can do other jobs but that is not relevant. You would not recommend a truck when someone asks what car to use to get to the office, either.
Indeed it is much more complicated these days that UCSD dont do anymore 44 net forwarding and a routing line needed for every gateway ..
This is crucial. And also, the fact that more people now use dynamic addresses.
I get a very reliable solution with Zero money (my Cisco 1005 was taken from the trash cost me nothing)
I recommend you to put it back there... and I think most people here will agree. The Raspberry Pi was developed 15 years after this box, has a 10 times faster CPU, 10 times more memory and uses a lot less power. (and costs less than a 10th of what this thing must have cost when it was new)
However im willing to listen to your advice and test the Rasberry Pi If there is someone here that can direct me step by step until a working system and then i may consider testing it
As I said, it can be found on www.ampr.org More specific, on this page: http://wiki.ampr.org/index.php/Ubuntu_Linux_Gateway_Example
I have a Raspberry Pi running as a gateway for over 2.5 years now and it has been without any problem. It has never crashed. Good, because I have never touched it nor ever seen it. It has been mail-ordered and directly sent to a datacenter where it was powered up may 25, 2013 and has worked ever since (of course sometimes rebooted for updates). The above example was written by someone partly drawing from the example configuration I posted on this mailinglist some years ago.
Im not familiar with what have been told about the multi tunnel that a Cisco can not do ... (actually im not understand what the problem or the limitation is )
It is clear from your posted example (btw, it is not a good idea to post Cisco config files because now everyone can log in to your router, the passwords are in the config!).
In a Cisco, a Tunnel interface has a "tunnel destination". One. But there are 324 tunnel destinations in the network. So you need 324 tunnel interfaces. In Linux, a single tunnel interface can serve as many destinations as you want, by setting a route with a nexthop that serves the function of the "tunnel destination" in Cisco. Every route has its own nexthop (gateway). And this route table can be updated automatically with ampr-ripd, so you never need to download any encap file.
I know that at least two gateways are running and operating currently with CIsco
But most likely not a 1005!
Rob
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Unfortunately, Cisco type "7" is just obfuscation and no encryption. The enable password to the config you posted yesterday is "1005".
If you're really stuck to Cisco, you might have some better luck with a Cisco 7200 emulated in Dynamips.
Cheers/73, jof / K6BGP
On Mon, Feb 22, 2016 at 2:35 PM, R P ronenp@hotmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ Dear Rob And Thank also Antonio I have read carefully and start to understand ,, First of all about sending config files and Passwords Passwords are encrypted .. however im count on the hams and even if not so i can make reset and load the router again It is not a Company that something will happen if they will crack its router .... as for my Cisco there are solutions for the limitations one is to forward to a Tunnel peer that can handle all the necessary routes However i have more two routers on the way as a donation one is 2600 and other 2800 i will check if they can handle the 300 tunnels needed and i will ask the local hams to help me to build a Raspbarry pi system .. if you say it work for years (for me months is also enough) i may consider it as a good solution anyway i still need the Cisco to Connect our P25 Repeater to a WorldWide Ham -Network this can be done only with Cisco (minimum requirements for this connection is Cisco 2600) so if this Cisco will be able to do the AMPR gateway as well ill do it if not looks like the Rapbarry will be the solution Best 73;s Ronen - 4Z4ZQ http://www.ronen.org
From: 44Net 44net-bounces+ronenp=hotmail.com@hamradio.ucsd.edu on behalf of Rob Janssen pe1chl@amsat.org Sent: Monday, February 22, 2016 2:00 PM To: 44net@hamradio.ucsd.edu Subject: Re: [44net] route lines from encap file for CISCO Router
(Please trim inclusions from previous messages) _______________________________________________
I relay don't know why you are so objecting a gateway with CISCO I used to work a lot with Cisco when i have worked at the System team of Israel largest ISP .
Because a Cisco is not suitable for setting up an IPIP gateway. It is reliable, but it cannot do this job. It can do other jobs but that is not relevant. You would not recommend a truck when someone asks what car to use to get to the office, either.
Indeed it is much more complicated these days that UCSD dont do anymore 44 net forwarding and a routing line needed for every gateway ..
This is crucial. And also, the fact that more people now use dynamic addresses.
I get a very reliable solution with Zero money (my Cisco 1005 was taken from the trash cost me nothing)
I recommend you to put it back there... and I think most people here will agree. The Raspberry Pi was developed 15 years after this box, has a 10 times faster CPU, 10 times more memory and uses a lot less power. (and costs less than a 10th of what this thing must have cost when it was new)
However im willing to listen to your advice and test the Rasberry Pi If there is someone here that can direct me step by step until a working system and then i may consider testing it
As I said, it can be found on www.ampr.org More specific, on this page: http://wiki.ampr.org/index.php/Ubuntu_Linux_Gateway_Example
I have a Raspberry Pi running as a gateway for over 2.5 years now and it has been without any problem. It has never crashed. Good, because I have never touched it nor ever seen it. It has been mail-ordered and directly sent to a datacenter where it was powered up may 25, 2013 and has worked ever since (of course sometimes rebooted for updates). The above example was written by someone partly drawing from the example configuration I posted on this mailinglist some years ago.
Im not familiar with what have been told about the multi tunnel that a Cisco can not do ... (actually im not understand what the problem or the limitation is )
It is clear from your posted example (btw, it is not a good idea to post Cisco config files because now everyone can log in to your router, the passwords are in the config!).
In a Cisco, a Tunnel interface has a "tunnel destination". One. But there are 324 tunnel destinations in the network. So you need 324 tunnel interfaces. In Linux, a single tunnel interface can serve as many destinations as you want, by setting a route with a nexthop that serves the function of the "tunnel destination" in Cisco. Every route has its own nexthop (gateway). And this route table can be updated automatically with ampr-ripd, so you never need to download any encap file.
I know that at least two gateways are running and operating currently with CIsco
But most likely not a 1005!
Rob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-
Jonathan Lassoff -
R P -
Rob Janssen