GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
I think Netflix meant get your ISP to reset your connection, in other words have your modem renegotiate the connection parameters in the hope that this increases your speed. Just power cycling the router probably did something along those lines but for best results I think your ISP would have to reset the modem at their end also.
How changing IP address is going to fix Netflix problem?
While I haven't witnessed the following issue with Netflix I have with Amazon so with some services they identify who you are for such services as "Watch Again" or "Continue Watching" not to mention your personal preferences all by your IP. DHCP confirms that you are set for random IPs but your modem identifies itself to your ISP by MAC address and it is common that while technically Dynamic, you get the same one for years. Buying a Static IP is just a way of locking it down for certain and comes at a service fee from most ISPs.
Except that I do not know of any ISPs anymore that offer static ips to a residential customer, unless they get a business account. Either way, its a combination of many factors, the connection speed, the routing, if there is any network congestion on the ISP side, also any congestion on said streaming service. Lets not forget also that there could be throttling involved.
--edit
Also didn't the US already run out of IPv4 blocks? I am surprised they have not started to roll out either CGNAT (Carrier Grade Nat) for the IPv4 blocks, or full on IPv6. Comcast supposedly rolled something with IPv6 but it is in a very small region I think, it is more of a test.
So I imagine even as a business customer wanting a static ip, the going rate might be even higher now, just for 1 static ip, let alone if multiple static ip ranges were needed.
I don't see a high return on investment for paying extra for Static IP but I DO see huge benefits with most ISPs for the investment in a Premium or Business Account, especially DSL but even a few Cable services. Most people don't understand that Up and Down are inextricably linked and that when Up is overwhelmed, Down is severely throttled. This is not an anecdotal experience even though I can personally verify this concept and experience. It is a fundamental way in which networking functions.So I routinely pay extra for greater alignment between the two, meaning higher Up limits.
Quite honestly I do not see the point or need for a static ip even for a business, unless you are hosting something or have security cameras on site that you need to access. Most business accounts I encountered as a frontline agent would be mom-and-pop businesses and they would have a static ip, sometimes multiple and they were never used so clearly the sales office were able to trick them into buying the ips, and they did not even realize they needed to setup a static nat connection on their routers to even make use of the extra blocks. DHCP for all intensive purposes is just fine, hell even if you did need to host a security camera, dynamic dns svcs are out there, and cheaper than getting a static. Unles you are ACTUALLY hosting a server, and you know what you are doing, yes get a static ip, but again the majority of business accounts I have encountered over the years, its just a waste. Getting a static ip does not stabilise your connection in anyway, especially if you are on dsl, because its dsl.
Interestingly enough my home connection shows as static when I do DNS lookup, never asked for it. I noticed though the port blocking is gone, ports 25, 80 and some more used to be blocked by ISP.
DNS is usually static, because of the 'dns assist' option. Ever wonder sometimes when you are not able to reach a site instead of a webpage cannot be found message, you are redirected to a search engine with your isp's name on the front? https://en.wikipedia.org/wiki/DNS_hi...lation_by_ISPs
All isps have options for you to opt-out. For example you just go into your router settings, and find the dns info that is there and change part of the ip (usually the last octet) to a different value. Or you can simply not use your isp's DNS ip, and use something else, like Google's DNS 4.4.4.4 or 8.8.8.8.
All isps at least here in the US also block ports 25 80 and 110 for residential, business accounts have no restrictions and usually all isps by now probably do not even use ports 25 and 110 for email, Verizon uses ports 465 and 995 with ssl.
Again though, if you have a physically crappy connection i.e. dsl - settings on your router won't really have any real improvement. There is just too many issues, i.e noise on line, ground faults, shorts, water and other environmental issues. T1s and such are at least better shielded, but yes they are more expensive than a cable or dsl connection, but the reliability is plain to see though again it is more economical and advantagous in the long run just to go fiber (if available).
Thats not to say that fiber doesn't have it's own weaknesses, it is not subject to any interference per-se like copper, but a simple microbend (less than a mm) can actually weaken the light, or if it is severed of course, but other than that the bandwidth limitations are practically non-existent on fiber, except of course only limited by the equipment in the CO on how much it can throw out and at the site by their equipment as well.
Going off topic now. I never used ISP's DNS, I have my own. Ports 25. 80, and others were blocked on my residential connection and suddenly the blocks were gone. I'm not complaining, this is fiber connection BTW.
Going off topic now. I never used ISP's DNS, I have my own. Ports 25. 80, and others were blocked on my residential connection and suddenly the blocks were gone. I'm not complaining, this is fiber connection BTW.
Nice. Also is your fiber all the way to your premises (FTTP) or only up to the neighborhood/node or curb(FTTN FTTC)? My fiber is FTTP
None of those, either. When I set up my router years ago I noticed the DNS had IANA root servers preconfigured as source. For kicks I left it like this.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.