> I tend to agree that currently when i now go to any Israeli commercial site from the 44 net ip the packet travel to UCSD and then back to UCSD and by tunnel to me again and this is a long trip
> If there was a mechanism to allow the traffic to go to any local 44 gateway and then the packet will go to the local Internet the trip would be much shorter
> but i dont know how it can be done these days that every IPS block Source 44 Net address from passing through
> as for 44 net to 44 net trafic it look ok because it tunnel direct to the gateway and not passing through AMPRGW
> the only thing I can think off is to put a secondary portal for redundancy .
> Ronen - 4Z4ZQ
To solve this you need to talk to people at an ISP who want to announce the 44.138.0.0/16 block on internet
on their routers just like they do for the address block you use at home, then forward the traffic on that
block to your internet router. Similarly you forward the outgoing traffic to internet via their router.
When you have found an ISP who would be prepared to do that, at a cost you can afford, then you write a
letter to Brian asking for permission to do that and then you tell them to set it all up.
(NOT BEFORE YOU HAVE THE PERMISSION FROM Brian!)
Your own router then receives all traffic for that address block directly from internet and you can route
parts of it to others via radio, VPN, or whatever you like.
Please note you will have a constant traffic of several Mbit/s from only the bad guys that are
portscanning and the reflection from the bad guys using your addresses as spoofed source address, and
this is increasing all the time.
So don't do this from your home, put your router in a datacenter where you have 100 Mbit/s or more.
We have done this here for the 44.137.0.0/16 network and there are other places where this is done.
I can ping google from a 44-address and have reply times under 10ms.
This also enables us to run repeaters with echolink, DMR, D-Star etc etc on 44-net addresses.
Rob