<?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[Unable to communicate across VLAN&#x27;s after server reboot]]></title><description><![CDATA[<p dir="auto">I'm having a strange problem and I've checked everything I can think of.  So I'm hoping someone else might have a solution for me.</p>
<p dir="auto">I'm running 2.1-BETA1 (i386) built on Sat Feb 2 00:29:40 EST 2013</p>
<p dir="auto">I have a server on VLAN 10.200.0.x and a computer on VLAN 10.0.0.x.  When I reboot server at 10.200.0.x, I can not communicate with it after it comes back online.  If I use a computer on the same 10.200.0.x vlan I can communicate with it just fine, however no other computers on any other VLAN's can communicate with it.</p>
<p dir="auto">This only seems to happen on Linux Boxes.  Our windows servers can be rebooted and don't seem to experience this same problem.  We are using a bonded interface on Ubuntu or Debian to connect to the switch, and a bonded interface in PfSense to connect to our switch/router.</p>
<p dir="auto">I'm hoping that I'm just missing something really simple and someone could point me in the right direction, but I can't seem to find what is causing it.  Thank you in advance for any help you can offer!  I truly do appreciate it!</p>
]]></description><link>https://forum.netgate.com/topic/52689/unable-to-communicate-across-vlan-s-after-server-reboot</link><generator>RSS for Node</generator><lastBuildDate>Thu, 11 Jun 2026 09:51:33 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/52689.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 04 Feb 2013 18:08:35 GMT</pubDate><ttl>60</ttl></channel></rss>