HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: cipe routing
Operating System - Linux
1829514
Members
1937
Online
109991
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2003 06:01 AM
07-08-2003 06:01 AM
cipe routing
Hello. I have the folowing boxes.
Machine A
eth0: $real_ip1
eth1: 192.168.0.1(local network)
cipcb0: 10.0.0.1
/ ||
internet
||
\/
Machine B
eth0: real_ip
cipcb0: 10.0.0.2
I configured cipe for both boxes, and it works. Now i
want to make that all the traffic from machine A to
internet to pass through machine B, and then to go to
internet.
Something like that :if i access www.google.com from
machine A to pass
machineA->internet->machineB->www.google.com
.Something like machine B, to be a virtual gateway of
machine A. Or at least all the trafic from the local
network (192.168.0.1/24) to have this route to
internet. well, the traceroute shoud be like that for
a box from the local network (supposse 192.168.0.3)
192.168.0.3->192.168.0.1->10.0.0.1->10.0.0.2->ip_real2->
internet. Or something like that.
The configuration file otions.cipcb0 for both
macines is something like that
ptpaddr 10.0.0.2
ipaddr 10.0.0.1
me ip_real1:2304
peer ip_real2:2304
key xxxxxxxxxxxxxxxxxxxxxxxxx
Any idea how can i do that? Thanks very much.
Machine A
eth0: $real_ip1
eth1: 192.168.0.1(local network)
cipcb0: 10.0.0.1
/ ||
internet
||
\/
Machine B
eth0: real_ip
cipcb0: 10.0.0.2
I configured cipe for both boxes, and it works. Now i
want to make that all the traffic from machine A to
internet to pass through machine B, and then to go to
internet.
Something like that :if i access www.google.com from
machine A to pass
machineA->internet->machineB->www.google.com
.Something like machine B, to be a virtual gateway of
machine A. Or at least all the trafic from the local
network (192.168.0.1/24) to have this route to
internet. well, the traceroute shoud be like that for
a box from the local network (supposse 192.168.0.3)
192.168.0.3->192.168.0.1->10.0.0.1->10.0.0.2->ip_real2->
internet. Or something like that.
The configuration file otions.cipcb0 for both
macines is something like that
ptpaddr 10.0.0.2
ipaddr 10.0.0.1
me ip_real1:2304
peer ip_real2:2304
key xxxxxxxxxxxxxxxxxxxxxxxxx
Any idea how can i do that? Thanks very much.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2003 06:30 AM
07-08-2003 06:30 AM
Re: cipe routing
Hi !
The easiest way should be to set up an Iptables rule on machine A and a proxy on machine B...
More on iptables :
http://www.netfilter.org
On squid :
http://www.squid-cache.org
Ask here if you want more details on configuration.
J
The easiest way should be to set up an Iptables rule on machine A and a proxy on machine B...
More on iptables :
http://www.netfilter.org
On squid :
http://www.squid-cache.org
Ask here if you want more details on configuration.
J
You can lean only on what resists you...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2003 11:16 AM
07-08-2003 11:16 AM
Re: cipe routing
Well, i want to route all the trafic through tunnel, not only http traffic. I want a routing solution, where my knowledge are missing here. I want the default gateway on machine A to be 10.0.0.2 and to add a iptables masquarade on machine B(
iptables -A POSTROUTING -t nat -s -o eth0 -j MASQUERADE).I tried to make the default route 10.0.0.2 on machine A , and i added a route to ip_real of machine B through the A gateway, but it doesn't work. Can anyone give me a detailed solution ? Thanks
iptables -A POSTROUTING -t nat -s -o eth0 -j MASQUERADE).I tried to make the default route 10.0.0.2 on machine A , and i added a route to ip_real of machine B through the A gateway, but it doesn't work. Can anyone give me a detailed solution ? Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2003 12:50 PM
07-08-2003 12:50 PM
Re: cipe routing
what about
iptables -t nat - A PREROUTING -i eth0 -j dnat --to-destination 10.0.0.2
You could also set up squid on B, which would also allow you to monitor connections (if you use port 3128, then former command ecom 10.0.0.2:3128).
hth
J
iptables -t nat - A PREROUTING -i eth0 -j dnat --to-destination 10.0.0.2
You could also set up squid on B, which would also allow you to monitor connections (if you use port 3128, then former command ecom 10.0.0.2:3128).
hth
J
You can lean only on what resists you...
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP