All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Patrick Dench" <pat@acdisplays.com>
To: lartc@vger.kernel.org
Subject: [LARTC] gre nightmares...
Date: Fri, 15 Mar 2002 23:32:54 +0000	[thread overview]
Message-ID: <marc-lartc-101623517418593@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]

GRE Tunnels are RUINING MY LIFE!

Ok, maybe it isn't that bad.  
I am a Linux sophmore (for lack of a better term).  I have some experience, I have set up a Masq. Firewall at the company's office as well as one at home.  
Now... The fun part.  LInking the two so I can have access to office network assets from home.

Home:
    External: 65.28.x.y
    Internal: 192.168.55.1
    GRE Tunnel: "ofc"

Office:
    External 216.170.a.b
    Internal 192.168.5.1
    GRE Tunnel: "phome"

I have followed the information given in the GRE section, but to no avail.  I can't ping anything through the tunnel created, though it says the link is up.  The Tunnel runs from the Office External to Home External (and back)... 
I used
#ip route add 192.168.5.0/24 dev ofc
and
#ip route add 192.168.55.0/24 dev phome
on home and office Firewall/Routers.. I am stuck-ed!

On the Home Firewall/Router:
#ping -I ofc 192.168.5.1
or
#ping 192.168.5.1
Result in %100 packet loss...

On the Office Firewall/router:
#ping -I phome 192.168.55.1
or 
#ping 192.168.55.1
Result in %100 loss...

Any thoughts?

Patrick Dench
Application Specialist
www.acdisplays.com

[-- Attachment #2: Type: text/html, Size: 2986 bytes --]

             reply	other threads:[~2002-03-15 23:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-15 23:32 Patrick Dench [this message]
2002-03-16 11:31 ` [LARTC] gre nightmares Stef Coene

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-101623517418593@msgid-missing \
    --to=pat@acdisplays.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.