
We’ll assume that your tunnel interface is TUN0 … replace this below as you see fit. Â We’re going to wind up not using a relay server, and just directly connecting to the target hosts.

Objective: Â Running a postfix SMTP server on Ubuntu Linux, route all outbound SMTP through a VPN tunnel. Many thanks to Lekensteyn and the other contributors to the post “ iptables – Target to Route Packet to Specific Interface” on for key pointers. Â It took me a while to figure this out (I’m not the world’s greatest IP routing guru), so I figured it might be of use to you. Â I don’t have much mail to send (just what the kids generate, and the occasional system alert), so I don’t feel that I’m much of a threat to anyone’s traffic. The problem is that UVerse blocks outbound SMTP (port 25) traffic, and doesn’t provide their own relay (or, more accurately, won’t relay mail that’s neither to nor from an AT&T address). Â I continue to have an account with StrongVPN that I use (I originally acquired it to give me a US IP for use when out of the US … side note, I’m really happy with StrongVPN).

I’ve recently switched providers (having moved countries), and am now reconstructing my services in a new location, using AT&T UVerse.


 The next problem you have is that the rpc.mountd port is assigned randomly, unless you fix it otherwise. While I didn’t carefully record all of my steps, here are some general pointers for you to help you in running it down.įirst, the best way to test whether the ZoneMinder API is working is just to fetch the URL to any port sunrpcĢ. It turned out that the problem was with the APC cache not working properly in the ZoneMinder API. I was getting an error about invalid credentials (sorry, didn’t record the error). I was having difficulty getting the ZoneMinder module to work with HomeAssistant, running on Ubuntu 16.04.
