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

Re: Network Card Strangeness



On Tue, 26 Oct 2004 13:00:22 +0100 (BST), Jonathan Allen
<jonathan barumtrading co uk> wrote:
> Paul,
> 
> Sorry for the delay in responding to this; putting out fires in another
> part of the forest.
> 
> > Do you have the appropriate aliases for eth1 and eth2 in /etc/modprobe.conf?
> >
> > alias eth1 tulip
> > alias eth2 tulip
> 
> Yes - all four NICs have entries:
> 
>    alias eth0 tulip
>    alias eth1 tulip
>    alias eth2 tulip
>    alias eth3 sk98lin
> 
> Any other ideas why eth1 and eth2 don't load properly ?
> 
> > The router should have a separate IP address for each interface, in the IP
> > address range for the segment it is on.
> 
> That sparked a lot of discussion in another place, with people agreeing
> with you and others disagreeing.  While some agree that you are right in
> principle, others say that they have running systems that seem to work
> quite satisfactorily.
> 
> My principle concern is that the machine that is bridging these segments
> needs to be known by only one IP address across the whole LAN and that
> there is only one DNS on the network, and which is not on this machine
> but on the segment that links to the Internet.
> 
> Jonathan

You mention bridging and routing which are you doing?  If you are
doing both than you need to specifi which interface is doing what.  If
you are bridging then the computeres on each bridge segment can't
comingle the physical connections with a hub or switch (unless the
switch is set up for VLANs).


-- 
Leonard Isham, CISSP 
Ostendo non ostento.


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