|
|
Post by overthehill on Jun 15, 2024 9:44:24 GMT
reboot your router (wait 1 minute) to get assigned a different IP address. DHCP doesn't work like that. You'll simply renew the lease and get the same IP again. You'd need to leave the router off for an extended period (probably 24hr+) to be sure of a different IP... not that a different IP within the same range will make much difference to anything anyway. Leaving the router off for 48hr+ can have benefits if your ADSL has gone slow anyway - if the cabling is a bit iffy, it'll lose its remembered fault-sensing, and restart the learning process. As it learns, it ratchets the speed down until it finds a reliable speed.
Not true. I get a new IP address when I reboot the router, that's exactly how DHCP is supposed to work rather than reserving IP addresses for offline devices
It can make a difference if someone has my IP address and it never changes. And the DNS lookup won't help as it only reveals the IP address in its host name.
|
|
JamesFrance
Member of DD Central
Port Grimaud 1974
Posts: 1,323 
Likes: 897
|
Post by JamesFrance on Jun 15, 2024 10:44:41 GMT
Nearly 20 years ago I helped with the development of Comodo Internet Security from when they just had a firewall. It was an interesting hobby as they would send me new files to test as well as running the beta versions. I have used it ever since and it has never let anything through. Melih who founded the company is Turkish but went to a northern uk university before starting the business in Trafford Park before relocating to California. He fell out with some of the virus experts some years ago.
|
|
|
|
Post by stevepn on Jun 15, 2024 11:05:12 GMT
Thanks for the replies. I will give Avira free a try. Yesterday I had 2 days left of Norton, now I have 30 days left. Could be a one month bonus.
|
|
|
|
Post by bernythedolt on Jun 15, 2024 11:16:32 GMT
adrianc overthehill You're both kind of right. From my old professional days as a network engineer, I remember DHCP can do both. You can hard-code configure it to lease the same internal IP address for a protracted period, or allow it to assign you any currently unused address from a preconfigured range. The former keeps things somewhat easier to troubleshoot and stay sane. One thing being missed here is that the internal private address being issued by your router's DHCP has no relevance beyond your router, so regularly rebooting the router to change it won't help much. Your internal address will be assigned from one of the private address ranges:- 10.0. 0.0 to 10.255. 255.255. 172.16. 0.0 to 172.31. 255.255. 192.168. 0.0 to 192.168. 255.255. Most commonly our router's DHCP assigns us a 192.168.x.x address. These private addresses are not permitted to cross the router to the WAN (the internet), so they have no relevance to hackers trying their luck on your system. They can't directly access your private address. That's the whole point of the relatively small private address space - to make a small number of addresses stretch an awful long way right around the globe. So whatever DHCP address you get assigned, however it's done, will never be seen on the web. The industry standard mandates that no private address is allowed to be routable beyond your router (otherwise there'd be internet meltdown!). It's the external port of your router that's assigned a public IP address by your ISP and it's this address that the interweb uses (and hackers are continually trying their luck with). The router's job is to accept that traffic and reroute it internally across your wi-fi/Ethernet cable to your browser/e-mail PC's internal private address. Similar in reverse for outgoing traffic. If, like me in the past, you have access to line sniffing tools, you'd be amazed at the sheer number of attempts to access your router's public IP address nefariously. From the moment you switch it on, they're there trying several times a minute, looking for vulnerabilities...
|
|
agent69
Member of DD Central
Posts: 6,030
Likes: 4,431
|
Post by agent69 on Jun 15, 2024 11:45:46 GMT
I remembre many years ago when I purchased my first personal computer (when 28.8kbs download speed was considered lighting fast). It came with anti-virus software on a CD that you loaded onto your machine. Every 3 months they sent you a new disk with the updated anti-virus files on it.
What ever happened to the good old days?
|
|
|
|
Post by batchoy on Jun 15, 2024 13:06:44 GMT
DHCP doesn't work like that. You'll simply renew the lease and get the same IP again. You'd need to leave the router off for an extended period (probably 24hr+) to be sure of a different IP... not that a different IP within the same range will make much difference to anything anyway. Leaving the router off for 48hr+ can have benefits if your ADSL has gone slow anyway - if the cabling is a bit iffy, it'll lose its remembered fault-sensing, and restart the learning process. As it learns, it ratchets the speed down until it finds a reliable speed.
Not true. I get a new IP address when I reboot the router, that's exactly how DHCP is supposed to work rather than reserving IP addresses for offline devices
It can make a difference if someone has my IP address and it never changes. And the DNS lookup won't help as it only reveals the IP address in its host name.
It depends on the DHCP server, cheap home routers tend not to have persistant storage, so lose the DHCP Lease database when powered off and so will issue IPs on a first come first served basis (if they have not been reserved) when rebooted. The high availablity firewalls I use have persistant storage so they keep the lease database even through power outages, and tend to reallocate the same IP when a client renews even after being power cycled.
|
|
|
|
Post by overthehill on Jun 15, 2024 14:33:45 GMT
adrianc overthehill You're both kind of right. From my old professional days as a network engineer, I remember DHCP can do both. You can hard-code configure it to lease the same internal IP address for a protracted period, or allow it to assign you any currently unused address from a preconfigured range. The former keeps things somewhat easier to troubleshoot and stay sane. One thing being missed here is that the internal private address being issued by your router's DHCP has no relevance beyond your router, so regularly rebooting the router to change it won't help much. Your internal address will be assigned from one of the private address ranges:- 10.0. 0.0 to 10.255. 255.255. 172.16. 0.0 to 172.31. 255.255. 192.168. 0.0 to 192.168. 255.255. Most commonly our router's DHCP assigns us a 192.168.x.x address. These private addresses are not permitted to cross the router to the WAN (the internet), so they have no relevance to hackers trying their luck on your system. They can't directly access your private address. That's the whole point of the relatively small private address space - to make a small number of addresses stretch an awful long way right around the globe. So whatever DHCP address you get assigned, however it's done, will never be seen on the web. The industry standard mandates that no private address is allowed to be routable beyond your router (otherwise there'd be internet meltdown!). It's the external port of your router that's assigned a public IP address by your ISP and it's this address that the interweb uses (and hackers are continually trying their luck with). The router's job is to accept that traffic and reroute it internally across your wi-fi/Ethernet cable to your browser/e-mail PC's internal private address. Similar in reverse for outgoing traffic. If, like me in the past, you have access to line sniffing tools, you'd be amazed at the sheer number of attempts to access your router's public IP address nefariously. From the moment you switch it on, they're there trying several times a minute, looking for vulnerabilities... I'm not talking about addresses on my network but the IP address used to access the internet and the internet uses to access you. It is assigned by your internet provider like Vodafone as it's their network which interfaces with the Internet and routes traffic to your router. My router is not on the internet but a private network between me and my network provider, for anyone unclear what the hell we're talking about.
|
|
|
|
Post by bernythedolt on Jun 15, 2024 17:28:35 GMT
adrianc overthehill You're both kind of right. From my old professional days as a network engineer, I remember DHCP can do both. You can hard-code configure it to lease the same internal IP address for a protracted period, or allow it to assign you any currently unused address from a preconfigured range. The former keeps things somewhat easier to troubleshoot and stay sane. One thing being missed here is that the internal private address being issued by your router's DHCP has no relevance beyond your router, so regularly rebooting the router to change it won't help much. Your internal address will be assigned from one of the private address ranges:- 10.0. 0.0 to 10.255. 255.255. 172.16. 0.0 to 172.31. 255.255. 192.168. 0.0 to 192.168. 255.255. Most commonly our router's DHCP assigns us a 192.168.x.x address. These private addresses are not permitted to cross the router to the WAN (the internet), so they have no relevance to hackers trying their luck on your system. They can't directly access your private address. That's the whole point of the relatively small private address space - to make a small number of addresses stretch an awful long way right around the globe. So whatever DHCP address you get assigned, however it's done, will never be seen on the web. The industry standard mandates that no private address is allowed to be routable beyond your router (otherwise there'd be internet meltdown!). It's the external port of your router that's assigned a public IP address by your ISP and it's this address that the interweb uses (and hackers are continually trying their luck with). The router's job is to accept that traffic and reroute it internally across your wi-fi/Ethernet cable to your browser/e-mail PC's internal private address. Similar in reverse for outgoing traffic. If, like me in the past, you have access to line sniffing tools, you'd be amazed at the sheer number of attempts to access your router's public IP address nefariously. From the moment you switch it on, they're there trying several times a minute, looking for vulnerabilities... I'm not talking about addresses on my network but the IP address used to access the internet and the internet uses to access you. It is assigned by your internet provider like Vodafone as it's their network which interfaces with the Internet and routes traffic to your router. My router is not on the internet but a private network between me and my network provider, for anyone unclear what the hell we're talking about. Hmm... you were discussing the operation of the DHCP server on your router, so I'd say you were very much talking about your private addresses inside your network. 
|
|
|
|
Post by overthehill on Jun 15, 2024 19:16:06 GMT
No I wasn't. This is what I wrote, you've assumed I was referring to my internal router addresses which would be meaningless in the context of threats from the Internet.
"I get a new IP address when I reboot the router"
|
|
|
|
Post by bernythedolt on Jun 15, 2024 21:31:19 GMT
You're right that I interpreted "I get a new IP address [from DHCP] when I reboot the router" to mean you get a new laptop/desktop address. It was this statement you wrote about your PC which led me to think that way: "Reboot your PC as Windows gets slower the longer you use it, reboot your router (wait 1 minute) to get assigned a different IP address". I'm possibly alone in interpreting the ambiguity that way though... |
|
|
|
Post by bracknellboy on Jun 16, 2024 7:34:52 GMT
You're right that I interpreted "I get a new IP address [from DHCP] when I reboot the router" to mean you get a new laptop/desktop address. It was this statement you wrote about your PC which led me to think that way: "Reboot your PC as Windows gets slower the longer you use it, reboot your router (wait 1 minute) to get assigned a different IP address". I'm possibly alone in interpreting the ambiguity that way though... There are many things in this fractured, polarised world that we can all too easily fallout over, , and end up vehemently arguing the toss down to the last possible nuance. Which particular IP address was being discussed should not be one of them. Just saying.
|
|
|
|
Post by bernythedolt on Jun 16, 2024 11:10:32 GMT
There speaks someone who's obviously never been a network engineer!  "Which particular IP address was being discussed" was my bread & butter for donkey's years and a leopard can't change its spots... And I'm now fresh out of animal references. |
|
|
|
Post by overthehill on Jun 16, 2024 13:12:30 GMT
We could turn our attention to fallout and fall out , one being post apocalyptic and the other pre apocalyptic.
|
|
adrianc
Member of DD Central
Posts: 9,978
Likes: 5,131
|
Post by adrianc on Jun 16, 2024 21:34:17 GMT
There speaks someone who's obviously never been a network engineer! "Which particular IP address was being discussed" was my bread & butter for donkey's years and a leopard can't change its spots... And I'm now fresh out of animal references. It's aardvark sometimes.
|
|
|
|
Post by overthehill on Jun 17, 2024 8:57:20 GMT
There speaks someone who's obviously never been a network engineer! "Which particular IP address was being discussed" was my bread & butter for donkey's years and a leopard can't change its spots... And I'm now fresh out of animal references. It's aardvark sometimes. Can't bear it.
|
|
