[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: MSS100 and CBus (was: How many PCs do you have at home?)
- Subject: RE: MSS100 and CBus (was: How many PCs do you have
at home?)
- From: Shane Harrison <shane.harrison@xxxxxxxxxxxxxxx>
- Date: Wed, 01 Sep 2004 08:27:08 +1200
Another approach is to use DHCP to always allocate the same IP address.
Just
set the DHCP server to map an IP to a certain MAC. While on the face of it
it seems to invalidate much of the DHCP advantage it does give centralised
control of the IP addresses - using DHCP in this manner is recognised in
the
DHCP specification. Furthermore the DHCP server conf file can be a record
of what fixed addresses have been allocated rather than keeping these
recorded somewhere else.
Shane
> -----Original Message-----
> From: Kevin Hawkins [mailto:lists@xxxxxxx]
> Sent: Tuesday, 31 August 2004 10:34 p.m.
> To: ukha_d@xxxxxxx
> Subject: RE: [ukha_d] MSS100 and CBus (was: How many PCs do you have
at
> home?)
>
>
>
> > -----Original Message-----
> > From: Frank Mc Alinden [mailto:fmcalind@xxxxxxx]
> > Sent: 31 August 2004 10:00
> > To: ukha_d@xxxxxxx
> > Subject: Re: [ukha_d] MSS100 and CBus (was: How many PCs
> > do you have at home?)
> >
> > Thanks for that Paul
> > Of course it was a piece
> > of cake for me ...as normal i had probs but i think i got
> > it set up ok now.....In the server / tcp ip setups i
> > unticked the DHCP etc ??? hope thats correct.......Will
> > find out next time i reboot........
>
> Hi Frank,
>
> The address that is setup there is the address the unit will occupy
> even if rebooted (provided DHCP is disabled) - there is one thing
that
> might be an issue still though . The 'residual' address there may
> be the one
> that was allocated last time the unit booted using DHCP - and if so it
is
> now a static IP address but still in the range of the DHCP
> allocation. What
> I mean by this is that your DHCP server has a 'pool' of addresses it
can
> allocate and you should never use these addresses as fixed
> addresses as they
> could conflict with dynamic allocated addresses. Do you know the range
of
> addresses that you DHCP server hands out ? (I don't know what your
DHCP
> server is) - if so if the new MSS100 address is within that range
> then move
> it somewhere just outside of it - any address will do as long as it
is
> UNIQUE on your network - but ONLY change the last group of digits
though -
> the ones at the right hand end ...
>
> eg if the address is currently 192.168.1.240 and your DHCP server
> allocates addresses 192.168.1.230 to 192.168.1.250 say then move the
unit
> to 192.168.1.229 (as long as this address is not already in use). You
can
> see if an address is currently free by 'pinging' it and if there is no
> reponse then it is not currently in use. It is a good idea to
> keep a little
> note of all your static IP addresses somewhere so you can
> allocate them more
> easily and without conflicts. People tend to group similar
> devices or areas
> by address so for example addresses between 192.168.1.10 and
192.168.1.19
> may be PC's and addresses between 192.168.20 to 192.168.1.29 may be
Rio
> audio players . The gateway often tends to occupy the .1 address eg
> 192.168.1.1
>
> Having said all this if it works and you are uncomfortable with
> further changes then leave it as is - if later you experience any
problems
> with the device or a new device you add that uses DHCP then bear in
mind
> this may well be the issue.
>
> Kevin
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
UKHA_D Main Index |
UKHA_D Thread Index |
UKHA_D Home |
Archives Home
|