|
From: James Y. <ji...@yo...> - 2004-10-14 21:12:55
|
On Thu, 14 Oct 2004, Marc-Christian Petersen wrote: > On Thursday 14 October 2004 21:18, Marc-Christian Petersen wrote: > > Hi James, > > > > No, the client config can't use --iroute, but the server on the other > > > side of the client needs to specify both "route" and "iroute" with the > > > subnet that corresponds to the ifconfig-pool addresses being passed out > > > to A's clients. This is necessary so that the return packets on B's > > > subnet are able to find their way back to A's clients. > > > hmm, sorry, I'm confused. There's already a route for 172.16.0.0/24 which > > are passed out to A's clients. The problem is that I have to send clients > > something like "push route 192.168.1.0 255.255.255.0", then clients > > connecting to A are able to speak with B and its subnet, but when I use > > that in the server config of A, everything behind server B can't speak with > > the outside. > > Hmm, okay, I can use --up on the client side with a script containing > something like this: > > /sbin/route add -net 192.168.1.0 netmask 255.255.255.0 gw $5 > > But I thought its somehow possible to specify this at the server A side. Yes, on the server: push "route 192.168.1.0 255.255.255.0" James |