10 DRK to the person who can solve this Linux networking problem for me!
I have six masternodes running on one T2.medium using chaeplin's excellent guide which can be found here
https://darkcointalk.org/threads/ec2-multiple-remote-nothing-mn-max-5.1660/
Both CPU and network resources are underutilised and I have plenty of spare elastic IPs in the same region so I would like to run a few more masternodes on the same instance.
The problem is that you can only bind a maximum of 6 private IPs to a T2.medium network interface. I have tried creating a second network interface and attaching it to the same instance but unfortunately it appears that by default all traffic received by the second interface (eth1) is forwarded to and dropped by eth0.
This is how I want a T2.medium to work:
¦ User Proc ¦
nm01 darkcoind <-> eth0 <-> PrivIP <-> EIP
nm02 darkcoind <-> eth0 <-> PrivIP <-> EIP
nm03 darkcoind <-> eth0 <-> PrivIP <-> EIP
nm04 darkcoind <-> eth0 <-> PrivIP <-> EIP
nm05 darkcoind <-> eth0 <-> PrivIP <-> EIP
nm06 darkcoind <-> eth0 <-> PrivIP <-> EIP
-------------------------------------------------------------- theoretical networking wall!
nm07 darkcoind <-> eth1 <-> PrivIP <-> EIP
nm08 darkcoind <-> eth1 <-> PrivIP <-> EIP
nm09 darkcoind <-> eth1 <-> PrivIP <-> EIP
nm10 darkcoind <-> eth1 <-> PrivIP <-> EIP
nm11 darkcoind <-> eth1 <-> PrivIP <-> EIP
Can anything be done with static routes to allow this to happen? I think need to learn how to enable eth1 in linux and then set up routes to ensure that traffic is handled symmetrically. I.e traffic received in to eth1 is processed by the appropriate user darkcoind instance and routed back out through Eth1 and subsequently the correct IP.
You'll probably want to read chaeplin's guide (linked above).
So...any ideas?
First person to provide info that actually helps me solve it gets the bounty.
I have six masternodes running on one T2.medium using chaeplin's excellent guide which can be found here
https://darkcointalk.org/threads/ec2-multiple-remote-nothing-mn-max-5.1660/
Both CPU and network resources are underutilised and I have plenty of spare elastic IPs in the same region so I would like to run a few more masternodes on the same instance.
The problem is that you can only bind a maximum of 6 private IPs to a T2.medium network interface. I have tried creating a second network interface and attaching it to the same instance but unfortunately it appears that by default all traffic received by the second interface (eth1) is forwarded to and dropped by eth0.
This is how I want a T2.medium to work:
¦ User Proc ¦
nm01 darkcoind <-> eth0 <-> PrivIP <-> EIP
nm02 darkcoind <-> eth0 <-> PrivIP <-> EIP
nm03 darkcoind <-> eth0 <-> PrivIP <-> EIP
nm04 darkcoind <-> eth0 <-> PrivIP <-> EIP
nm05 darkcoind <-> eth0 <-> PrivIP <-> EIP
nm06 darkcoind <-> eth0 <-> PrivIP <-> EIP
-------------------------------------------------------------- theoretical networking wall!
nm07 darkcoind <-> eth1 <-> PrivIP <-> EIP
nm08 darkcoind <-> eth1 <-> PrivIP <-> EIP
nm09 darkcoind <-> eth1 <-> PrivIP <-> EIP
nm10 darkcoind <-> eth1 <-> PrivIP <-> EIP
nm11 darkcoind <-> eth1 <-> PrivIP <-> EIP
Can anything be done with static routes to allow this to happen? I think need to learn how to enable eth1 in linux and then set up routes to ensure that traffic is handled symmetrically. I.e traffic received in to eth1 is processed by the appropriate user darkcoind instance and routed back out through Eth1 and subsequently the correct IP.
You'll probably want to read chaeplin's guide (linked above).
So...any ideas?
First person to provide info that actually helps me solve it gets the bounty.
