Re: 1st:Sharing ; 2nd:Freezing

[Chuck Yerkes <chuck+obsd_(_at_)_2003_(_dot_)_snew_(_dot_)_com>]

Quoting Alexander Farber (Alexander_(_dot_)_Farber_(_at_)_t-online_(_dot_)_de):
> On Thu, Apr 17, 2003 at 08:03:36AM -0700, Bogdan wrote:
> > b&b_server# cat hosts
> > ::1 localhost.my.domain localhost
> > 127.0.0.1 localhost.my.domain localhost
> > 192.168.0.31 b&b_server.my.domain b&b_server
> > 10.0.1.1 b&b_server.my.domain b&b_server
> > 10.0.1.2 shoshonel.my.domain shoshonel
> > 10.0.2.1 b&b_server.my.domain b&b_server
> > 10.0.2.2 bulinuta.my.domain bulinuta
> 
> Wow... have you tried the same setup with a less weird hostname?

Oh yeah, you have the SAME (illegal) hostname for 3 interfaces.
This is going to cause you problems.

1) _ is not allowed in a hostname.
2) & is not allowed in a hostname.
3) each INTERFACE should have a unique (legal) hostname.

so if you try THIS:
192.168.0.31 b-n-b-server.my.domain b-n-b-server
10.0.1.1     b-n-b-server1.my.domain b-n-b-server1
10.0.2.1     b-n-b-server2.my.domain b-n-b-server2

You will not be breaking naming rules and have something
more sensible.  Once you have a normal starting point,
things may work better.

I'm also a HUGE fan of cheap, 4 port hubs rather than
crossover cables.


And make sure your netmasks are correct for those DMZ nets.
10.0.2.1 wants 255.255.255.0, I'd guess.
Though I might just use ONE class C and a 29 bit netmask there
(1 net, a broadcast, 6 hosts).
hosts for two networks could be 
192.168.1.1-6 /255.255.255.248  and 
192.168.1.9-14/255.255.255.248

But that's just cause I know networking.