I worked for a NSF project. My project was my first job out of college and I knew it would fail. NSF will throw at anything and not require justification. I guess you only need a PhD to get funding.
Server example. You want 10.1.1.1 and 10.1.1.2 on the same network. 10.1.1.1 is on eth0 and 10.1.1.2 is on eth1. If you unplug eth1, you will still be able to talk to 10.1.1.1. However, if eth1 is plugged in and pingable, and you unplug eth0, 10.1.1.2 will not be accessible. The server will respond for all traffic out one interface, and not the interface that the traffic came in.
Linux doesn't support dual NICs on the same network. It is possible to do it with special drivers from Intel, but if I have 3com and Intel NICs in a machine, I can't put them on the same network.
Slashdot Mirror
This doesn't surprise me. I tried jajah and had trouble. I replaced them with rebtel.com and I'm glad I did.
I worked for a NSF project. My project was my first job out of college and I knew it would fail. NSF will throw at anything and not require justification. I guess you only need a PhD to get funding.
Server example. You want 10.1.1.1 and 10.1.1.2 on the same network. 10.1.1.1 is on eth0 and 10.1.1.2 is on eth1. If you unplug eth1, you will still be able to talk to 10.1.1.1. However, if eth1 is plugged in and pingable, and you unplug eth0, 10.1.1.2 will not be accessible. The server will respond for all traffic out one interface, and not the interface that the traffic came in.
Linux doesn't support dual NICs on the same network. It is possible to do it with special drivers from Intel, but if I have 3com and Intel NICs in a machine, I can't put them on the same network.
-Mag