07-28-2008
Are you trying to set up a tunnel ? Something like:
hosts_behind_NAT>============[server]
Did you set up routing on the hosts?
Did you set up routes back?
are tunnel interfaces up?
moreover you said your server has just one interface: eth0,
did you mean one internal,LAN interface, or one at all (no WAN )???
honestly I don't have much experience with pptp,
more with GRE... but the question is interesting
10 More Discussions You Might Find Interesting
1. IP Networking
Hi
I know this problem is more likely some windows problem but it has also something to do with unix.
We have a windows nt environment wich uses AIX (unix) machines as file servers (samba). In our windows network environment we nicely see al the unix file servers via the 10 MB network. Last... (2 Replies)
Discussion started by: Mark Detrez
2 Replies
2. IP Networking
following Problem.
I configured my SuSE Linux 8.0 as a router. I4l, named, ip_forward, iptables (NAT/MASQUERADING) are running or are aktivatet.
I just can get a internet connection about the proxy server squid, but if i want to use other protocols i need functional routing.
(I had this... (1 Reply)
Discussion started by: razor
1 Replies
3. IP Networking
I have a question concerning networking. Could any forum
members explain to me why I might be getting "no route
to host" messages when I try to connect through ftp and
http protocols?
I have went to my etc/hosts file and everything seems to be
configured properly. I can connect within my... (1 Reply)
Discussion started by: cstovall
1 Replies
4. IP Networking
hi,
below is the situation:
my server is in 128.10.200.xxx network.
i have a solaris computer running in a subnet. this computer got 2 nic card.
1 is 172.18.198.xxx , another 1 is 10.100.xxx.11
there is a machine stick with this computer, ip is 10.100.xxx.12
so, 10.100.xxx.11 and... (3 Replies)
Discussion started by: kyhah
3 Replies
5. Solaris
Hi,
I got problem of Sun Solaris 8 routing.
IP of SunA is 10.16.64.164, and have routing table:
10.16.64.0 10.16.64.164 U 1 19236 bge1
10.6.0.0 10.6.0.3 U 1 16534 bge0
224.0.0.0 10.6.0.3 U 1 ... (4 Replies)
Discussion started by: milo
4 Replies
6. Red Hat
hi,
having an issue on a class C network with trying to get a redhat diskless setup going. I am using oracle enterprise 5, which is RHEL 5.3 i believe.
here is the scenario:
sun sparc m4k that i am planning on making the red hat boxes boot off after i get the network issue fixed.
... (3 Replies)
Discussion started by: caddyjoe77
3 Replies
7. AIX
I need the following solution , please help me...
Current situation
ip: 192.168.0.12 persistent and 192.168.254.12 service ip
gateway: 192.168.0.254
subnet: 255.255.255.0
i have added a new ip on a new nic
ip: 10.10.255.40
gateway: 10.10.255.62
subnet: 255.255.255.224
... (1 Reply)
Discussion started by: rajibimran
1 Replies
8. IP Networking
hi guys!
I was searching few days for a solution to my problem but haven't found one or I'm too dumb to understand.
Here's what happened:
I have a linux server used as a router. It has an eth0 and eth1 (local interface). I just installed openvpn (I need it only as a client), I configured it and... (0 Replies)
Discussion started by: shamora
0 Replies
9. IP Networking
Internet Gateway
192.168.0.201
Server 1
192.168.0.101
192.168.1.101
192.168.2.101
gateway: 192.168.0.201
VIP: 192.168.1.100
VIP: 192.168.2.100
Server 2
192.168.0.102
192.168.1.102
192.168.2.102
gateway: 192.168.0.201
Client 1
192.168.2.201
gateway: 192.168.2.100 (1 Reply)
Discussion started by: hopfensp
1 Replies
10. Solaris
Hi,
I have two physical interfaces on a servers.
We have connected them to differerent subnets.
1) First interface:
10.158.49.87 to newtwork 10.158.49.0, its gateway is 10.158.49.1
(It is added as default gateway)
It is existing set up. It works well
2) Second interface:
... (1 Reply)
Discussion started by: sri243
1 Replies
LEARN ABOUT FREEBSD
nos-tun
NOS-TUN(8) BSD System Manager's Manual NOS-TUN(8)
NAME
nos-tun -- implement ``nos'' or ``ka9q'' style IP over IP tunnel
SYNOPSIS
nos-tun -t tunnel -s source -d destination -p protocol_number [source] target
DESCRIPTION
The nos-tun utility is used to establish an nos style tunnel, (also known as ka9q or IP-IP tunnel) using a tun(4) kernel interface.
Tunnel is the name of the tunnel device /dev/tun0 for example.
Source and destination are the addresses used on the tunnel device. If you configure the tunnel against a cisco router, use a netmask of
``255.255.255.252'' on the cisco. This is because the tunnel is a point-to-point interface in the FreeBSD end, a concept cisco does not
really implement.
Protocol number sets tunnel mode. Original KA9Q NOS uses 94 but many people use 4 on the worldwide backbone of ampr.org.
Target is the address of the remote tunnel device, this must match the source address set on the remote end.
EXAMPLES
This end, a FreeBSD box on address 192.168.59.34:
nos-tun -t /dev/tun0 -s 192.168.61.1 -d 192.168.61.2 192.168.56.45
Remote cisco on address 192.168.56.45:
interface tunnel 0
ip address 192.168.61.2 255.255.255.252
tunnel mode nos
tunnel destination 192.168.59.34
tunnel source 192.168.56.45
AUTHORS
Nickolay N. Dudorov <nnd@itfs.nsk.su> wrote the program, Poul-Henning Kamp <phk@FreeBSD.org> wrote the man-page. Isao SEKI
<iseki@gongon.com> added a new flag, IP protocol number.
BUGS
We do not allow for setting our source address for multihomed machines.
BSD
April 11, 1998 BSD