Crazy Idea. Hopefully someone has some guidance.
I go to college, and for some reason, my University has decided to cap ALL upload ports to 10kbs. As I know all of you agree, 10kbs is nothing, can't work with that. After many failed tries, they refuse to change my cap, however, I can register as many comps (nics) to the DHCP as I want.

So I got around to thinking:
Bonding, Clustering.
Clustering involves multiple computers being controlled by 1 central computer, Bonding involves making multiple NIC's act as one large NIC.
If each NIC is capped at 10kbs, you can see what I'm getting at.

Is there any way to do the following:
Have 6 NICs on 1 comp, when a request comes into one of them, have all 6 start acting.
Example: Someone connected over HTTP or FTP asks for file1.bin. The request comes into NIC1. Instead of NIC1 sending the file back, NIC1 sends back the first piece, NIC2 sends the 2nd piece, NIC3 the 3rd, etc. Esentially giving me 6x the upload bandwidth. The hard part I can see is convincing the person who originally sent the request packet that all the file pieces were coming back from the same place (all have different IPs).

Is there any sort of way to IP spoof so the recipient's comp deals with this correctly?

Option 2 I dont think works, but I'll post it anyhow:
Bond the 6 network adapters together. The problem here is they bond to the same IP as far as I know, which would just get capped.


Anyone have any thoughts? Or any other ideas?
Or even other crazy plans?

I'll be paying attention to this post. Oughta be entertaining to say the least !

LOL

lol, whats that supposed to mean? =P

Just saying the solution to your problem oughta be interesting.. I doubt that you can have all the network cards spoof their identity due to router problems. But it's funny that you're attempting it. I say go for it. If you figureit out, I know a lot of people would love to read the HOWTO on it. :-)

Seems like it should be possible. I think its more of a HTTP/FTP problem than a linux one. But for some reason i cant find an HTTP/FTP forum =P
Plus, the guys here are always helpful.
Shouldn't it just be able to edit the outgoing packets to spoof the different IP?
Would the client accept that?

Edit:
Added thought: What about a messed up NAT system?

Edit #2:
Looking into modifying packets more (and by more, i mean, more than the zero knowledge I had before), TCP packets (HTTP/FTP) they have a constant open socket. Being that these network cards would be on the same computer, is it possible to share the socket connection?

nobody?
I also heard if this doesn't work, theres apparently an easy way to run multiple connection streams (to different people) so I could host X number of people at the capped 10kbs each.
Anyone have anywhere to point me for this (apache)

Typically when you want to do bonding where each NIC communicates simulatenously for a single connection, then you need to also have the bonding done on the switch end of the cable as well.

yeah, thats what i had read..
hmmm

You should be able to do this with the Linux Advanced Routing & Traffic Control HOWTO:
http://lartc.org/howto/

awesome, dont have time right now to check it out, but thanks a ton for the link. You can be sure ill read it over =P

hmmm, gave it a good once-over, but didn't find anything that really seemed to be what I wanted...
Ill check it again tomorrw (might just be too late at night)
did you see anything in specific? or just thought that doc would be helpful?

More specificly this section is what you are probably looking for:
http://lartc.org/howto/lartc.rpdb.multiple-links.html

Particularly the second section however the first section is required so I would just read the whole page - it isn't that long .

Hmmm, looks to be EXACTLY what I want. All I need to know is...
Say someone sends a request to IPAddy1, and through load balancing the response gets sent out IPAddy2. Will the client who sent the initial request experience any problems dealing with a response coming from a different IPAddy?

That shouldn't happen.

hmmm, problem is then I need the requests to get evenly spread out...
bringing me back to my original problem...