Re: [nznog] IPv4 Exhaustion Information
On Fri, 2011-04-01 at 10:33 +1000, Elly Tawhai wrote:
________________________________________________________________________
IPv4 Exhaustion Information ________________________________________________________________________
Never mind the internet, I'm suffering from IPv4 exhaustion. In the last few weeks I've been assisting people debug access to web servers and I'm starting to get really bored with IT people telling me that their customer's IP address is 192.168.... Cheers, Lloyd This email and any attachment may contain confidential information. If you have received this email or any attachment in error, please delete the email / attachment, and notify the sender. Please do not copy, disclose or use the email, any attachment, or any information contained in them. Consider the environment before deciding to print: avoid printing if you can, or consider printing double-sided. Visit us online at ird.govt.nz
On 4/04/2011 9:30 a.m., Lloyd Parkes wrote:
On Fri, 2011-04-01 at 10:33 +1000, Elly Tawhai wrote:
________________________________________________________________________
IPv4 Exhaustion Information ________________________________________________________________________ Never mind the internet, I'm suffering from IPv4 exhaustion.
In the last few weeks I've been assisting people debug access to web servers and I'm starting to get really bored with IT people telling me that their customer's IP address is 192.168....
My guess is that the customer is sitting behind a firewall of some sort because they've given you a private ip number - 192.168.... So, you've got a clue as to where to start. Now 2403:cc00:10ff:0abb:2c00:20ff:fz01:8502/64 So, that's a public IP address, yes. So why can't that user get to your web site? Now to help you they did a traceroute from the command prompt. C:\Users\Idiot User>tracert www.ird.govt.nz Tracing route to ird.govt.nz [138.235.33.2] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.2.1 2 * * * Request timed out. 3 12 ms 12 ms 14 ms lo0.internet.ivpn.pe22.telstraclear.net [218.101 .61.114] "Turns out that while they've got a public ip (which they did write out wrong - 'z' is not valid - see above) but it gives though a firewall that's not doing the related/active connections correctly but what did it take you to discover this? How did I work it out?" These are issues that I'm still trying to get my head around before running up v6 for production use anywhere. D -- Don Gould 31 Acheson Ave Mairehau Christchurch, New Zealand Ph: + 64 3 348 7235 Mobile: + 64 21 114 0699 www.thinkdesignprint.co.nz
participants (2)
-
Don Gould -
Lloyd Parkes