On Friday 10 April 2009 11:50:33 Timothy Murphy wrote:
> If I ssh into my home server, ifconfig gives:
> --------------------------------------------
> tun0 Link encap:UNSPEC HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> inet addr:192.168.5.1 P-t-P:192.168.5.2 Mask:255.255.255.255
> UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
> RX packets:9 errors:0 dropped:0 overruns:0 frame:0
> TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:756 (756.0 b) TX bytes:1008 (1008.0 b)
> --------------------------------------------
> while ifconfig on my laptop gives
> --------------------------------------------
> tun0 Link encap:UNSPEC HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> inet addr:192.168.5.6 P-t-P:192.168.5.5 Mask:255.255.255.255
> UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
> RX packets:3 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:336 (336.0 b) TX bytes:252 (252.0 b)
> --------------------------------------------
> As I point out, the P-t-P addresses are different -
> I don't know if that is significant.
Thats normal. in my case
Server
tun0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:192.168.133.1 P-t-P:192.168.133.1 Mask:255.255.255.0
client laptop
tun0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:192.168.133.3 P-t-P:192.168.133.3 Mask:255.255.255.0
I'm using topology subnet so the inet addr and the P-t-P addresses are the
same. You're not so they will be different.
>
> Also ping from my laptop gives
> --------------------------------------------
> [tim@mary ~]$ ping -c1 192.168.5.1
> PING 192.168.5.1 (192.168.5.1) 56(84) bytes of data.
> From 192.168.5.1 icmp_seq=1 Destination Host Unreachable
> --------------------------------------------
> I'm not clear why it thinks it is pinging from 192.168.5.1
> and not 192.168.5.6 .
Your laptop can't connect to the server
Again in my case
[root@nogs ~]# ping -c1 192.168.133.1
PING 192.168.133.1 (192.168.133.1) 56(84) bytes of data.
64 bytes from 192.168.133.1: icmp_seq=1 ttl=64 time=53.8 ms
> Ping from the server gives
> --------------------------------------------
> [tim@mary ~]$ ping -c1 192.168.5.1
> PING 192.168.5.1 (192.168.5.1) 56(84) bytes of data.
> From 192.168.5.1 icmp_seq=1 Destination Host Unreachable
> --------------------------------------------
>
Pinging the server from itself gives "Destination Host Unreachable"
That's strange. In my case
[root@vpnexternal ~]# ping -c1 192.168.133.1
PING 192.168.133.1 (192.168.133.1) 56(84) bytes of data.
64 bytes from 192.168.133.1: icmp_seq=1 ttl=64 time=0.028 ms
Have you a firewall on the server blocking pings or the openvpn port 1194.
> I guess I have not set openvpn up correctly on my laptop ...?
>
I'd guess the problem is with the setup on the server.
Can you send on the config files for the server and client minus all the
comments ;-)
Regards,
Tony
> --
> Timothy Murphy
> e-mail: gayleard /at/ eircom.net
> tel: +353-86-2336090, +353-1-2842366
> s-mail: School of Mathematics, Trinity College Dublin
--
Dept. of Comp. Sci.
University of Limerick.
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
