internal routing & vpn


 
Thread Tools Search this Thread
Special Forums IP Networking internal routing & vpn
# 1  
Old 03-08-2005
internal routing & vpn

hi there. i got a vpn working. this is what happens:
remote pc ----(vpn/INTERNET)----vpn server--(redirect)---webapp (internal network)
real: 200.12.15.20 200.20.45.123
vpn: 10.8.0.2 10.8.0.1
internal: 130.1.11.183 130.1.11.180
the tunnel gets done. then, when i enter 130.1.11.180 i see how packets go from the remote to the webapp, then reponse to the vpn server, but the vpn server doesnt forward the packets back to the remote pc. ip forwarding is working. i go a line on my routing table that shold do the trick, but it's not happening:

10.8.0.2 0.0.0.0 255.255.255.255 tun0
are there any special things i should activate/deativate for this to get done??
thanks
wach
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. IP Networking

Cisco 3750 Switch ASA VPN Routing

Hi,I want connect my ASA 5510 firewall to a 3750 switch with RIP routing. Unfortunately,I am having issues passing the VPN subnet through rip to the 3750.I don't understand how the routing table is populated on the ASA. Any suggestions? (0 Replies)
Discussion started by: Ayaerlee
0 Replies

2. IP Networking

VPN Server & Client

First of all, hello. I have a problem installing a vpn server and client. My server is a computer running windows 7, and windows, running a virtual machine running debian. In the debian system, I've the vpn server installed (SoftEther VPN Server) The problems come when I try to connect to... (1 Reply)
Discussion started by: Blues23
1 Replies

3. IP Networking

OS X & VPN DNS Issue

I'll try and be brief and detailed. I have a Macbook Pro Retina running Mavericks. When on my network at the office (work) everything local works just fine. Local servers are resolved through our internal DNS settings. For example, we have a fileserver at "fs01". I can connect to it with... (1 Reply)
Discussion started by: jbhardman
1 Replies

4. IP Networking

IP routing & Squid

Hello, I have a Squid Proxy Web content filtering three subnets, the matter is that each subnet has a separate gateway and with the implementation of the proxy, all traffic is routed to a single link. Any idea how to fix it? thanks (2 Replies)
Discussion started by: kev_2108
2 Replies

5. IP Networking

IPSec VPN Routing

Hello, I'm trying to setup a gateway VPN between two routers across an unsecured network between two local networks. The routers are both linux and I'm using the ipsec tools, racoon and setkey. So far hosts from either local net can successfully ping hosts on the other local net without issue. ... (0 Replies)
Discussion started by: salukibob
0 Replies

6. Shell Programming and Scripting

PHP read large string & split in multidimensional arrays & assign fieldnames & write into MYSQL

Hi, I hope the title does not scare people to look into this thread but it describes roughly what I'm trying to do. I need a solution in PHP. I'm a programming beginner, so it might be that the approach to solve this, might be easier to solve with an other approach of someone else, so if you... (0 Replies)
Discussion started by: lowmaster
0 Replies

7. IP Networking

I need HELP to Set up Coyote Linux router with 1 static IP & 64 internal static IP

hello, i need help on setting my coyote linux, i've working on this for last 5 days, can't get it to work. I've been posting this message to coyote forum, and other linux forum, but haven't get any answer yet. Hope someone here can help me...... please see my attached picture first. ... (0 Replies)
Discussion started by: dlwoaud
0 Replies

8. UNIX for Advanced & Expert Users

Forwarding internal internet packets to internal webserver using iptables

Hi, I need to redirect internal internet requests to a auth client site siting on the gateway. Currently users that are authenticated to access the internet have there mac address listed in the FORWARD chain. All other users need to be redirected to a internal site for authentication. Can... (1 Reply)
Discussion started by: mshindo
1 Replies

9. Linux

Linux & Internal Modems

Hello There! Why is it so difficult (read: impossible) to configure and run an internal modem in linux operating system. Not all can afford an external modem and hardware modems are obsolete as well as out of production. Is it impossible to write software drivers for an internal modem to work... (6 Replies)
Discussion started by: Jawwad
6 Replies
Login or Register to Ask a Question
IP-NETNS(8)                                                            Linux                                                           IP-NETNS(8)

NAME
ip-netns - process network namespace management SYNOPSIS
ip [ OPTIONS ] netns { COMMAND | help } ip netns [ list ] ip netns add NETNSNAME ip [-all] netns del [ NETNSNAME ] ip netns set NETNSNAME NETNSID ip netns identify [ PID ] ip netns pids NETNSNAME ip [-all] netns exec [ NETNSNAME ] command... ip netns monitor ip netns list-id DESCRIPTION
A network namespace is logically another copy of the network stack, with its own routes, firewall rules, and network devices. By default a process inherits its network namespace from its parent. Initially all the processes share the same default network namespace from the init process. By convention a named network namespace is an object at /var/run/netns/NAME that can be opened. The file descriptor resulting from opening /var/run/netns/NAME refers to the specified network namespace. Holding that file descriptor open keeps the network namespace alive. The file descriptor can be used with the setns(2) system call to change the network namespace associated with a task. For applications that are aware of network namespaces, the convention is to look for global network configuration files first in /etc/netns/NAME/ then in /etc/. For example, if you want a different version of /etc/resolv.conf for a network namespace used to isolate your vpn you would name it /etc/netns/myvpn/resolv.conf. ip netns exec automates handling of this configuration, file convention for network namespace unaware applications, by creating a mount namespace and bind mounting all of the per network namespace configure files into their traditional location in /etc. ip netns list - show all of the named network namespaces This command displays all of the network namespaces in /var/run/netns ip netns add NAME - create a new named network namespace If NAME is available in /var/run/netns/ this command creates a new network namespace and assigns NAME. ip [-all] netns delete [ NAME ] - delete the name of a network namespace(s) If NAME is present in /var/run/netns it is umounted and the mount point is removed. If this is the last user of the network names- pace the network namespace will be freed and all physical devices will be moved to the default one, otherwise the network namespace persists until it has no more users. ip netns delete may fail if the mount point is in use in another mount namespace. If -all option was specified then all the network namespace names will be removed. It is possible to lose the physical device when it was moved to netns and then this netns was deleted with a running process: $ ip netns add net0 $ ip link set dev eth0 netns net0 $ ip netns exec net0 SOME_PROCESS_IN_BACKGROUND $ ip netns del net0 and eth0 will appear in the default netns only after SOME_PROCESS_IN_BACKGROUND will exit or will be killed. To prevent this the processes running in net0 should be killed before deleting the netns: $ ip netns pids net0 | xargs kill $ ip netns del net0 ip netns set NAME NETNSID - assign an id to a peer network namespace This command assigns a id to a peer network namespace. This id is valid only in the current network namespace. If the keyword "auto" is specified an available nsid will be chosen. This id will be used by the kernel in some netlink messages. If no id is assigned when the kernel needs it, it will be automatically assigned by the kernel. Once it is assigned, it's not possible to change it. ip netns identify [PID] - Report network namespaces names for process This command walks through /var/run/netns and finds all the network namespace names for network namespace of the specified process, if PID is not specified then the current process will be used. ip netns pids NAME - Report processes in the named network namespace This command walks through proc and finds all of the process who have the named network namespace as their primary network names- pace. ip [-all] netns exec [ NAME ] cmd ... - Run cmd in the named network namespace This command allows applications that are network namespace unaware to be run in something other than the default network namespace with all of the configuration for the specified network namespace appearing in the customary global locations. A network namespace and bind mounts are used to move files from their network namespace specific location to their default locations without affecting other processes. If -all option was specified then cmd will be executed synchronously on the each named network namespace even if cmd fails on some of them. Network namespace name is printed on each cmd executing. ip netns monitor - Report as network namespace names are added and deleted This command watches network namespace name addition and deletion events and prints a line for each event it sees. ip netns list-id - list network namespace ids (nsid) Network namespace ids are used to identify a peer network namespace. This command displays nsid of the current network namespace and provides the corresponding iproute2 netns name (from /var/run/netns) if any. EXAMPLES
ip netns list Shows the list of current named network namespaces ip netns add vpn Creates a network namespace and names it vpn ip netns exec vpn ip link set lo up Bring up the loopback interface in the vpn network namespace. SEE ALSO
ip(8) AUTHOR
Original Manpage by Eric W. Biederman iproute2 16 Jan 2013 IP-NETNS(8)