Mark,
ipforwarding is set to "yes" by default, but i don't think this is
the problem. i still think that the networks are connected somewhere else.
those things can be very insidious. if you can check with full assurance
that there is no connect, then we have a real problem. i'd go with
disconnecting everything but 1 hub per connection and start with 1 station
per hub. keep adding, until you get an erroneus address assignment. when
that happens, disconnect the last wire and continue. this wire most
probably has a connect to the other network.
ipforwarding is rather needed - getting on the 'net from private
segment and so on ...
good luck, julius
On Mon, 4 Feb 2002, Mark Howe wrote:
> Le Dimanche 3 Février 2002 20:34, Julius Szelagiewicz a écrit :
>
> > first, you seem to have to separate networks running on comon wire
> > - not good but it would explain addresses from the "wrong" network.
> > second, dump the hub (use it dowstream) and replace it with a switch.
> > third, my quoted message should read: "make sure that suse dhcpd server is
> > not trying to serve addresses on the wrong segment by physically
> > separating the segments". good luck, julius
>
> Sorry for being slow here, but I thought I *had* physically separated the two
> networks: I have two network cards in the server, one of which is connected
> to each network, so I'm not clear how traffic is getting from one to the
> other. (Well, actually, it's blindingly obvious that it is crossing over via
> the server, unless we have moved from X-Windows to X-Files, but I have no
> idea why).
>
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.openprojects.net
