Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Glynn S. Condez" <glynn@itextron.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Help with GRE Tunneling
Date: Thu, 14 Feb 2002 01:20:36 +0000	[thread overview]
Message-ID: <marc-lartc-101364869015965@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101195228202181@msgid-missing>

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

Hello Bert, I understand about your solution but I dunno how to do it using
proxy arp. :( Bert can you help me how to do it? I will attach my config
file to this email and can you edit it and send it back to me? I really
badly need to work.


Thanks,
glynn

----- Original Message -----
From: "bert hubert" <ahu@ds9a.nl>
To: "Glynn S. Condez" <glynn@itextron.com>
Cc: <lartc@mailman.ds9a.nl>
Sent: Wednesday, February 13, 2002 3:59 PM
Subject: Re: [LARTC] Help with GRE Tunneling


> On Wed, Feb 13, 2002 at 10:25:55AM +0800, Glynn S. Condez wrote:
>
> > hello everyone, I have a working pptp vpn ( gre tunneling ). I setup
samba
> > server on both linux server, in network A, i could see the network
> > neighborhood with samba but i couldnt see the network of the otherside
but
> > I could open the samba server in Network B and also the workstation
using
> > \\networkB\share. I'd like to ask if its possible that im going to use
the
> > same subnet of the network B, so that both Network A and Network B are
in
> > the same subnet. Here is my config in pptp vpn on both networks. if its
> > possible can anyone correct the config?
>
> Could you use a mailer that does not send out thousand character lines?
You
> are supposed to wrap lines after ~75 characters on the internet. But
> returning to the question, yes, you can perform tricks to create a tunnel
> within the same subnet.
>
> This is done with proxy arp, which tells the router on Network A about
which
> hosts live on Network B. Network A will then think the router contains
> Network B - no explicit routes are needed.
>
> I *think* this will do what you want but I'd advise against it. There are
> SMB proxy servers available which can help you browse over network
borders.
> Those are probably the right solution.
>
> Regards,
>
> bert
>
> --
> http://www.PowerDNS.com          Versatile DNS Software & Services
> http://www.tk                              the dot in .tk
> Netherlabs BV / Rent-a-Nerd.nl           - Nerd Available -
> Linux Advanced Routing & Traffic Control: http://ds9a.nl/lartc
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO:
http://ds9a.nl/lartc/
>

[-- Attachment #2: vpnconfig.txt --]
[-- Type: text/plain, Size: 822 bytes --]

#Network A
/sbin/echo 1 > /proc/sys/net/ipv4/ip_forward
/sbin/ipchains -A forward -s 192.168.1.0/24 -j MASQ
/sbin/ipchains -A forward -s 192.168.2.0/24 -j MASQ
 
/sbin/insmod ip_gre
/sbin/ip tunnel add alas mode gre remote x.x.x.x local y.y.y.y ttl 255
/sbin/ip link set netb up
/sbin/ip addr add 192.168.1.1 dev netb
/sbin/ip route add 192.168.2.0/24 dev netb
------------------------------------------------------------------------------
#Network B
/sbin/echo 1 > /proc/sys/net/ipv4/ip_forward
/sbin/ipchains -A forward -s 192.168.2.0/24 -j MASQ
/sbin/ipchains -A forward -s 192.168.1.0/24 -j MASQ
 
/sbin/insmod ip_gre
/sbin/ip tunnel add text mode gre remote y.y.y.y local x.x.x.x ttl 255
/sbin/ip link set neta up
/sbin/ip addr add 192.168.2.1 dev neta
/sbin/ip route add 192.168.1.0/24 dev neta

      parent reply	other threads:[~2002-02-14  1:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-25  9:51 [LARTC] Help with gre tunneling glynn
2002-01-25 11:59 ` Greg Scott
2002-01-30  8:43 ` glynn
2002-01-30 12:20 ` Greg Scott
2002-02-13  2:25 ` [LARTC] Help with GRE Tunneling Glynn S. Condez
2002-02-13  7:59 ` bert hubert
2002-02-14  1:20 ` Glynn S. Condez [this message]

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-101364869015965@msgid-missing \
    --to=glynn@itextron.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox