[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[cobalt-users] every added domain on wrong interface



I solved the immediate problem when, I realized after issuing an
netstat -nr command that I had an invalid route.

As best I can tell my problems came about as follows: 

I set up my private network, the 192.168.1.x space, on eth0 or Network
1. I set up my, exposed to the world network on eth1 or Network2. My
private network settings were IP-192.168.1.1 and
Netmast-255.255.255.0. My exposed to the public settings, for my first
registered domain were, using the fake numbers from below, IP-
1.2.3.194 Netmask-255.255.255.240. 

So later when I added another subdomain to my DNS and created
1.2.3.195, instead of it being aliased as eth1:0, it was aliased as
eth0:0. It took the netmask from the other eth0 ip. This created a
1.2.3.0/24 network that was added to the routing table. I manually
deleted the insane route which means I can now access legitimate sites
on other networks like 1.2.3.71.

So, where is the documentation that I missed that says everytime you
add a site it goes on eth0 and not eth1? Why can't I use both, why
can't I specify? I can't find anything much -- I did print out the
docs and have been pouring over them honest. Can is just go in and
change the ifcfg-eth0:0 entries to ifcfg-eth1:0 entries? Can I just go
and swap make my network 1 and my network 2 entries?



On Tue, Apr 08, 2003 at 09:56:14PM -0400, Josh Kuperman wrote:
> This is weird and I'm not sure why it happens.  The gist (not the
> actual ip addresses or domains) is that I have 1.2.3.192-207 and he
> has 1.2.3.64-127. I have a.org and he has b.org. I cant view
> www.b.org, because the lookup times out. Basically we have the same
> ISP and he has given us, as his custromers, a subnet to use. Nslookup
> fails when I from the RaQ XTR home to a.org, try to get to lookup
> b.org.

-- 
Josh Kuperman                       
josh@xxxxxxxxxxxxxxxxxx