<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Public IP behind pfsense via bridge]]></title><description><![CDATA[<p dir="auto">Hi,<br />
I am using pfsense 2.4 with a simple setup with one WAN interface an a public /28 subnet.<br />
Various internal services within this subnet are accessible via Virtual IPs an Port Forwarding to internal IPs.<br />
No I got an VPN Box from an customer which needs to be assigned a public IP directly without NAT.<br />
I thought about realizing this via bridging as described in this scenario:<br />
https://docs.netgate.com/pfsense/en/latest/book/firewall/methods-of-using-additional-public-ip-addresses.html#single-ip-subnet-on-wan<br />
pfsense itself hay IP a.b.c.2, my public gateway has a.b.c.1 as configured as default gateway on pfsense<br />
I attached the box to a new interface OPT1 of my pfsense giving ist the ip a.d.c.3<br />
I set up a bridge with the member Ports WAN and OPT1.<br />
OPT1 hat no own IP config.<br />
I allowed every traffic on Interface OPT1<br />
I allowed every traffic to a.b.c.3 on WAN</p>
<p dir="auto">I suggest that now I could access a.b.c.3 from "the internet"<br />
That does not work.<br />
Doing a packet capture on OPT1 I see ARP requests for a.b.c.3 comming from the gateway a.b.c.1 without answer.<br />
Doing packet capture on the vpn box there are no arp requests.</p>
<p dir="auto">I assigned a new interface called BRIDGE with the network port bridge0 (it's my only bridge)<br />
I changed system tunable net.link.bridge.pfil_bridge to 1<br />
allowed every traffic on Interface BRIDGE<br />
This does not work too.<br />
I see arp requests from the gateway on the interface BRIDGE (and the Interface OPT1) requesting for a.b.c.3 bit these are not answered an not getting through to net vpn box.</p>
<p dir="auto">Is there anything I forgot?<br />
Maybe someone has a hint where I can start to analyze where the problem is?</p>
<p dir="auto">Best Regards</p>
]]></description><link>https://forum.netgate.com/topic/151190/public-ip-behind-pfsense-via-bridge</link><generator>RSS for Node</generator><lastBuildDate>Sun, 19 Apr 2026 06:07:58 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/151190.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 10 Mar 2020 16:08:19 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Public IP behind pfsense via bridge on Wed, 11 Mar 2020 15:23:57 GMT]]></title><description><![CDATA[<p dir="auto">If you already have NAT configured for the others, did you look into 1:1 NAT (https://docs.netgate.com/pfsense/en/latest/book/nat/1-1-nat.html) which forwards all traffic for the public IP to that private IP?  Or does the VPN device actually require a public IP address in it?</p>
]]></description><link>https://forum.netgate.com/post/896379</link><guid isPermaLink="true">https://forum.netgate.com/post/896379</guid><dc:creator><![CDATA[SteveITS]]></dc:creator><pubDate>Wed, 11 Mar 2020 15:23:57 GMT</pubDate></item><item><title><![CDATA[Reply to Public IP behind pfsense via bridge on Tue, 10 Mar 2020 19:55:36 GMT]]></title><description><![CDATA[<p dir="auto">I came to this forum with almost exactly this question, although I haven't tried it, just been thinking about it.<br />
The only thing I can think of that's missing in your config is this: have you added the a.b.c.3 address as a virtual IP on the WAN interface?</p>
<p dir="auto">gr.<br />
tinus</p>
]]></description><link>https://forum.netgate.com/post/896258</link><guid isPermaLink="true">https://forum.netgate.com/post/896258</guid><dc:creator><![CDATA[gravity27]]></dc:creator><pubDate>Tue, 10 Mar 2020 19:55:36 GMT</pubDate></item></channel></rss>