gutsy and regular PCs on edubuntu lan

[Philippe Rousselot]

hi david ,

David Van Assche a écrit :
> Hi,
>     Apart from that, it's really not hard to install both dansguardian 
> and some firewall like shorewall and manage both (and other aspects of 
> the server) with Webmin, 
I am sorry to disagree but as I said before, the level of most people I 
know is enought to install the system, update it, but not really more, 
and with or without webmin

> which for all the negative attention I've seen it get in the ubuntu 
> forums, is not such a bad tool for those of us wanting gui tools as 
> well as the command line. 
i entirely agree, webmin is a great tool

> Anyway, the problem mentioned above sounds like nating... I have the 
> same setup here, some thin clients and the rest being normal computers 
> connecting to the lan, and they all, windows machines too, get dhcp 
> and internet from the server.
I really would like to see your config as I have some problem to set-up 
mine.

Thanks,

All the best

Philippe
>
> Kind Regards,
> David
>
> On 10/30/07, *Gavin McCullagh* <gmccullagh at gmail.com 
> <mailto:gmccullagh at gmail.com>> wrote:
>
>     Hi Philippe,
>
>     On Tue, 30 Oct 2007, Philippe Rousselot wrote:
>
>     > It is apparently impossible (out of the box) to get regular PCs
>     > connected to the edubuntu lan to access internet. it is only
>     possible
>     > for thin clients.
>
>     There are (as I understand it) two possible network topologies for
>     edubuntu:
>
>     1. Single network interface.  Edubuntu and all thin clients sit on
>     the main
>        network like all other machines.  Edubuntu runs dhcp for all
>     machines,
>        and thin client services for thin clients.
>     2. Two network interfaces.  Edubuntu sits on the main network,
>     thin clients
>        sit behind it, connected by a separate switch to its second network
>        interface.
>
>     In [1], all machines can see the internet directly.  In [2], you
>     can put
>     your desktops directly on the main network and they will get internet
>     access _or_ put them behind the edubuntu server which must then have
>     ip_forwarding switched on.
>
>     It's possible the above situation has changed recently.  I'm open to
>     corrections if it has.
>
>     > remarque: as the primary vocation for edubuntu is to be used in
>     schools,
>     > it is quite domageable not to get out of the box  :
>     >     1. parental control with GUI to modify white/black list
>     >     2. access to internet for regular PCs connected to the server
>
>     What you seem to be describing here is a firewall/content
>     filtering server.
>     Edubuntu (again, as I understand it) provides a desktop OS for
>     schools, not
>     a firewall.  You probably don't want to plug things together as
>     though it
>     were the firewall and it doesn't attempt to provide content filtering
>     (which is usually best done at/near the firewall).
>
>     I would suggest a firewall/filtering product is required for this
>     need.
>     Maybe edubuntu should try to provide it, I don't know, but the current
>     product is really not aimed at that.
>
>     ... or such is my understanding.
>
>     Gavin
>
>
>     --
>     edubuntu-users mailing list
>     edubuntu-users at lists.ubuntu.com
>     <mailto:edubuntu-users at lists.ubuntu.com>
>     Modify settings or unsubscribe at:
>     https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
>
>