On Thu, Jan 20, 2011 at 1:05 PM, mayak-cq <[email protected]> wrote: > hi all, > > i wrote about this issue in late december, and now having downloaded the > latest snapshot, it still persists: > > i have an issue with 2 pfsense machines each running 2.0 beta 5: > > all of the x509 stuff is fine, and i have a two-way tunnel between two > distant subnets [client=172.16.32.0/24 <-> server=172.16.8.0/24]. > > this problem that i'm facing is the client side -- it insists on using > the ip address from the address pool rather than the than the subnet ip. > > when a server side machine pings a client side machine it uses its > address of 172.16.8.1 as expected. > > when a client side machine (172.16.32.1) pings a server side machine, it > uses the 10.8.0.2 address. > > if i use a 1.23 client (ceteris paribus), all works as expected. > > i've just no clue -- i've tried everything. anyone have some hints? >
http://redmine.pfsense.org/issues/1216 you can work around with manual outbound NAT. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Commercial support available - https://portal.pfsense.org
