2007/7/17, Craig White <craig@xxxxxxxxxxxxx>:
On Tue, 2007-07-17 at 22:37 +0200, antonio montagnani wrote:
> 2007/7/17, Frank Cox <theatre@xxxxxxxxxxx>:
> > On Tue, 17 Jul 2007 17:24:45 +0200
> > Manuel Arostegui Ramirez <manuel@xxxxxxxxxxxxxx> wrote:
> >
> > > subnet 192.168.1.0 netmask 255.255.255.0 {
> > > range 192.168.1.100 192.168.1.150;
> > > option broadcast-address 192.168.1.255;
> > > option routers 192.168.1.1;
> > > #option domain-name "YOURNET";
> > > option domain-name-servers 213.172.33.34;
> >
> > Some stuff will fail without "next-server" as well.
----
I don't think so but if you want to educate me on why you believe this
to be true, by all means...
----
> >
> Tnx to all for help: I arranged to use the following dhcp.con f file,
> I guess that is not very different from Manuel's...: but I am fully
> un-expert of DHCP (and may others subjects!!!)
>
> # option subnet-mask 255.255.255.0;
> ddns-update-style none;
> subnet 192.168.0.0 netmask 255.255.255.0 {
> range 192.168.0.200 192.168.0.250;
> option subnet-mask 255.255.255.0;
> option broadcast-address 192.168.0.255;
> option routers 192.168.0.1;
> #option domain-name-servers 62.211.69.250, 212.48.4.15;
> #option domain-name "podzone.net" ;
> default-lease-time 604800;
> max-lease-time 2592000;
> }
----
it seems silly to use DHCP and not provide DNS server addresses as all
of the computers on the LAN would probably be well served by using the
same DNS Server
maybe, but it is an operator's choice: please note that usually DHCP
is not running on my home network, all IP's should be very well known
in a home network, shouldn't they??
DHCP was started only because a DHCP server was required by SC101.
----
> For your information we inserted a SC101 Netgear storage device: no
> way to have it working in a Linux environment (and also you need to
> install his software on each windows computer on a network), even if
> it gets a IP number from my Linux DHCP server. But Netgear clearly
> stated that only Windows is supported.
----
Linux does Windows...it's called samba
Sorry, but SC101 in a Linux environment is not seen, the device has a
strange file system, it is seen as a computer resource also under
Windows, not as a Network resource: anyway, scope of starting DHCP was
to have IP's numbers broadcasted on the network, and to check if at
least in a Windows network device was running fine.
It seems silly to use devices that don't support NFS but SMB/CIFS
protocols are supported easily enough with samba. It should be
reasonably trivial to get Linux to connect to that device.
--
Craig White <craig@xxxxxxxxxxxxx>
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
tnx Craig for your comments
--
Antonio Montagnani
Skype : antoniomontag
