[Omega_Shadow]

Simply put, got a computer with two nic cards; one connected to the router, my home network and the internet. Then other, connected to an auxiliary computer in my room for testing and experimentation. I want the auxiliary computer to access the internet as well as the local network. So far, after running the internet connection sharing wizard in the control center of the "gateway" pc, I can't get aux to connect to squat.

Any ideas?

"gateway" OS:
PCLinuxOS .93a BigDaddy

[drgoodtrips]

Originally Posted by Omega_Shadow

Simply put, got a computer with two nic cards; one connected to the router, my home network and the internet. Then other, connected to an auxiliary computer in my room for testing and experimentation. I want the auxiliary computer to access the internet as well as the local network. So far, after running the internet connection sharing wizard in the control center of the "gateway" pc, I can't get aux to connect to squat.

Any ideas?

"gateway" OS:
PCLinuxOS .93a BigDaddy

I take it you want to be able to use the "gateway" box as more than just a glorified router? If not, there are tiny Linux distributions that you can put on the box, which actually allow Windows configuration the way a router you purchase at Circuit City might.

If you want to use the box, I imagine that you'll need to use the "ipchains" command. I believe something like:

ipchains -A input -i <your second NIC interface i.e. eth1> -s <your test box ip> -d <your router ip> -j ACCEPT

is a good starting point. I don't remember if that will accomplish what you want on its own, or if you also have to tell it separately to forward. From there, you can simply configure your test box to connect to your router's IP, as per normal. Linux will see those requests and pass them along, provided they're from the test box's static IP.

(Note - I might not have the ipchains syntax right off the top. You can either consult the man pages or, if it doesn't exist, download it. I think most Linux distributions include it)

[Omega_Shadow]

Yeah, don't want to turn my primary computer into just a router

Will try ipchains. If you find out anymore info I would love to hear about it. Even if I can't use the info right away I like learning about networking.

[Squashman]

I am confused. If you have a router, why not just connect everything to the router.

[Omega_Shadow]

Router is full. Only has four ports for cat5 and this test computer is not worth going out and buying a wireless adapter or a new router. Just some old POS I put together from parts I had laying around.

Not to mention it gives me the chance to learn some more about networking with linux

[fenderfreek]

Try using Firestarter in gnome, or maybe Kmyfirewall in KDE. I haven't used the latter much at all, but it seems more full featured. Both are GUI ipchains/iptables editors, so you can use them for routing/firewall configuration. Kmyfirewall has a nice little wizard and all sorts of tools to make configuration a lot easier, though I'm rather unfamiliar with it, so I can't give you any specifics.
Routing and firewall config from the console isn't something I do much, almost never really, but using a GUI makes it go a lot more quickly since I don't have to learn new command and syntaxes.

[Squashman]

Originally Posted by Omega_Shadow

Router is full. Only has four ports for cat5 and this test computer is not worth going out and buying a wireless adapter or a new router. Just some old POS I put together from parts I had laying around.

Not to mention it gives me the chance to learn some more about networking with linux

I would be you could pick up an old hub or switch for under $10, maybe even cheaper.

[Omega_Shadow]

But what's the fun in that?

Thanx fenderfreak. Will try that when I get home. Right now I am fighting my windoze work computer

[Omega_Shadow]

at first I thought it wasnt working but then I realized I didnt have a crossover cable going to have to pick up an adapter or make a cable in the morning. The simple mistakes are the ones that hurt the pride the most