Can you give me some idea how to check Multinet? I let you set it up remotely and I don't know what/how to check it >.<
--
Mark Benson
http://markbenson.org/bloghttp://twitter.com/MDBenson
On 21 Mar 2012, at 14:04, "Steve Davidson" <jeep at scshome.net> wrote:
The Eastern US HECnet hub will be down this Friday due to static IP
address reassignment and bandwidth increases. Any systems that
currently connect to IP address 69.21.253.230 should change to
bridge.declab.net. This includes bridge and Multinet Tunnel connections
as well as UUHEC (UUCP port 540) connections.
Regards,
-Steve
The Eastern US HECnet hub will be down this Friday due to static IP
address reassignment and bandwidth increases. Any systems that
currently connect to IP address 69.21.253.230 should change to
bridge.declab.net. This includes bridge and Multinet Tunnel connections
as well as UUHEC (UUCP port 540) connections.
Regards,
-Steve
On 3/19/2012 4:15 PM, Dave McGuire wrote:
Brian, I think the best way to approach it is to just try this:
interface Tunnel1
no ip address
decnet cost 10
bridge-group 1
You know, I was thinking about this. I don't think you should need to do the bridge-group if all you want to do is DECnet routing.
Let's try it without. :-D
-brian
On 03/20/2012 10:18 AM, Brian Hechinger wrote:
Another possibility might be to to just bridge everything across the
tunnel, then use ACLs to filter on EtherType (DECnet Phase IV is 0x6003):
We'll have to do some testing, but I don't *think* we should need to do
that. I'll check with some cisco guys smarter than me.
What'd you find out? I'm ready to start hacking whenever you are.
access-list 200 permit 0x6003
...
interface Tunnel1
no ip address
bridge-group 1 input-type-list 200 # or output-type-list?www
What about LAT/MOP/etc? I'm assuming we may or may not want to allow those?
Definitely LAT, but I kinda think not for MOP. I mean, everyone has a copy of PR0801ENG.SYS, right? ;)
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 3/19/2012 4:15 PM, Dave McGuire wrote:
Brian, I think the best way to approach it is to just try this:
interface Tunnel1
no ip address
decnet cost 10
bridge-group 1
Sometimes the simplest approach is best. =) Offhand I don't see why that wouldn't work.
We'll find out, but I don't see why it wouldn't.
Another possibility might be to to just bridge everything across the tunnel, then use ACLs to filter on EtherType (DECnet Phase IV is 0x6003):
We'll have to do some testing, but I don't *think* we should need to do that. I'll check with some cisco guys smarter than me.
access-list 200 permit 0x6003
...
interface Tunnel1
no ip address
bridge-group 1 input-type-list 200 # or output-type-list?www
What about LAT/MOP/etc? I'm assuming we may or may not want to allow those?
-brian
Dave,
This end uses the Multinet Tunnel. It also happens to be connected via the bridge. You can install Multinet at the same time that TCP/IP is but you may run only one of the stacks at a time. This end uses static IP addresses but it will accommodate Dynamic DNS addresses at the other end (for Multinet only). All I need is you IP address. This end is 69.21.253.230. Multinet uses port 700 so be sure to forward as necessary.
Regards,
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Dave McGuire
Sent: Saturday, March 17, 2012 16:19
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] intro
Thank you! I'm told that Steve Davidson runs the big hub
on the US East coast. Ideally I'd like to get online via a
GRE tunnel. Can anyone offer any advice on how to get
started? I don't know the the organizational structure is here.
-Dave
On 03/17/2012 02:00 PM, Joe Ferraro wrote:
Hi Dave... welcome!
On Sat, Mar 17, 2012 at 10:19 AM, Saku Set l <setala at gmail.com
<mailto:setala at gmail.com>> wrote:
Dave,
Welcome to play!
--Saku (Area #11)
--
Dave McGuire, AK4HZ
New Kensington, PA
On 03/19/2012 05:56 PM, Johnny Billquist wrote:
Just a check here. When you do this, will the ethernet packets coming
through retain their original MAC source addresses? Otherwise this will
not work.
Right, as the area/node are encoded in the MAC address. I'm pretty sure the MAC addresses will pop out unchanged.
Oh, and you probably need to pass through both 0x6003 and 0x6004.
Oh ok, thanks for the tip!
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 03/19/2012 06:07 PM, Johnny Billquist wrote:
Ah, and rereading the stuff right now reminds me of why I never got
anywhere with it. I can't seem to understand how you use it for non-IP
traffic.
Even reading the Wikipedia article, it says:
"A GRE tunnel is used when IP packets need to be sent from one network
to another, without being parsed or treated like IP packets by any
intervening routers."
So, it is essentially for IP traffic. It don't seem to be generic enough
for any random ethernet traffic.
Then, of course, you can run any kind of traffic on top of that IP layer
in the GRE tunnel, and it will all be invisible to the outside. But that
don't help when there is no IP to start with...
No, GRE isn't just for IP. You can bridge most any protocol with GRE. I've bridged non-IP-based Windows networks (for a customer) many years ago using GRE over a WAN. The Wikipedia article is poorly worded.
I'll happily go on talking with people interested in this more, but we
might do it outside of this list, since it will quickly become pretty
narrow and technical.
Ok.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 2012-03-19 15.00, Dave McGuire wrote:
On 03/19/2012 05:57 PM, Mark Wickens wrote:
Sorry for being ignorant, what's GRE?
It's not ignorance if you've had no reason to know about it. :-) Generic
Routing Encapsulation, a Cisco protocol that implements generalized
tunneling. You can tunnel just about anything over GRE. Most OSs
implement GRE natively nowadays as well.
Ah, and rereading the stuff right now reminds me of why I never got anywhere with it. I can't seem to understand how you use it for non-IP traffic.
Even reading the Wikipedia article, it says:
"A GRE tunnel is used when IP packets need to be sent from one network to another, without being parsed or treated like IP packets by any intervening routers."
So, it is essentially for IP traffic. It don't seem to be generic enough for any random ethernet traffic.
Then, of course, you can run any kind of traffic on top of that IP layer in the GRE tunnel, and it will all be invisible to the outside. But that don't help when there is no IP to start with...
I'll happily go on talking with people interested in this more, but we might do it outside of this list, since it will quickly become pretty narrow and technical.
Johnny
