Re: Network route problem

2012-01-08 Thread Tim
On Sat, 2012-01-07 at 11:21 -0600, Kevin Martin wrote: > And not top-posting (or bottom posting) is simply done by posting your > replies at the bottom of the thread, not the top. That way > people can read from top-to-bottom of a thread (like a book). Makes > the threads much easier to follow then

Re: Network route problem

2012-01-07 Thread Andre Speelmans
Hello, > Here is the output of : route -n : > > 0.0.0.0                192.168.50.2        0.0.0.0         UG    0      0 >      0 eth0 > 169.254.0.0        0.0.0.0                 255.255.0.0     U     1002   0 >      0 eth0 > 172.16.2.6          192.168.50.184  255.255.255.255 UGH   0      0    

Re: Network route problem

2012-01-07 Thread Aaron Konstam
On Sat, 2012-01-07 at 18:01 +0100, Luc MAIGNAN wrote: > Yes, 50.184 is another box on the network on which the tunnel has been > setup via racoon. > On 50.184 the access to 172.16.2.6 works fine. ANd I want to use 50.184 > as a gateway for this host on the network. > > What email address have I

Re: Network route problem

2012-01-07 Thread Aaron Konstam
On Sat, 2012-01-07 at 17:18 +0100, Luc MAIGNAN wrote: > Hi, > > I have the following problem. > > Here is the output of : route -n : > > 0.0.0.0192.168.50.20.0.0.0 UG0 > 00 eth0 > 169.254.0.00.0.0.0 255.255.0.0 U

Re: Network route problem

2012-01-07 Thread Paul Morgan
On Jan 7, 2012 11:19 AM, "Luc MAIGNAN" wrote: > > Hi, > > I have the following problem. > > Here is the output of : route -n : > > 0.0.0.0192.168.50.20.0.0.0 UG0 0 0 eth0 > 169.254.0.00.0.0.0 255.255.0.0 U 1002 0

Re: Network route problem

2012-01-07 Thread Luc MAIGNAN
Le 07/01/2012 19:37, Kevin Martin a écrit : On 01/07/2012 11:56 AM, Luc MAIGNAN wrote: Le 07/01/2012 18:53, Kevin Martin a écrit : On 01/07/2012 11:49 AM, Luc MAIGNAN wrote: Le 07/01/2012 18:39, Kevin Martin a écrit : On 01/07/2012 11:30 AM, Luc MAIGNAN wrote: Le 07/01/2012 18:21, Kevin

Re: Network route problem

2012-01-07 Thread Kevin Martin
On 01/07/2012 11:56 AM, Luc MAIGNAN wrote: > > Le 07/01/2012 18:53, Kevin Martin a écrit : >> >> On 01/07/2012 11:49 AM, Luc MAIGNAN wrote: >>> Le 07/01/2012 18:39, Kevin Martin a écrit : On 01/07/2012 11:30 AM, Luc MAIGNAN wrote: > Le 07/01/2012 18:21, Kevin Martin a écrit :

Re: Network route problem

2012-01-07 Thread Luc MAIGNAN
Le 07/01/2012 18:53, Kevin Martin a écrit : On 01/07/2012 11:49 AM, Luc MAIGNAN wrote: Le 07/01/2012 18:39, Kevin Martin a écrit : On 01/07/2012 11:30 AM, Luc MAIGNAN wrote: Le 07/01/2012 18:21, Kevin Martin a écrit : On 01/07/2012 11:01 AM, Luc MAIGNAN wrote: Yes, 50.184 is another bo

Re: Network route problem

2012-01-07 Thread Kevin Martin
On 01/07/2012 11:49 AM, Luc MAIGNAN wrote: > > Le 07/01/2012 18:39, Kevin Martin a écrit : >> >> On 01/07/2012 11:30 AM, Luc MAIGNAN wrote: >>> Le 07/01/2012 18:21, Kevin Martin a écrit : On 01/07/2012 11:01 AM, Luc MAIGNAN wrote: > Yes, 50.184 is another box on the network on which

Re: Network route problem

2012-01-07 Thread Luc MAIGNAN
Le 07/01/2012 18:39, Kevin Martin a écrit : On 01/07/2012 11:30 AM, Luc MAIGNAN wrote: Le 07/01/2012 18:21, Kevin Martin a écrit : On 01/07/2012 11:01 AM, Luc MAIGNAN wrote: Yes, 50.184 is another box on the network on which the tunnel has been setup via racoon. On 50.184 the access to 172

Re: Network route problem

2012-01-07 Thread Kevin Martin
On 01/07/2012 11:30 AM, Luc MAIGNAN wrote: > > Le 07/01/2012 18:21, Kevin Martin a écrit : >> >> On 01/07/2012 11:01 AM, Luc MAIGNAN wrote: >>> Yes, 50.184 is another box on the network on which the tunnel has been >>> setup via racoon. >>> On 50.184 the access to 172.16.2.6 works fine. ANd I w

Re: Network route problem

2012-01-07 Thread Luc MAIGNAN
Le 07/01/2012 18:21, Kevin Martin a écrit : On 01/07/2012 11:01 AM, Luc MAIGNAN wrote: Yes, 50.184 is another box on the network on which the tunnel has been setup via racoon. On 50.184 the access to 172.16.2.6 works fine. ANd I want to use 50.184 as a gateway for this host on the network.

Re: Network route problem

2012-01-07 Thread Kevin Martin
On 01/07/2012 11:01 AM, Luc MAIGNAN wrote: > Yes, 50.184 is another box on the network on which the tunnel has been setup > via racoon. > On 50.184 the access to 172.16.2.6 works fine. ANd I want to use 50.184 as a > gateway for this host on the network. > > What email address have I to use to

Re: Network route problem

2012-01-07 Thread Reindl Harald
Am 07.01.2012 18:01, schrieb Luc MAIGNAN: > What email address have I to use to do not top post? jesus christ put your answer BELOW and not on top as others in this thread does so that after 10 replies with 5 top and 5 bottom replied the whole thread is not unreadable Google -> top post http:/

Re: Network route problem

2012-01-07 Thread Luc MAIGNAN
Yes, 50.184 is another box on the network on which the tunnel has been setup via racoon. On 50.184 the access to 172.16.2.6 works fine. ANd I want to use 50.184 as a gateway for this host on the network. What email address have I to use to do not top post ? Le 07/01/2012 17:53, Kevin Martin

Re: Network route problem

2012-01-07 Thread Kevin Martin
On 01/07/2012 10:46 AM, Luc MAIGNAN wrote: > 192.168.50.184 is a gateway on which a IPSEC tunnel allow to access to host > 172.16.2.6 > > > > Le 07/01/2012 17:45, Kevin Martin a écrit : >> >> On 01/07/2012 10:18 AM, Luc MAIGNAN wrote: >>> Hi, >>> >>> I have the following problem. >>> >>> Here i

Re: Network route problem

2012-01-07 Thread Luc MAIGNAN
192.168.50.184 is a gateway on which a IPSEC tunnel allow to access to host 172.16.2.6 Le 07/01/2012 17:45, Kevin Martin a écrit : On 01/07/2012 10:18 AM, Luc MAIGNAN wrote: Hi, I have the following problem. Here is the output of : route -n : 0.0.0.0192.168.50.20.

Re: Network route problem

2012-01-07 Thread Kevin Martin
On 01/07/2012 10:18 AM, Luc MAIGNAN wrote: > Hi, > > I have the following problem. > > Here is the output of : route -n : > > 0.0.0.0192.168.50.20.0.0.0 UG0 0 >0 eth0 > 169.254.0.00.0.0.0 255.255.0.0 U 1002 0

Network route problem

2012-01-07 Thread Luc MAIGNAN
Hi, I have the following problem. Here is the output of : route -n : 0.0.0.0192.168.50.20.0.0.0 UG0 00 eth0 169.254.0.00.0.0.0 255.255.0.0 U 1002 00 eth0 172.16.2.6 192.168.50.184 255.255.255.