Types of IP address

Guyz i have not found a single discussion of types of IP addresses...

for examples there are dynamic IP (heard its very much secured)

well i dontknow how would be define dynamic IP

well the times of IP's are

xx.xxx.x.xxx (forexample 10.207.2.200)
similarly xxx.xxx.x.xx (192.168.0.22)
and many many ofcoz i dont have the knowledge of this but i want to know about this...

if i can get a explanation on this ..

about the IP its about which IP is how much bits what is it called and what is the plus point and negative point of that IP

so if i can get a lil about this i think network security will be more closely looked if this is discussed with u guyz

thx for ur excenlent replies

Regards
Kingkong

IP addresses are pretty much irrelevant when it comes to security considerations. What matters is:

1. How you configure your system
2. How you manage your system
3. How you use your system

A "static" IP address (if known) does present a sitting target, whereas a "dynamic" IP address would be a moving target in theory. However:

1. Many "dynamic" addresses change relatively infrequently
2. Your "dynamic" IP has been used by someone else who may result in you getting targeted by mistake.
3. Thinking that dynamic addresses are more secure is nonsense. At best it is "security through obscurity" and that is a very false sense of security.
4. Undisclosed static IP addresses will get attacked anyway.

I just looked at my firewall log..............

Access attempts: 92,074
Intrusion attempts: 13,475

And I have a dynamic IP that changes every time I log on.

These are bots, worms, and scumbags that are randomly trawling the net looking for vulnerable systems (OK some internet "noise" as well :D)

OK, most of these "threats" just try to communicate with an IP. If they don't get a response they move on to the next one. If they do find an active computer, or know that there is one there, they still have to find an open port running a vulnerable service to proceed any further. Or possibly get a user to do something very stupid from the inside.

In reality, security begins at home (that's 127.0.0.1 :D)

The only exception I can think of is DoS and DDoS attacks against known IP addresses. Even in this case the IP address is spurious because the targets want legitimate communication, and have to broadcast their IP for this to be possible. For example, how would e-commerce work if this were not the case?

Like in a post room, most packets are harmless but every now and then one is a bomb.

king kong what exactly are your trying to achieve? IP address's are merely a way of communicating to each other. like when you have something to say to joe on 3rd floor, you know that you can call him on extension 208 and he'll pick up and listen to what you have to say (check out OSI Model). and whats this about plus point and negative point? Security implemented at an IP level?? no such thing, unless your talking about segregating your Network, like i said you need to tell us what your trying to achieve. (if this then do this)

IPs have 4 octets(8bits per octet making 32bits) but we also have IPv6 which is 128 bits in a whole different ball game (hexa). I advise you to break down your question, then guys in here can help. cheers man

Hi KK,

For descriptions of the workings of IP addresses please try these links. They are just the technical side rather than security but might help your studies?

http://www.webopedia.com/TERM/I/IP_address.html

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

:)

ya what i thought was wrong but also correct....

as the phase goes everything has 2 sides good and the bad

like we have to check the other side also

as much as i say that dynamic IP is much more secured as it keeps on changing everytime u log on but at the sme time u may be attacked for no reason

hey dude Can u quote on this

how is a dynamic IP ___.___.___.___
Static IP ___.___.___.___
etc ___.___.___.___

that wuoldbe more helpfull..

Thx and regards
Kingkong

as was mentioned above, dynamic IPs don't necessarily change every time you log on. They may do so if you have a dialup connection, but with DSL, and even more so with cable, they change very infrequently. I've had the same IP on a cable connection for as long as ten months.

Hey thx for giving me a short from which i really liked "KK"

Back to the topic

its exactly the same thing which i was asking for how is the description of bits done which one is better and which one can be the bad and less secure (Plus and negative i refer to advantages and disadvantages) for the type of IP i use

Quote:

---

1. Many "dynamic" addresses change relatively infrequently
2. Your "dynamic" IP has been used by someone else who may result in you getting targeted by mistake.
3. Thinking that dynamic addresses are more secure is nonsense. At best it is "security through obscurity" and that is a very false sense of security.
4. Undisclosed static IP addresses will get attacked anyway.

I just looked at my firewall log..............

Access attempts: 92,074
Intrusion attempts: 13,475

And I have a dynamic IP that changes every time I log on.

These are bots, worms, and scumbags that are randomly trawling the net looking for vulnerable systems (OK some internet "noise" as well )

---

like for dynamic IP i nihil told it has bad point where as i have told for dynamic IP to be more secured but again that has a problem with it

ne ways i think i have got the correct quote by nihil for the link of wiki pedia

ne waysthx a tone again for the help and reply

and yes please give further knowledge in the same topic for me as well as for other novioces here...........


Regards
KK

Hmmm, not really.

There are some numbers that are "reserved" for non-internet use, for example I think that these are:

10.xxx.xxx.xxx
172.xxx.xxx.xxx
192.xxx.xxx.xxx

Apart from that the numbers are assigned in blocks to Registrars who then assign them to the next level of users.

Now, how the users assign them is up to their own choice. Just looking at ISPs as an example, some may break them down into end user class (business, home, and so on) They might also divide them into static and dynamic blocks, but I think that would come naturally from the user type.

Business and institutional users would normally require a static address, whereas home users would not.

The real difference is in the service contract. You normally have to pay extra for a guaranteed static address.

I am not aware of any consistent way of determining if an IP address is dynamic or static from the number alone.

some ISPs use the words static or dynamic in the user identification string.

well today or may be by saturday i wil bring some real info on this

today i m going to the library and will definately bring the right info what i wanted well hope u guyz will help me out if i fail

the only problem is i m not able to explain what i wanted to know

but let hope

Regards
KK

Quote:

---

as much as i say that dynamic IP is much more secured

---

This is a old rumor which was generated by the idea that you couldn't turn machines with dialup connections into bot command and control infrastructures. Then there was alot of lies from Steve Gibson about how anyone with a high speed connection will get owned the moment they go online.

The only truth to it may be that dial-up users tend to be connected to the Internet less often. Whereas cable users would be more inclined to leave the machine connected and turned on.

Yes, the desirability of the target needs to be considered. Gibson's argument has a ring of truth to it in that high speed connections were generally on most of the time, had static or relatively static IP addresses and not only performed well, they would almost certainly be backed up by high performance hardware. That made them desirable, but not vulnerable per se.

Whether they could be owned would depend on their security, not their speed.

The fallacy of the:

Quote:

---

idea that you couldn't turn machines with dialup connections into bot command and control infrastructures

---

Also seems logical, as they would be mostly dynamic IP addresses and the botherder wouldn't be able to contact the owned machine again. He might even hit a system with better security and get detected when the IP was reassigned.

The reason that this is a fallacy should be fairly obvious? the owning software is set to phone home. Botherders don't want IP addresses, they want to own actual hardware assets. If they have found a system they can own, it is relatively safe to let that initiate communication, rather than trying to dial in.

Quote:

---

high speed connections were generally on most of the time

---

Im currently using a wireless network but that doesn't mean my computer in itself has a uptime of eight hours or more.

Its obvious most botnets still centralise to certian areas on the web, sure... but thats only to gain the information needed to slightly seperate for a multi-tiered approach at things.

Sure,

You don't have to turn it on, but how many little "fanboys" post "how many hours my system has been up" crap?

Hell, I would hunt them down and fine them for gratuitous and profligate wasting of scarce resources (electricity). What about this carbon emissions crap?

Not to mention the fire risk? :fpissed:

Quote:

---

Its obvious most botnets still centralise to certian areas on the web, sure... but thats only to gain the information needed to slightly seperate for a multi-tiered approach at things.

---

Yes, nowadays the control mechanisms are distributed. Back then they were much more centralised, so the botmaster was constantly exposing his entire asset on a net by net basis.

Quote:

---

There are some numbers that are "reserved" for non-Internet use, for example I think that these are:

10.xxx.xxx.xxx
172.xxx.xxx.xxx
192.xxx.xxx.xxx

---

Nearly.

For IPv4:

Private ranges that all ISP's will filter at the gateways, therefore will not route across the Internet and are only to be used internally in a home/office or for localhost/testing purposes etc:-

10.0.0.0 - 10.255.255.255 = Internal Class A range

172.16.0.0 - 172.31.255.255 = Internal Class B range

127.X.X.X = Loopback - Used by the localhost for various diagnostic reasons

169.254.X.X = APIPA - (Auto Assigned Private IP Address)

192.168.0.0 - 192.168.255.255 = Internal Class C range

224.X.X.X = Multicast range

240.X.X.X = R & D / Scientific purposes



Common usable ranges are that will work across the Internet:

1.X.X.X - 126.X.X.X - Class A range

128.X.X.X - 191.X.X.X = Class B range

192.X.X.X - 223.X.X.X - Class C ranges



Obviously the previously mentioned Private IP ranges are excluded from the above ranges.

Depending on what type of attack in being used, dynamically issued IP addresses do offer some security as the host is not guaranteed to be on-line for an extended period of time. Broadband users may keep the same IP for months at a time but only the actual ADSL router (or equivalent) keeps the IP address assigment, not the host behind the router.

Traffic coming in from the WWW that has not been initiated from the internal side will 9 times out of 10 never get past the router unless it has specifically been configured to do so.

If the attacker has managed to install software that phones home then the type of IP address in use is irrelevant.

Any Dynamically issued address WILL change at some point in time, which limits the availability of the host(s) to any would-be attackers

Statically assigned IP address are invariably assigned to servers/services that have a constant and direct connection to the WWW and that need 100% uptime. Also some older ISP's who got into the game around the time the Internet went global, managed to secure a large number of IP addresses and issued static ones to it's users - a static IP is very unlikely to change making the availability of the host almost unlimited, therefore any would-be attacker has one less thing to worry about and can possibly be more stealthy.

The main difference from a security point of view is that more information can usually be gathered about the owner of a static IP than from the temporary owner of a dynamic IP.

as per the above NOKIA as done the same thing which i was going to post as on the clearance of dought and knowledge i would lke to give further clarification on the same and will like to give more knowledge on the same......


What is IPv4 (IPversion4)?
172.16.254.1
10101100.00010000.11111110.00000001

This resembles to the break up of the 32 bit IP address which is separeted by the Decimals spilting it into 8 bits

One byte = 8 Bits

Which in simple is 8*4= 32 bits


IPv6 Latest Version used .

2001:0DB8:AC10:FE01

This can be used and the performs with Windows Vista, Apple Computers & Advance range of Lunix


and this creates a Unique Range of IP Addresses


Where as on the Forums its knews that IPv8 is on the way

http://antionline.com/showthread.php?t=276103




Please Correct if Wrong

Thanks and Regards
KK

Hi KK,

Actually IPv6 is 128 bit (2 x 64) in 8 hexadecimal quartets.

Leading 0's and blocks of 0's can be omitted in IPv6, so it can appear to be less than 128 bits. Colons are needed when blocks of sequential 0's are omitted though.

Hmm!!

Hi Nokia and Nihil

U guyz are really good can u please explan me about the IPv6 a lil more

regard
Kk

http://www.google.co.uk/search?hl=en...e+Search&meta=

Im trying to post on somewhat relevent grounds; how can one setup a static IP on a local machine then use another to access that computer through telnet. I want to practice on a local network but would it be possible to do this through the information highway?
_________________
"you give a man a fire you warm him up for a day, you set a man on fire you warm him up for a lifetime"

You'll need to install a Telnet server on the host you want to Telnet on to. If you want to connect to it over the internet (which I wouldn't recommend) you will need to configure your router and/or firewall to forward connection to port 23 to the relevant host.

As stated, Telnet is not recommended for internet use. It came to life around 1970 and was largely used on private networks. There wasn't much in the way of an "internet" back then, certainly not how we know it today.

The main point is that security was not a major issue back then, such as it is now. Telnet is fundamentally insecure as it does not encrypt traffic, and most versions do not have strong authentication so "man-in-the-middle" attacks are quite possible.

There are other vulnerability issues as well, depending on which flavour you are using.

I would suggest that you take a look at "PUTTY" which will give you the feel of Telnet but is rather more secure.

http://www.chiark.greenend.org.uk/~sgtatham/putty/

Basically, Telnet should not be used over the public internet.

Quote:

---

The main point is that security was not a major issue back then, such as it is now. Telnet is fundamentally insecure as it does not encrypt traffic

---

Im tired of people saying that while logged into something that can be sniffed out along with the rest of their online activities.

Seems like a cheap shot at promoting software. I can play that game aswell.

"Wow, Look everyone! Poderosa has better SUCKurity! And it even has features that are so cool... you'll never use them."

Quote:

---

Im tired of people saying that while logged into something that can be sniffed out along with the rest of their online activities.

---

Well, it happens to be very true. In the case of Telnet, you are sending unencrypted information which may or may not matter, but why take risks?

PUTTY is basically Telnet with encryption and some more controls/options. Hardly rocket science, and it is free.

Quote:

---

Seems like a cheap shot at promoting software. I can play that game aswell.

---

It is freeware, and an improvement on Telnet, that is now 37 years old. Hell, you don't still boot DOS 1.0 do you? If I wanted to promote something, I would at least go for VPN or the like?:D