search for: tcpproxy

...Hardware: x86_64 OS: Fedora Status: NEW Severity: normal Priority: P5 Component: nft Assignee: pablo at netfilter.org Reporter: zing at fastmail.fm I've a got a dnat rule inserted like this: # nft add rule tcpproxy preproxy tcp dport 500 meta mark set 0x1 dnat to 107.14.73.68:25 However, when I list it the dnat ip address is not shown (only the port): # nft list chain tcpproxy preproxy table ip tcpproxy { chain preproxy { type nat hook prerouting priority -150; policy accept; tcp dport i...

We have dovecot on a pop/imap server working as a proxy to dovecot on the backend storage servers. This is working fine, but the difficulty is that if I use, for example, avelsieve in squirrelmail, it doesn't know where to connect. I imagine the same problem would exist with sieve-capable mail clients such as KMail, especially since the outside world isn't allowed to connect directly to

I must be missing the point here somehow. From my simple mind I think that two things would be needed - first a mod, e.g., mod_sshd, or better an addition to mod_auth and mod_proxy so that a URL could be used to initiate contact to an sshd server elsewhere. The mod_auth part could/should be used to verity the credentials to used - basically setting up the VPN between ssh and httpd as ssh; the