<?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[Bridging WiFi to LAN - What changed?]]></title><description><![CDATA[<p dir="auto">Hey all,</p>
<p dir="auto">I'm stumped today.</p>
<p dir="auto">I've been running the 20090422-1111 snapshot for quite a while now because when I upgrade to something newer Bridge0 stops functioning correctly.  From the wireless clients I can touch the various FreeBSD boxen, the other access point, anything really, except the firewall/AP which also happens to be the default gateway.</p>
<p dir="auto">My config hasn't changed in months and searching the forums hasn't yielded anything obvious so I thought I'd ask around.</p>
<p dir="auto">What's changed in the way Bridging works between 20090422 and now?  The rules seem right, the AP (Atheros chipset) obviously works MOSTLY correctly, but I'm still missing something.</p>
<p dir="auto">Anyone?  Anyone?  Bueller?  Bueller?</p>
<p dir="auto">–-</p>
<p dir="auto">Addendum:  I suppose I should mention that this install is 2.0/7.2 and that routing works just fine.<br />
So, for the record;</p>
<p dir="auto">Old Setup - LAN and OPT1 Bridged with interface Bridge0;<br />
Client: 10.1.1.1<br />
AP/Firewall: 10.1.1.254/24<br />
Client can touch everyone else on the network except 10.1.1.254.</p>
<p dir="auto">New Setup - OPT1 has an interface IP of 10.1.2.254, no Bridge0;<br />
Client: 10.1.2.1<br />
AP/Firewall: 10.1.1.254/24 on LAN, 10.1.2.254/24 on OPT1<br />
Works fine except that now Samba/SMB shares aren't accessible to the wireless clients.<br />
SSH, Nagios (monitoring ICMP) and other protocols work just fine.</p>
<p dir="auto">I'm still experimenting and surfing the forums for answers.  Any help would be appreciated.</p>
<p dir="auto">Thanks in advance.</p>
]]></description><link>https://forum.netgate.com/topic/16450/bridging-wifi-to-lan-what-changed</link><generator>RSS for Node</generator><lastBuildDate>Tue, 09 Jun 2026 11:47:50 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/16450.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 06 Jul 2009 14:27:18 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Bridging WiFi to LAN - What changed? on Tue, 07 Jul 2009 18:00:09 GMT]]></title><description><![CDATA[<p dir="auto">Booyah!  Thanks for the link.  For some bizarre reason I knew about clicking on "save" in the interfaces menu but the subject line of that thread was so obtuse that I really don't even remember seeing it in my searches.</p>
<p dir="auto">So I'm only a little nuts.  Good.</p>
<p dir="auto">Just so long as others are aware and are working toward a fix.</p>
<p dir="auto">Thanks again.</p>
]]></description><link>https://forum.netgate.com/post/202041</link><guid isPermaLink="true">https://forum.netgate.com/post/202041</guid><dc:creator><![CDATA[2low4zero]]></dc:creator><pubDate>Tue, 07 Jul 2009 18:00:09 GMT</pubDate></item><item><title><![CDATA[Reply to Bridging WiFi to LAN - What changed? on Tue, 07 Jul 2009 16:28:30 GMT]]></title><description><![CDATA[<p dir="auto">In GUI, go to Interfaces/LAN, and then click Save, then Apply.  This should fix the bridge issue temporarily until next reboot.  Discussed in the following thread:</p>
<p dir="auto">http://forum.pfsense.org/index.php/topic,15468.msg86681.html#msg86681</p>
]]></description><link>https://forum.netgate.com/post/202035</link><guid isPermaLink="true">https://forum.netgate.com/post/202035</guid><dc:creator><![CDATA[AhnHEL]]></dc:creator><pubDate>Tue, 07 Jul 2009 16:28:30 GMT</pubDate></item><item><title><![CDATA[Reply to Bridging WiFi to LAN - What changed? on Tue, 07 Jul 2009 14:47:40 GMT]]></title><description><![CDATA[<p dir="auto">Brief update;</p>
<p dir="auto">Bridging dies arbitrarily on my setup.  If I give the WiFi (OPT1) interface an IP address and then delete and recreate the bridge, everything works fine… for a while (some unspecified unit of time or usage).  A reboot kills bridging.  Deleting and recreating the bridge brings it back.</p>
<p dir="auto">Again, symptomatically; the wireless clients simply can't touch the firewall/AP.  The rest of the network remains available to SSH, SMB shares, ICMP, ...whatever... on the wired network.  Nothing shows up in the syslogs regarding BridgeD/Murder/Death/Kill.</p>
<p dir="auto">Has anyone else experienced this?  Or is anyone else interested in particulars for the purposes of debugging?</p>
<p dir="auto">Or is it just time to separate out my access point from the firewall (which would be REALLY annoying) ?</p>
]]></description><link>https://forum.netgate.com/post/202026</link><guid isPermaLink="true">https://forum.netgate.com/post/202026</guid><dc:creator><![CDATA[2low4zero]]></dc:creator><pubDate>Tue, 07 Jul 2009 14:47:40 GMT</pubDate></item><item><title><![CDATA[Reply to Bridging WiFi to LAN - What changed? on Mon, 06 Jul 2009 21:29:01 GMT]]></title><description><![CDATA[<p dir="auto">Just a brief update;</p>
<p dir="auto">I messed around with different combinations of IP addresses / netmasks and with running OPT1 unnumbered and so far the secret appears to be enabling STP on Bridge0.  I didn't notice any logged errors with BridgeD before but I'm still watching it and experimenting with different configurations.  Has anyone else noticed BridgeD silently dying up to now?</p>
<p dir="auto">Thanks in advance.</p>
]]></description><link>https://forum.netgate.com/post/201976</link><guid isPermaLink="true">https://forum.netgate.com/post/201976</guid><dc:creator><![CDATA[2low4zero]]></dc:creator><pubDate>Mon, 06 Jul 2009 21:29:01 GMT</pubDate></item></channel></rss>