Network IP

[Amboyduke]

This is going to sound like a very novice question and it is. I am a somewhat newbie tech. Our clients use watchguad firewall...I know where the IP address on the External port come from but where does the IP scheme on the Trusted port and /or Optional port come from. Some of our clients have a 10. scheme and others have a 192.168 scheme. I could ask my boss but I obviously do not want him to know that i am a little lost.
Any help would be appreciated. Feel free to make jokes if they are followed by important information.

 

[CiscoGuy33]

Amboyduke,

10.x.x.x and 192.168.x.x are both private IP address ranges, you can read more here -

http://en.wikipedia.org/wiki/Private_network

These, in most cases, were setup by the network admin based on his preference or maybe on what the client had previously setup.

In some cases the router such as a Linksys or a D-Link will use 192.168.0.x or 192.168.1.x by default based on how it was configured at the factory in the firmware.

As a "newbie tech" you might want to pick up a good networking book!!

Hope this helps!


E.A. Broda
CCNA, CCDA, CCAI, Network +

 

[Amboyduke]

Just to give background: the vast majority of our clients use server 2003 that is set up for DHCP. I had a feeling that it was kind of the admins discretion on the IP range as long as it was in the A,B, or C class. I was just not sure. Thanks for the info.

 

[burtsbees]

What do you mean, "where do they come from"? Do you mean what caused your boss to choose these subnets, or how they get there, as in the configuration of the firewall? For more info on private IP addresses vs public IP addresses, Google RFC1918.

Burt

 

[CiscoGuy33]

Amboyduke,

You said - "I had a feeling that it was kind of the admins discretion on the IP range as long as it was in the A,B, or C class." - it really has nothing to do with class A, B or C, these are PRIVATE LAN IP addresses, I could have a class C IP on the WAN and use 10.x.x.x on the LAN. The admin can mix and match or use them anyway he wants - they are PRIVATE - they are not routed outside the LAN.

As Burt said - Google RFC1918 or follow my Wikipedia link (which talks about RFC 1918) to have a better understanding on this.

Hope this helps!

E.A. Broda
CCNA, CCDA, CCAI, Network +

 

[kmills]

Amboyduke,
Asking the boss how your network is configured (DHCP, reservations, static IPs) isn't unreasonable. He should have provided you that information to start with.

However, if you have access to a client computer, running ipconfig /all at the command prompt should give you some insight.

Kmills

 

[burtsbees]

Normally, people assign static IP addresses to servers, printers, routers, switches and cameras, etc---anything they must be able to console to remotely (telnet, ssh, ssl, etc). I have had people argue me on this point, but they were mostly MSCA/MSCEs, and they would say that it is okay for EVERYTHING to be dhcp, because one could always remote to a device by node name. DNS services aren't always reliable, especially on a Windoze network, IMHO. I ALWAYS statically assign ip addresses to printers, routers, switches, cameras and other such devices. The only devices that I normally assign as dhcp, in fact, are workstations. Everyone's different. So I agree---ask your boss what he/she feels is the best way.

Burt