Sponsored Content
Full Discussion: IPSec - VPN using shared key
Special Forums Cybersecurity IPSec - VPN using shared key Post 34239 by eNTer on Tuesday 11th of February 2003 09:56:59 AM
Old 02-11-2003
My real problem is that the Linux gateway is using a "pre-shared ke", while the xBSD gateway is asking different keys with different encryption styles: encryption key and auth key. That i did not figure out: why BSD needs different keys and FreeSWAN/ipsec does not, or how can a BSD gateway talk to a FreeSWAN/Linux gateway with PSK?
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

How to interpret the shared memory key

I'm facing a problem interpreting the shared memory key on an AIX machine. (1) I go to a property file and I see the following: shm_key = "119112066" (2) So I now go the command prompt and do this: ipcs -m | grep 119112066 And, I do not find it. So what I do is to run the... (2 Replies)
Discussion started by: vijaygade
2 Replies

2. 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

3. Solaris

Solaris 8 ssh public key authentication issue - Server refused our key

Hi, I've used the following way to set ssh public key authentication and it is working fine on Solaris 10, RedHat Linux and SuSE Linux servers without any problem. But I got error 'Server refused our key' on Solaris 8 system. Solaris 8 uses SSH2 too. Why? Please help. Thanks. ... (1 Reply)
Discussion started by: aixlover
1 Replies

4. Cybersecurity

IPSEC

hello, after configuration ipsec in ip4 I can not ping between client and server whereas I had success ping before configuration! I also generate different key for AH and ESP as i have shown below. what is my problem and what should i do to have ping and test the configuration? code: ... (0 Replies)
Discussion started by: elinaz
0 Replies

5. Programming

Shared library with acces to shared memory.

Hello. I am new to this forum and I would like to ask for advice about low level POSIX programming. I have to implement a POSIX compliant C shared library. A file will have some variables and the shared library will have some functions which need those variables. There is one special... (5 Replies)
Discussion started by: iamjag
5 Replies

6. IP Networking

VPN IPSec Openswan

Hi all, I have installed Openswan and configured IPSec and works perfect, but for some unknown reasons it stop working. I see that the tunnels are up and established. The route to the destination are added. Everything by the book seems to be ok. But somehow when i start to ping the other side (... (4 Replies)
Discussion started by: ivancd
4 Replies

7. IP Networking

IPSec Openswan Site to Site VPN - Big Pain

Hi @all, I try to connect 2 LANs with IPSec/Openswan LAN 1: 192.168.0.0/24 LAN 2: 192.168.1.0/24 This is my Config: conn HomeVPN # # Left security gateway, subnet behind it, nexthop toward right. left=192.168.1.29 ... (1 Reply)
Discussion started by: bahnhasser83
1 Replies

8. IP Networking

Best tool to monitor VPN IPSEC Tunneling

We are using cyberoam device, VPN IPSEC tunnel is going of frequently even the traffic is throug. Please suggest what may be the cause for the above mentioned issue. Also suggest a best tool to monitor the same VPN IPSEC tunnel connectivity. (4 Replies)
Discussion started by: marunmeera
4 Replies
route(8c)																 route(8c)

Name
       route - manually manipulate the routing tables

Syntax
       /etc/route [ -f ] [ -n ] command args ]

Description
       The  program  is  used  to manipulate the network routing tables manually.  However, normally it is not needed, as the system routing table
       management daemon, should tend to this task.

       The program accepts two commands: add, to add a route and delete, to delete a route.

       All commands have the following syntax:

	    /etc/route command [ net | host ] destination gateway [ metric ]

       In this syntax, destination is a host or network for which the route is to, gateway is the gateway to which packets  should  be	addressed,
       and  metric  is	an  optional count indicating the number of hops to the destination.  The metric is required for add commands.	It must be
       zero if the destination is on a directly-attached network, and nonzero if the route utilizes one or more gateways.

       When adding a route with metric 0, the gateway given is the address of this host on the common network, indicating the interface to be used
       for  transmission.   Routes to a particular host are distinguished from routes to a network by interpreting the Internet address associated
       with destination.  The optional keywords net and host force the destination to be interpreted as a network or host, respectively.   If  the
       destination  has  a local address part of INADDR_ANY, then the route is assumed to be to a network. Otherwise, it is presumed to be a route
       to a host.  If the route is to a destination connected via a gateway, the metric should be greater than 0.  All	symbolic  names  specified
       for a destination or gateway are looked up first as a host name using If this lookup fails, is then used to interpret the name as that of a
       network.

       The command uses a raw socket and the SIOCADDRT and SIOCDELRT ioctls to do its work.  As such, only the superuser can  modify  the  routing
       tables.

Options
       -f   Flushes  the routing tables of all gateway entries.  If is used with one of the commands described above, the tables are flushed prior
	    to the command's application.

       -n   Prevents attempts to print host and network names symbolically when reporting actions.

Restrictions
       The change operation is not implemented.  Therefore, you should first add the new route, and then delete the old one.

Diagnostics
       add [host | network] %s: gateway %s flags %x"
       The specified route is being added to the tables.  The values printed are from the routing table entry supplied in the ioctl call.  If  the
       gateway	address  used  was not the primary address of the gateway (the first one returned by the gateway address is printed numerically as
       well as symbolically.

       delete [ host | network] %s: gateway %s flags %x
       The specified route is being deleted from the tables.  The values printed are from the routing table entry supplied in the ioctl call.	If
       the  gateway  address used was not the primary address of the gateway (the first one returned by the gateway address is printed numerically
       as well as symbolically.

       %s %s done
       When the flag is specified, each routing table entry that is deleted is indicated with a message of this form.

       Network is unreachable
       An attempt to add a route failed because the gateway listed was not on a directly-connected network.  The next-hop gateway must be given.

       not in table
       A delete operation was attempted for an entry which was not present in the tables.

       routing table overflow
       An add operation was attempted, but the system was low on resources and was unable to allocate memory to create the new entry.

See Also
       intro(4n), routed(8c)

																	 route(8c)
All times are GMT -4. The time now is 10:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy