SCOUG-HELP Mailing List Archives
Return to [ 29 | 
February | 
2004 ]
<< Previous Message << 
 >> Next Message >>
 
 
 
Content Type:   text/plain 
=====================================================  
If you are responding to someone asking for help who  
may not be a member of this list, be sure to use the  
REPLY TO ALL feature of your email program.  
=====================================================  
 
Svobi:  
 
I think a scheme like yours could be a good idea   
and I use one myself.  I need to keep mine simple,   
because I rarely need or want to re-configure anything.   
It's hard to remember what I did last time.   
------------------------------------------------------  
 
192.168.123.001 - 010   DHCP for windows machine and sometimes laptops/wireless AP.    
192.168.123.011 - 254   Static   
192.168.123.254         SMC Router/firewall box with built-in printserver   
192.168.123.253         Printserver for LaserJet     
192.168.123.252         Printserver for tabloid ("B") size color inkjet     
192.168.123.251         Reserved for future printserver    
192.168.123.250         Reserved for future printserver    
 
If I need more DHCP addresses, I'll start taking them out of the BOTTOM   
of the Static range. I like the idea of having my printers on a static IP.  
It seems like it might help to make troubleshooting easier. The Router had   
to be on a static IP, so that set the pattern for the rest.   
 
I set the wireless AP for DHCP passthrough, rather than fixed IP.   
Most folks these days seems to expect to plug it in and have it   
work, without any further fuss -- me included.  So I set the fixed   
hardware to Fixed IP and the moveable hardware to DHCP.   
 
 -- Steve   
 
++++++++++++++++++++  
On 2/29/04, Svobi wrote, in part:  
>  
>Hello SCOUGians  
>   
>I have a working TCPip envrionment with, for me,   
>somewhat logical design but I would like to hear some   
>other opinions !  
>  
>Does it matter how the TCPip numbers are given or   
>would it be a benefit to keep a structured on like i.e.  
>following:  
>  
>192.168.zzz.1 for DSL modem  
>192.168.zzz.11 for DSL router  
>  
>192.168.zzz.y21 static for system 1  
>192.168.zzz.y22 static for system 2 (notebook)  
>192.168.zzz.y23 static for system 3  
>192.168.zzz.y24 static for system 4  
>192.168.zzz.y25 static for system 5  
>192.168.zzz.y26-y29 dynamic for guest or test systems  
>  
>192.168.zzz.y31 for print server  
>  
>The listed units here are the same as in my environment.  
>  
>Now, ONE more aspect has to be checked & integrated:  
>  
>192.168.xxx.y22 now is my notebook with WL abilities and   
>I am going to install an AP soon !!  
>  
>  
>How shall I change my current TCPip number structure to   
>implement this / perhaps also guest and test AP's ???  
>  
>Your suggestions are very appreciated ;-)  
>TIA and have a nice Sunday,  
>svobi  
 
 
=====================================================  
 
To unsubscribe from this list, send an email message  
to "steward@scoug.com". In the body of the message,  
put the command "unsubscribe scoug-help".  
 
For problems, contact the list owner at  
"rollin@scoug.com".  
 
=====================================================  
 
  
<< Previous Message << 
 >> Next Message >>
Return to [ 29 | 
February | 
2004 ] 
  
  
The Southern California OS/2 User Group
 P.O. Box 26904
 Santa Ana, CA  92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group.  ALL RIGHTS 
RESERVED. 
 
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International 
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
 
 |