29 Apr
2013
29 Apr
'13
10:41 p.m.
...didnt quite finish...
And so the IPIP tunnel is anchored to your router at its normal WAN IP (one
of the 128.118.0.0/16 addrs). Thats what completes the circuit,
if-you-will.
On Mon, Apr 29, 2013 at 8:39 PM, Andrew Ragone <ajr9166(a)rit.edu> wrote:
Ah gotcha. Fortunately the IPIP tunnel should help you
on this.
You don't have to worry about direct BGP advertisements from PSU for your
44-subnet. Effectively 44.0.0.0/8 is advertised to the internet by CALI
and the routing tables at CA know what subnet to route through your IPIP
tunnel. So, all traffic ultimately to/from your 44-net allocation hits the
internet through CA
On Mon, Apr 29, 2013 at 8:18 PM, Jim Alles <kb3tbx(a)gmail.com> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
On Mon, Apr 29, 2013 at 9:13 PM, Andrew Ragone <ajr9166(a)rit.edu> wrote:
_______________________________________________
Another comment, though there are always unique design cases, why
would you want NAT with 44net addresses? There are so many addresses
and the benefits to running native addressing across a network are
unrivaled.
I don't.
The problem is our internet access is through the University, Penn State (
128.118.0.0/16) and I have not yet found a way around that. I have been
told it would take an act of God. That doesn't bother me (since I have seen
it before ;). One possibility may be KINBER <http://www.kinber.org/>'s
new Pennsylvania Research & Education Network
(PennREN<http://www.kinber.org/docs/PennREN_Construction_Complete_release…)
based here in State College. And I am still exploring that.
I would appreciate any other ideas. I do not have a formal IT background.
What is possible? could this N2N <http://luca.ntop.org/n2n.pdf>be
relevant?
73,
Jim A. KB3TBX for PSARC <http://www.clubs.psu.edu/up/k3cr/>
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html