|
|
hi, just another bug/note for the push parameter i can't push a " since the paramteres should have to be inside a "" and neither \" nor "" working. so how can i push this: dhcp-option NBS "" the ' is not working since it has different meaning on the client side:-( James Yonan wrote: >> - neither on the server nor in the client we set any mtu. but we got >> this warning: >> WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1541', >> remote='link-mtu 1542' >> is it normal, a bug, or just a warning? should i have to fix it? >> ie. define link-mtu on both end? >> > This is related to the LZO issue above. >> - if i set the above server network then i've got in the log file: >> "IFCONFIG POOL: base=192.168.254.2 size=252 >> IFCONFIG POOL LIST" >> in this case i still can use in the ccd/* files eg. the following: >> ifconfig-push 192.168.254.2 255.255.255.0 >> or i should have to use different network for the fixed ip? or? >> > I believe that the ifconfig-push will override taking the address from > the pool. However you should not ifconfig-push an address which is > already "owned" by the pool. That could create a conflict. so what is the prefered way? ie. if i use server 192.168.254.0 255.255.255.0 what king of address should i push? >> wouldn't it be much better, cleaner and easier if the client-to-client >> defined and an iroute in the ccd/* files also 'generate' the above >> route command and push command for all clients except the ones who >> owns the network? >> >> - if i choose "topology subnet" and in the ccd/client file a: >> ifconfig-push 192.168.254.2 255.255.255.0 >> then why i see on the client: >> 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.254.2 P-t-P:192.168.254.2 Mask:255.255.255.0 >> 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) >> >> shouldn't the P-t-P:192.168.254.1 is the right settings? >> >> >> > > You are pushing 192.168.254.2 to the client, so why would you expect to > see the interface on the client set to something else? inet addr:192.168.254.2 P-t-P:192.168.254.1 Mask:255.255.255.0 -- Levente "Si vis pacem para bellum!" Warning: require_once(../../../archive_common.php) [function.require-once]: failed to open stream: No such file or directory in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2006-06/msg00160.html on line 230 Fatal error: require_once() [function.require]: Failed opening required '../../../archive_common.php' (include_path='/usr/local/lib/php') in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2006-06/msg00160.html on line 230 |