you need to tell the router to pass/nat 10.x.y.z too not only 192.168.1.0/24. i don't know if that's possible with the "plastic/appliance" routers but it's certainly possible with a freebsd / openwrt / cisco/ any where you have more control than a simple web interface. while your def gw is through 10.x.y.w all your outgoing connection local ip will be 10.x.y.w. if you run sendmail locally you can tell it to send from 192.168.1.90 via ClientPortOptions config directive.
Thanks! I'm not sure if that would be possible with my router, but I will try tomorrow.
while your def gw is through 10.x.y.w all your outgoing connection local ip will be 10.x.y.w.
I thought that the packet flow with VPN on was like that:
192.168.1.90 (me) -> 192.168.1.1 (router) -> 10.x.y.z (VPN server; a gateway) -> destination. And receiving is in backward order. Since VPN server acts a gateway, with incoming traffic, it tells my router that destination should be 192.168.1.90 so now router knows where to send packets.
But know what we're trying to do is:
192.168.1.90 (me) -> 192.168.1.1 (gateway) -> ...
but the packet that we send this way has a source address of 10.x.y.z, which my router can't handle?
But now I thought about it once again and got confused: how does ipfw rule that I added works then? I mean, it forwards packets to 192.168.1.1, but the packet would anyway go into my router, otherwise how would it access 10.x.y.z? I'm certanly lacking some basic knowledge here, but I believe I will now learn from practice.