<div>
The issue is with the routing table where .8 is seen as the primary interface such that traffic arrives on .9 while when leaving the path is via em0<br />
netstat -rn<br />
Depending on your resources you could use bond to bind the two interfaces to appear as one.<br />
If you are using sfw iptables firewall, you would need to setup rules that will tag the packets and thus maintain the path for the outgoing packet if binding the two interfaces is not an option.
</div>


The issue is with the routing table where .8 is seen as the primary interface such that traffic arrives on .9 while when leaving the path is via em0
netstat -rn
Depending on your resources you could use bond to bind the two interfaces to appear as one.
If you are using sfw iptables firewall, you would need to setup rules that will tag the packets and thus maintain the path for the outgoing packet if binding the two interfaces is not an option.

<div>
Is there no way to tell the traffic to leave on the interface it came in on?
</div>


Is there no way to tell the traffic to leave on the interface it came in on?

<div>
Many thanks, I will give it a go and report back.
</div>


Many thanks, I will give it a go and report back.

<div>
Thanks this resolved the issue.
</div>


<div>
<div class="content wysiwyg-content">
Hi all<br />
<br />
I am having an odd issue with my Freenas server, It is setup as such:<br />
<br />
Two network interfaces<br />
&nbsp;<br />
EM0 - 192.168.0.8<br />
EM1 - 192.168.0.9<br />
<br />
I have an ESX box that connects to an iscsi target that ONLY runs on 192.168.0.8, it is disabled on 192.168.0.9.<br />
<br />
I have samba setup on the box as well. <br />
<br />
Now, I am copying files on a box to a samba share via 192.168.0.9.<br />
<br />
Although looking at the interface graphs, It seems as though RX is being done by 192.168.0.9 and TX is being done by 192.168.0.8, I have attached the bandwidth graphs.<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2012/03_w12/562560/Capture.PNG" target="_blank" title="Bandwidth Graphs (34 KB)"><img alt="Bandwidth Graphs" class="file-block lazyload" style="max-width: 537px;" data-src="https://filedb.experts-exchange.com/incoming/2012/03_w12/562560/Capture.PNG" /></a>
</div>
</div>


Capture.PNG

Hi all

I am having an odd issue with my Freenas server, It is setup as such:

Two network interfaces
 
EM0 - 192.168.0.8
EM1 - 192.168.0.9

I have an ESX box that connects to an iscsi target that ONLY runs on 192.168.0.8, it is disabled on 192.168.0.9.

I have samba setup on the box as well. 

Now, I am copying files on a box to a samba share via 192.168.0.9.

Although looking at the interface graphs, It seems as though RX is being done by 192.168.0.9 and TX is being done by 192.168.0.8, I have attached the bandwidth graphs.



Freenas odd network loading

The variety of Linux distributions creates myriad issues relating to configuration and operations when computers are networked, not the least of which is the use of various network management applications, some of which are included with specific distributions, while others are standalone applications.

Linux Networking

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.

Network Management

Operating systems perform basic tasks, such as recognizing input from the keyboard, sending output to the display screen, keeping track of files and directories on the disk, and controlling peripheral devices such as disk drives and printers. For large systems, the operating system makes sure that different programs and users running at the same time do not interfere with each other. The operating system is also responsible for security, ensuring that unauthorized users do not access the system. Operating systems provide a software platform on top of which other programs, called application programs, can run.