From: "Glynn S. Condez" <glynn@itextron.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Followup Question: Help with GRE Tunneling
Date: Wed, 13 Feb 2002 03:30:55 +0000 [thread overview]
Message-ID: <marc-lartc-101357009612695@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1891 bytes --]
I would like to make both Network A and B have the same subnet. I did a changes to my config pls correct if this will work.
#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 # this will be omitted
/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.1.0/24 dev netb # this option dont work coz theres an existing route in routing table and the routing table is set to eth1 interface. so if i force to add it using "route add -net 192.168.1.0 netmask 255.255.255.0 dev neta"
it cant ping the internal ip's only the tunnel is working :(
------------------------------------------------------------------------------
#Network B
/sbin/echo 1 > /proc/sys/net/ipv4/ip_forward
#/sbin/ipchains -A forward -s 192.168.2.0/24 -j MASQ # this will be omitted
/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.1.2 dev neta
/sbin/ip route add 192.168.1.0/24 dev neta # this option dont work coz theres an existing route in routing table and the routing table is set to eth1 interface. so if i force to add it using "route add -net 192.168.1.0 netmask 255.255.255.0 dev neta"
it cant ping the internal ip's only the tunnel is working :(
Pls check correct this config if its possible to work. Thanks
[-- Attachment #2: Type: text/html, Size: 4115 bytes --]
reply other threads:[~2002-02-13 3:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-101357009612695@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 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.