I'm on openbsd 6.8, ran syspatch today.
relayd.conf:
table { 192.168.1.158 }
http protocol "httpproxy" {
pass request quick header "Host" value "nextcloud.mydomain.com" \
forward to
block
}
relay "proxy" {
listen on 192.168.1.156 port 80
protocol "httpproxy"
forward to
I'm trying to find the cleanest solution for correct routing of internal LAN
servers to the external IP's of other servers in the same LAN.
I have read the OpenBSD FAQ here
(http://www.openbsd.org/faq/pf/rdr.html#reflect ) and mostly understand the
problems associated with doing this via some
(the ip that doesn't work)
and none on .146. Could this be the issue? Let's see. Yup. It was the binat
that was breaking it. Damn. Makes some sense I guess. Is there a way to do
this while using the binat?
>
>
> On 14-6-2012 18:31, James Chase wrote:
> > I already have 1
I already have 1 FTP server setup to use ftp-proxy with pf and it works
fine. I am trying to add a second. It seemed like this should be
straightforward - just add another ftp-proxy instance connected to the
proper servers and add some rules to pf.conf. This didn't work (however the
first FTP serve
Hi,
I recently upgraded to 4.9 and everything seemed OK between my master
and backup firewalls setup with CARP and state sharing. The firewalls
were setup strange, the backup had the internal IP of .25 and the master
had .26. I wanted to swap this so that the master firewall IP would be
in nu
I have two OpenBSD 4.7 firewalls. I have tried to take them down to the
most basic configuration possible in my pf.conf ruleset while still passing
carp and state rule as suggested in the OpenBSD FAQ/Guide, however when I
reboot the master, the backup does not seem to have kept any state since m
I'm using pfsync to keep state between two OpenBSD 4.7 firewalls running
on soekris devices. The problem is that it seems to work erratically. My
test is to download a large file via HTTP from a server behind the
firewalls and then reboot the master firewall and once that comes back
up, the bac
7 matches
Mail list logo
