Re: [[cobalt-users] Cobalt RaQ behind firewall]

["Dylan Smith" <dyls@xxxxxxx>]

> > How did the transition of placing your RAQ behind a firewall with NAT
> go???
> > I'm thinking of doing the same.
> >
> > Robyn L. Nixon
>
> Robyn
>
> I don't know how it went for him, but, I have mine sitting pretty on
> 192.168.10.240 with no problems.

The RaQ shouldn't be different to any other system, and should work fine on
the inside. My home setup is a Linux system (Debian, kernel 2.4.5) which is
doing NAT for the internal network (it has 2 ethernet cards - an RTL (forget
the model number) for the inside, an onboard 3com 59x for the outside) The
internal network is Linux and Windows. Both work flawlessly. Even Starcraft
(which uses UDP) works fine from the inside. I have a number of iptables
rules on the NAT router system to act as a firewall and block outside access
to anything that I only want the internal network to get at (since the NAT
router system is a server too). The NAT system also runs a dhcp client on
eth0 to get its IP address, and runs a dhcp server on eth1 to give internal
machines their own address (although my workstation has a static IP - dhcp
is for guests so they don't have to mess with their settings).

The NAT system has some iptables rules to forward certain ports to machines
on the inside (such as port 80 for http). For a RaQ, if you want access to
the admin pages from the outside, don't forget to forward port 81.