Erm, not quite no!
Going by how I read your post, and I appologise if I am missing something, you want to have NIC1 talkign to the internet and NIC 2 talking to the switch and yet you have both NICs connected to the switch.
That is assuming the router is directly in the same room as the machine but is connected to the switch which also provides connectivity for other machines. I have no wish to force all the other machines to go through this machine in order to access the internet.
I simply said or meant, that you should have one NIC talking to the MODEM and the other talking to the Switch. Then the one thats talking to the switch, if you enable ICS on that, it will allow any7 other PCs that are connected to the switch, to also communicate with the outside world via ICS on NIC1
Yep, I understand what you are suggesting but have no wish to force all internet connectivity through a single machine especially as that machine is streaming HD content internally at the same time to a number of other machines / head units.
Ok, So, its a gigabit NIC, other than, I have to ask... So what?
In order to make full use of that, you also need any other devices plus your switch to also be gigabit, and I will assume they all are, but again, so what? All NICs can go at the lower speeds, so it makes no difference.
Im confused?
The Intel NIC is a far more robust NIC than the other one. It handles the load on the NIC rather than via the processor and can handle link aggregation. The other NIC does and cannot. I would like the full 1Gbit bandwidth to be available to the internal subnet regardless of what information is being sent back and forth to the internet from the same machine or from others (give or take bandwidth usage due to internet traffic on the switch).
Oh, ok, so now you are getting clearer, but again, why would you want to double the bandwidth and then set each NIC to a different task?
Isnt that pretty much the same as setting up a RAID array and then wanting access to the individual drives instead of the array?
Yes it would be which is why I would not aggregate and then use for separate tasks. The idea is to prevent any internet bandwidth affect, at a NIC level on the same machine, from interfering with transfers on the internal subnet coming from this machine.
I see. I think?
But the idea still really does confuse me.
I clearly cannot help you here, but I have to know why you are trying this?
As you said, you want to tie them up to make a 2GB connection, but then set one to be WEB and one to be LAN )
Can you not see how this sounds?
Dont get me wrong, but that to me, really does sound a bit nutty.
unless of course your internet is a 1GB internet package and then why tie them up in the first place only to then split them up again?
Confused???
I can see why you are confused. Nope just looking to route all internet traffic to and from this machine via a dedicated NIC and all internal subnet traffic via another dedicated NIC so bandwidth usage on either NIC does not affect the other. The switch can handle the usage of internet and subnet traffic.
It is partly for segregation of tasks, data . The
other option would be to bond the NICs and just have a 2Gb virtual NIC. For this to work I would have to get another Intel 1000/Pro as the second one I had 'got damaged'
...
So in essence. Machine provided HD content to a number of other machines / head units. Machine also provides some internet duties. I don't want the machine as a single point of failure for all internet connectivity. I don't want internet activity to have an effect on transfers to/from the local subnet. I do appreciate that the disks and their attainable IOPS will have a big affect but there is nothing I can do about that at the moment.
Thanks
RB
.