Private in-house domain

[Bill McGonigle]

On May 15, 2007, at 16:47, Tech Writer wrote:

> Does anyone have any ideas why this might be?  Is it possible that  
> my routes or gateway need to be updated now that I've switched from  
> a 192.168.1.n address to the 10.25.1.n address?   If so, what needs  
> to be changed?

Two things I can think of.  First is look at:

   /etc/sysconfig/network

there's probably a:

   GATEWAY=

line in there.  If not, come back here - you might have per-interface  
route configuration files (more icky).

Oh... now actually looking at your files, I see you have a GATEWAY=  
in the ifcfg-eth0 file.  I haven't done it that way before - do you  
know that's valid?

Next, is how you're going to route.  This isn't so much linux setup  
but network design.,

The GATEWAY= you have in ifcfg-eth0 is:

   192.168.1.1

which isn't on your subnet.  So how does a packet get to  
192.168.1.1?  That's undefined.  Ordinarily you just send anything  
that you don't know how to get to to your default route, which is  
through your GATEWAY.  But this is a chicken-and-the-egg thing - it  
doesn't know how to get to your GATEWAY=.

You could setup one of those 'icky' route files with a static route  
to tell it how to get there, but if it were my network (yours is  
really similar to my home network) I'd set the internal address on  
the Linksys box to 10.25.1.10 rather than 192.168.1.1 and configure  
that as your GATEWAY.

To see the routing table do:

   netstat -nr

The syntax takes some studying, but once you learn it it makes alot  
of sense.

-Bill

-----
Bill McGonigle, Owner           Work: 603.448.4440
BFC Computing, LLC              Home: 603.448.1668
bill at bfccomputing.com           Cell: 603.252.2606
http://www.bfccomputing.com/    Page: 603.442.1833
Blog: http://blog.bfccomputing.com/
VCard: http://bfccomputing.com/vcard/bill.vcf