Hey folks;
I've got an interesting one for ya. First, a photo;
Here's what I want to do with as little fuss as possible.
In the image, the red and blue networks are hooked in through two routers, out to the internet through one DSL modem. Everything is running just fine in that regard.
On the blue network is where we put our clients virus infested machines. The red network is where we keep our store computers, or machines that are known to be clean. In the middle of this setup is one machine that sits on both the red and blue network. Its a linux box called RADIUS. Its responsibilties involve being a file server for both the networks, as well as the DHCPD for the red network. RADIUS has two NIC cards in it, statically assigned, 10.1.1.254 and 192.168.1.254.
On the red network, there is also an IIS server thats got an ASP setup that we use to keep track of notes for all our repairs. When the client machines are on the red network, things run mint. Unfortunately, when on the blue, I have to go route to the internet then back into my network to get to the IIS machine (OTWServer)
My question is, when I have a client machine on the blue network, I would like to go to something like and have RADIUS talk to the IIS server on 10.1.1.254:80 and exchange all the information needed for me to do my work.
The problem I'm having is figuring out how to get the work done. I don't want to really get this machine to bridge the networks, simply for the reason that I have this network setup as such to ELIMINATE (Or damned near close to) the chance of a network savvy virus infecting our work machines.
I've tried to use SQUID but I'm just dumbfounded as to how to get it to work properly. I've used WebMin to try and get it to go, but its doing nothing but spitting out errors when I try to apply anything to SQUID.
Any other ideas or suggestions or links to a walk through on how to get RADIUS to forward TCP:83 traffic back and forth?
-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=
NEVER send the boss to do a techs job
I've got an interesting one for ya. First, a photo;
Here's what I want to do with as little fuss as possible.
In the image, the red and blue networks are hooked in through two routers, out to the internet through one DSL modem. Everything is running just fine in that regard.
On the blue network is where we put our clients virus infested machines. The red network is where we keep our store computers, or machines that are known to be clean. In the middle of this setup is one machine that sits on both the red and blue network. Its a linux box called RADIUS. Its responsibilties involve being a file server for both the networks, as well as the DHCPD for the red network. RADIUS has two NIC cards in it, statically assigned, 10.1.1.254 and 192.168.1.254.
On the red network, there is also an IIS server thats got an ASP setup that we use to keep track of notes for all our repairs. When the client machines are on the red network, things run mint. Unfortunately, when on the blue, I have to go route to the internet then back into my network to get to the IIS machine (OTWServer)
My question is, when I have a client machine on the blue network, I would like to go to something like and have RADIUS talk to the IIS server on 10.1.1.254:80 and exchange all the information needed for me to do my work.
The problem I'm having is figuring out how to get the work done. I don't want to really get this machine to bridge the networks, simply for the reason that I have this network setup as such to ELIMINATE (Or damned near close to) the chance of a network savvy virus infecting our work machines.
I've tried to use SQUID but I'm just dumbfounded as to how to get it to work properly. I've used WebMin to try and get it to go, but its doing nothing but spitting out errors when I try to apply anything to SQUID.
Any other ideas or suggestions or links to a walk through on how to get RADIUS to forward TCP:83 traffic back and forth?
-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=
NEVER send the boss to do a techs job