Re: ipsec rouing problem

Marco wrote:

Hi all, I have 3 linux box that I want to connect by a ipsec vpn: I
mean fw1 connects with fw2 and fw1 connects with fw3. Here ipsec.conf

[root@xxxxxxxxxxx ~]# telnet 192.168.2.250 5900
Trying 192.168.2.250...
telnet: connect to address 192.168.2.250: No route to host

Why? do you have any suggestion?

Yes: run route -n and enlighten yourself with your routing table.
The above means exactly nothing without knowing what your network looks
like.

--
All your bits are belong to us.
.

Relevant Pages

  • Re: Telnet: route to host
    ... Subject: Telnet: route to host ... > nicely to the linux box two feet away on some ports. ... > telnet, for some reason I'm puzzling over. ...
    (comp.unix.sco.misc)
  • Re: No route to host
    ... route to host" is returned. ... three telnet tests to try and the results are below. ... Connection closed by foreign host. ...
    (comp.mail.sendmail)
  • Re: Telnet: route to host
    ... Subject: Telnet: route to host ... > just one VAR's application - wonder how it uses localhost? ... >> host unreachable responses on attempts to access blocked ports. ... > I found the telnet problem. ...
    (comp.unix.sco.misc)
  • Re: No route to host
    ... message "no route to host" is returned. ... they claim that port 25 is not blocked. ... telnet: connect to address 63.208.196.171: No route to host ...
    (comp.mail.sendmail)
  • No route to host
    ... route to host" is returned. ... three telnet tests to try and the results are below. ... Connection closed by foreign host. ...
    (comp.mail.sendmail)