Hello,
I own some apartments in a city far far away. Out there, I have a Linux box ( Slackware 13.0, more or less ). I am trying to implement a
VPN between my home Linux server and the remote one. Ultimately, I want to route between my home network and the Fresno net, but right
now I'll be happy with a simple point-to-point connection. The openvpn on both machines is version 2.0.9, which came precompiled as a Slackware package. Both machines are connected to the Internet via DSL's, and they both have static IP's.
I am using certificates, and all that stuff seems to work. However, the IP address of the client is not being properly assigned.
Here are the config files:
--------- server config file ------------
port 1194
proto udp
dev tun
ca certs/ca.crt
cert certs/my-server.com.crt
key keys/my-server.com.key
dh dh1024.pem
server 10.120.200.0 255.255.255.0
keepalive 10 120
cipher BF-CBC
comp-lzo
persist-key
persist-tun
status openvpn-status.log
verb 9
--------end of server config file---------------------
-------- Client config file ---------------------------
client
dev tun
proto udp
remote my-server.com 1194
resolv-retry infinite
nobind
persist-key
persist-tun
ca certs/ca.crt
cert certs/my-client.crt
key keys/my-client.key
cipher BF-CBC
comp-lzo
verb 3
------------ end of client config file -----------------
*** On the client side, I would expect it to assign 10.120.200.2 for the client, with 10.120.200.1 as its pointopoint. Instead, it sets
10.120.200.6 and pointopoint 10.120.200.5...
And no amount of playing with ifconfig-push etc seems to help.
Ultimately, I want to nail down all the IP addresses staticly, but for now, I'd be happy if it just worked.
Must be something really simple I'm missing here....
On the server side: ifconfig tun1:
tun1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.120.200.1 P-t-P:10.120.200.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
On the client side:
root@my-client:/etc/openvpn# ifconfig tun0
tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.120.200.6 P-t-P:10.120.200.5 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Why isn't it assigning 10.120.200.2 & 10.120.200.1?
Thanks in advance,
- Jerry Kaidor ( jerry@tr2.com )
Goofy IPs
Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech
Forum rules
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
-
- OpenVpn Newbie
- Posts: 3
- Joined: Sat Nov 06, 2010 2:29 am
Re: Goofy IPs
OK,
Feeling a little dumb here. Guess it just works. The "inner" IP on a pointopoint is really a "nothing" -
you never use it. It does *not* have to match anything on the other end of the link. You just
don't try to reuse that "inner" IP somwhere else.
- Jerry Kaidor
Feeling a little dumb here. Guess it just works. The "inner" IP on a pointopoint is really a "nothing" -
you never use it. It does *not* have to match anything on the other end of the link. You just
don't try to reuse that "inner" IP somwhere else.
- Jerry Kaidor