`<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 7, 2016 at 12:51 PM, Michael Talbott <span dir="ltr"><<a href="mailto:mtalbott@lji.org" target="_blank">mtalbott@lji.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Oh, I see. Sorry about that, reading it on my phone didn't render your diagram properly ;)<div><br></div><div>The reason this is happening is because the omnios box has knowledge of both subnets in its routing table and it always takes the shortest path to reach an ip destination.</div></div></blockquote><div><br></div><div>That's definitely the reason, but not correct when stateful firewalls are involved.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><br></div><div>So you will need to put the "clients" in a unique subnet that always passes through the firewall in both directions (in a subnet that's not shared by the omnios machines). Any attempt to add/modify a static route to the omnios box to resolve this will likely fail (it'll just move the problem from one network to the other one and cause your "services" network to route improperly).</div></div></blockquote><div><br></div><div>The problem is each person who manages these (there are 4) are also clients of the services (SMB, NFS). </div><div><br></div><div>For management, going through the firewall is fine, it is low volume, but the services need to be on the same VLAN or else the 1gb firewall will choke on the 10gb services.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><br></div><div>Either that, or remove the firewall as a hop, set sshd to listen only on the management IP, and add a management vlan interface to the clients allowed to connect.<span class="HOEnZb"><font color="#888888"><br><div><br></div></font></span></div></div></blockquote><div><br></div><div>I've considered this too, but I have some floating IP attached to zfs pools in an HA cluster that SSH needs to bind to. </div><div><br></div><div>Unless I can get the network stack on the management vlan to act independently of the other interfaces, it may come to modifying the sshd_config and restarting ssh each time a pool is started or stopped on a host. </div><div><br></div><div>-Chip</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><span class="HOEnZb"><font color="#888888"><div></div><div>Michael</div></font></span><div><div class="h5"><div><br></div><div><br><div><blockquote type="cite"><div>On Apr 7, 2016, at 10:25 AM, Michael Talbott <<a href="mailto:mtalbott@lji.org" target="_blank">mtalbott@lji.org</a>> wrote:</div><br><div><div dir="auto"><div>It sounds like you're using the same subnet for management and service traffic, that would be the problem causing the split route. Give each vlan a unique subnet and traffic should flow correctly.<br><br>Michael<br>Sent from my iPhone</div><div><br>On Apr 7, 2016, at 8:52 AM, Schweiss, Chip <<a href="mailto:chip@innovates.com" target="_blank">chip@innovates.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">On several of my OmniOS hosts I have a setup a management interface for SSH access on an independent VLAN. There are service vlans attached to other nics.<div><br></div><div>The problem I am having is that when on privileged machine on one of the vlans also on the service side that has access to the management SSH port the TCP SYN comes in the management VLAN but the SYNACK goes out the service VLAN instead of routing back out its connecting port. This causes a split route and the firewall blocks the connection because the connection never appears complete.</div><div><br></div><div>Traffic is flowing like this:</div><div><font face="monospace, monospace">client firewall omnnios</font></div><div><font face="monospace, monospace">10.28.0.106 -> 10.28.0.254->10.28.125.254 -> 10.28.125.44</font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">10.28.0.106 <--------------------------------- 10.28.0.44 </font></div><div><br></div><div>How can I cause connections to only communicate on the vlan that the connection is initiated from? </div><div><br></div><div>I don't want to use the 10.28.0.44 interface because that is a virtual IP and will not always be on the same host.</div><div><br></div><div>-Chip</div><div><br></div><div><br></div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>OmniOS-discuss mailing list</span><br><span><a href="mailto:OmniOS-discuss@lists.omniti.com" target="_blank">OmniOS-discuss@lists.omniti.com</a></span><br><span><a href="http://lists.omniti.com/mailman/listinfo/omnios-discuss" target="_blank">http://lists.omniti.com/mailman/listinfo/omnios-discuss</a></span><br></div></blockquote></div></div></blockquote></div><br></div></div></div></div></div></blockquote></div><br></div></div>
`