home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
HTPC Projects
Hardware
Communication
Network speed problems
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="SpudR" data-source="post: 920902" data-attributes="member: 54104"><p>Sorry - came late to this but the details seem fine.</p><p>Personally I usually config networks to the following (Class C addresses (or /24) subnet mask of 255.255.255.0):</p><p> </p><p>First 9 addresses (in your case 192.168.1.1 - 1.9 for server based stuff (usually the main server at 1.1) that leaves 9 adresses for other 'servers'</p><p>Next 89 addresses to use for network devices - 192.168.1.10 - 1.99 - this for managed switches, printers, etc</p><p>Next 149 addresses for client PCs - 192.168.100 1.249</p><p>Last few Addresses 192.168.1.250 - 1.254 for Network Infrastructure (router(s) bridges etc.)</p><p> </p><p>DHCP scope set to allocate from 192.168.1.100 - 1.250 only, That means that you don't need to allocate reservations or fixed IPs to certain network devices in the longer run, as clients will always get IPs that don't clasj with other network critical things.</p><p>Static addresses for the other stuff so they are all outside the scope of the DHCP range.</p><p> </p><p>This also has the additional benefit that if there is a problem and it's an pinned down to an IP address, I know what type of device I'm looking at as the culprit - i.e. if the Ip address is hogging the bandwidth of the broadband and it in the range of 1.100 to 1.250, I know there is a client out there causing a problem.</p><p> </p><p>In your case Id allocate the router to 192.168.1.254</p><p>Switch to 192.168.1.10</p><p>'Server' PC (main MP server) to 192.168.1.1</p><p> </p><p>Something to think about though is if you are going to use any VPNs you'll need a different IP range than that of the remote network, As most routers will allocate an internal IP range as 192.168.1.x I'd suggest changing to something a little different - use a 172.168.1.x range instead.</p><p>Phew!</p><p> </p><p>That must be the longest post I've done for a while! Hope it's of some use <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /></p><p>It's also late and I've downed a bottle of wine so forgive me if the IP counts don't match!</p></blockquote><p></p>
[QUOTE="SpudR, post: 920902, member: 54104"] Sorry - came late to this but the details seem fine. Personally I usually config networks to the following (Class C addresses (or /24) subnet mask of 255.255.255.0): First 9 addresses (in your case 192.168.1.1 - 1.9 for server based stuff (usually the main server at 1.1) that leaves 9 adresses for other 'servers' Next 89 addresses to use for network devices - 192.168.1.10 - 1.99 - this for managed switches, printers, etc Next 149 addresses for client PCs - 192.168.100 1.249 Last few Addresses 192.168.1.250 - 1.254 for Network Infrastructure (router(s) bridges etc.) DHCP scope set to allocate from 192.168.1.100 - 1.250 only, That means that you don't need to allocate reservations or fixed IPs to certain network devices in the longer run, as clients will always get IPs that don't clasj with other network critical things. Static addresses for the other stuff so they are all outside the scope of the DHCP range. This also has the additional benefit that if there is a problem and it's an pinned down to an IP address, I know what type of device I'm looking at as the culprit - i.e. if the Ip address is hogging the bandwidth of the broadband and it in the range of 1.100 to 1.250, I know there is a client out there causing a problem. In your case Id allocate the router to 192.168.1.254 Switch to 192.168.1.10 'Server' PC (main MP server) to 192.168.1.1 Something to think about though is if you are going to use any VPNs you'll need a different IP range than that of the remote network, As most routers will allocate an internal IP range as 192.168.1.x I'd suggest changing to something a little different - use a 172.168.1.x range instead. Phew! That must be the longest post I've done for a while! Hope it's of some use :D It's also late and I've downed a bottle of wine so forgive me if the IP counts don't match! [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
HTPC Projects
Hardware
Communication
Network speed problems
Contact us
RSS
Top
Bottom
