Re: [cobalt-users] every added domain on wrong interface

[Josh Kuperman <josh@xxxxxxxxxxxxxxxxxx>]

On Thu, Apr 10, 2003 at 11:16:55AM -0400, Gerald Waugh wrote:
> r
> On Thu, 10 Apr 2003, Josh Kuperman wrote:
> 
> > On Thu, Apr 10, 2003 at 10:07:21AM -0400, Gerald Waugh wrote:
> > > On Thu, 10 Apr 2003, Josh Kuperman wrote:
> > >
> > >   On RaQs
> > >   eth0 is connected to the Internet.
> > >   eth1 is connected to the Intranet.
> > >   On Qubes it's the opposite.
> > >
> > Hunh??
> > 1. is this documented somewhere?
> 
>      Yes it is documented, in the RaQ and Qube manuals.

I printed out the Sun Cobalt(TM) RaQ(TM) XTR server appliance User
Manual. And so far the closest thing I can find is a reference to the
primary network. All the examples use 10.x.x.x IPs or in the DNS
appendix 192.168.x.x IPs. 

> 
> > 2. can I safely switch my entries for net1 and net2?
> 
>      If you want to admin the server without the GUI yoy
>      can do most anything.

If I wanted to admin the server without the GUI and autoupdates I
would have bought a cheap-o from TigerDirect -- which some days seems
like a good idea.
  
> > 3. can I manually alter the network-scripts?
> 
>      Sure, but using the GUI just might overwrite your changes.
> 
> > 4. shouldn't I be able to add subdomains to my intranet, too?
> 
>      Not sure, I don't think the system is setup for that, but it might
>      work.
>      The eth1 interface is normally used for backups and local traffic.
> 
>      I have setup masquerading and port forwarding on RaQs, but the
>      servers on eth1 used the server's NAT for sending and port forwarding
>      for receiving.


NAT seems to work fine regardless as does access to the sites that are
aliased on the wrong port -- this makes sense because as long as a
route is available and the machine is on the network it should work. 

Indeed if it wasn't for needing to access another site being hosted by
the same ISP, using a subnet of the same 1.2.3.x net - I would never
have noticed the misconfiguration, or that all the sites were going up
on the wrong eth. 

-- 
Josh Kuperman                       
josh@xxxxxxxxxxxxxxxxxx