From: Truman, Michelle, NTCOM (mtruman@xxxxxxx)
Date: Fri Jul 28 2000 - 12:50:41 GMT-3
It is not common, but it does happen. I have seen it happen with
International. Perhaps it was a case of using the access list to permit
certain ports and deny all others and the GRE protocol was not considered
when they set up the list. (Isn't that port 47?)
-----Original Message-----
From: Wojtek Iwanczyk [mailto:wiwanczyk@exenet.com]
Sent: Friday, July 28, 2000 10:33 AM
To: sam@chinet.com
Cc: ccielab@groupstudy.com
Subject: Re: GRE Tunneling ..
Is it common for ISPs to block GRE ? I have set up GRE tunnels several times
before and never ran into problems like this .... As for source/destination.
i have tried using both the ethernet and serial (unnumbered IP from e0 ) but
either did not work ...
Wojtek Iwanczyk
Sr Support Engineer
Exenet Technologies
15 E 26th Street
New York, NY 10010
(212) 684 7300
wiwanczyk@exenet.com
>>> Sam Munzani <sam@chinet.com> 07/28/00 11:31AM >>>
On Router1 you have set destination address to be Router-2's Ethernet
interface address.
So,
On router-2 your tunnel source will be etheret0 not serial 0.1.
Through internet you may face some problems if some ISP in your PATH to
destination blocks GRE protocol. There is nothing you can do if that's the
case.
Sam
On Fri, 28 Jul 2000, Wojtek Iwanczyk wrote:
> I am attempting to set up a GRE tunnel through the internet between 2
private networks. I am trying to use the ISP/WAN interfaces as my
source/destination of the tunnel .. The config for the GRE is really simple,
- Tunnel interface , source of tunnel, and destination ... Somehow I can not
get it to work .. I know its probably something really stupid I am missing..
>
> at Router 2 I have tried using both the serial and ethernet interfaces as
the tunnel source, but either does not work.. I also attempted using
loopback interfaces as tunnel sources, but to no avail ..
>
> I would really appreciate any suggestions and/or comments ..
>
> thanx
>
>
>
> my configs are as follows ..
> Router 1
> »---------------------------
> interface Tunnel0
> ip address 192.168.151.1 255.255.255.0
> tunnel source Serial0/1
> tunnel destination 207.323.35.1
>
> interface Serial0/1
> description Level-3
> ip address 53.212.64.456 255.255.255.252
> ip nat outside
> encapsulation ppp
>
> Router2
> »----------------------------------------
> interface Tunnel0
> ip address 192.168.151.2 255.255.255.0
> tunnel source Serial0.1
> tunnel destination 53.212.64.456
>
> interface Ethernet0
> description Dayton-legal
> ip address 207.323.35.1 255.255.255.0
>
> interface Serial0
> description to WORLDCOM
> no ip address
> encapsulation frame-relay IETF
> bandwidth 1536
> no fair-queue
> frame-relay lmi-type ansi
> !
> interface Serial0.1 point-to-point
> description to WORLDCOM
> ip unnumbered Ethernet0
> no arp frame-relay
> bandwidth 1536
> frame-relay interface-dlci 426 IETF
>
>
> Wojtek Iwanczyk
> Sr Support Engineer
> Exenet Technologies
> 15 E 26th Street
> New York, NY 10010
> (212) 684 7300
> wiwanczyk@exenet.com
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:59 GMT-3