On Friday 13 June 2008, Ben Scott wrote: > Suggested course of action: > > Use the "route" command to review the routing tables on the two > computers. Just issue the command "route" with no arguments, and it > should print the routing table. Or maybe "route -n" to prevent the > system from wasting time trying to look up names for things. If > you're not sure how to interpret the output, post the output (for each > computer, identifying which is which), and we can check your work.
Ok thank you, here we go, I hope I can explain it well enough for people to understand. Server -- CentOS 5.1 10.8.8.1 Client1 -- WinXP 10.8.8.10 Client2 -- OpenBSD 10.8.8.6 Client1 and Client2 are on different subnets, 192.168.24.0 and 192.168.25.0. I need to create a route from an XP client to 10.10.0.42 on the OpenBSD client. Attempting to set "route add 10.10.0.0 mask 255.255.255.0 10.8.8.6 if 3" results in failure, " either the interface index is wrong ( interface index 3 is the TAP-Win adapter ) or the gateway does not lie on the same network as the interface". 10.8.8.6 is pingable from this machine and traceroute shows it as one hop, I can ssh in, etc. I get similar error messages (SIOCADDRT: Network is unreachable) if I try to set it up on a Linux client. I don't understand how I have to set the gateway, or perhaps I'm misunderstanding what the gateway should be. OpenVPN server: == Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.8.8.2 * 255.255.255.255 UH 0 0 0 tun0 63.131.36.0 * 255.255.255.224 U 0 0 0 eth0 10.8.8.0 10.8.8.2 255.255.255.0 UG 0 0 0 tun0 default 63.131.36.1 0.0.0.0 UG 0 0 0 eth0 == Client1 running XP: == Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.24.254 192.168.24.214 20 10.8.8.0 255.255.255.0 10.8.8.9 10.8.8.10 1 10.8.8.8 255.255.255.252 10.8.8.10 10.8.8.10 30 10.8.8.10 255.255.255.255 127.0.0.1 127.0.0.1 30 10.255.255.255 255.255.255.255 10.8.8.10 10.8.8.10 30 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.24.0 255.255.255.0 192.168.24.214 192.168.24.214 20 192.168.24.214 255.255.255.255 127.0.0.1 127.0.0.1 20 192.168.24.255 255.255.255.255 192.168.24.214 192.168.24.214 20 224.0.0.0 240.0.0.0 10.8.8.10 10.8.8.10 30 224.0.0.0 240.0.0.0 192.168.24.214 192.168.24.214 20 255.255.255.255 255.255.255.255 10.8.8.10 10.8.8.10 1 255.255.255.255 255.255.255.255 192.168.24.214 192.168.24.214 1 Default Gateway: 192.168.24.254 == Client2 running OpenBSD: == Routing tables Internet: Destination Gateway Flags Refs Use Mtu Interface default 192.168.25.254 UGS 0 2307 - fxp0 10.8.8/24 10.8.8.5 UGS 0 405 - tun0 10.8.8.5 10.8.8.6 UH 0 2 - tun0 10.10.0/24 link#1 UC 0 0 - xl0 10.10.0.42 00:08:da:61:5c:68 UHLc 0 3 - xl0 loopback localhost.corp.app UGRS 0 0 33224 lo0 localhost.corp.app localhost.corp.app UH 0 0 33224 lo0 192.168.25/24 link#2 UC 0 0 - fxp0 192.168.25.25 link#2 UHLc 0 411 - fxp0 192.168.25.254 00:0e:2e:b1:1e:da UHLc 0 0 - fxp0 BASE-ADDRESS.MCAST localhost.corp.app URS 0 0 33224 lo0 == thanks, --charlie -- ------------------------------------------------------------------------ Charles Farinella Appropriate Solutions, Inc. (www.AppropriateSolutions.com) [EMAIL PROTECTED] voice: 603.924.6079 fax: 603.924.8668 _______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
