Our ISP is ihug for both netblocks. I will contact them and see what is up with it, since we can access everything else. Matt Brown wrote:

On Mon, 2005-10-03 at 11:39 +1300, Andrew Thrift wrote:

...

For around a month now i have not been able to access www.wlug.org.nz from out netblocks 202.49.148.0/24 and 202.49.149.0/24 has anything changed at the WLUG end that could be causing this?

Hoiho (www.wlug.org.nz server) did change IP address a month ago, so it's possible there is a routing problem.

Can you provide a traceroute from within the problematic netblock to hoiho please.

Who is your upstream ISP?

Unfortunately we have a horrible managed Lucent Brick firewall that blocks all inbound/outbound ICMP! Matt Brown wrote:

On Mon, 2005-10-03 at 12:01 +1300, Andrew Thrift wrote:

...

Our ISP is ihug for both netblocks.

I will contact them and see what is up with it, since we can access everything else.

Can you post a traceroute? It's not necessarily ihug's fault (although it is certainly likely that it is). A traceroute will help us to determine where the problem lies.

Cheers

FYI Gavin on Ihug blink adsl 256 flat rate get the site fine so its maybe not totally ihug either. just your bit of it On 3/10/2005, at 12:34 PM, Matt Brown wrote:

On Mon, 2005-10-03 at 12:19 +1300, Andrew Thrift wrote:

...

Unfortunately we have a horrible managed Lucent Brick firewall that blocks all inbound/outbound ICMP!

Yah, I imagine that not being able to access hoiho is the least of your problems then.

/me passes Cluebat

We've checked the BGP session feeding hoiho and the routes for your networks aren't advertised there. But the traffic is routed nationally from hoiho to global gateway.

Looks like a routing fault between global gateway (Telecom) and ihug. Other ihug traffic (bliink, etc.) seems to be passing between these two correctly so it's possible that your networks have been dropped from a filter list or something.

So as you say, probably best to bug iHug about it, at least we've verified that it's not our fault now :)

-- Matt Brown matt(a)mattb.net.nz Mob +64 275 611 544 www.mattb.net.nz

_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug

still bugging ihug, still cant reach it... :( -- FORTUNE PROVIDES QUESTIONS FOR THE GREAT ANSWERS: #19 A: To be or not to be. Q: What is the square root of 4b^2?

On 19/10/05, John R. McPherson <jrm21(a)cs.waikato.ac.nz> wrote:

On Wed, Oct 19, 2005 at 03:20:36AM +0000, Glenn Enright wrote:

...

still bugging ihug, still cant reach it... :(

if I traceroute a 202.49.148.x address from www.wlug.org.nz, it goes via global-gateway to optus.net.au to ihug.net.

Doesn't sound like anything we can change from our side of things.

John McPherson

I have forwarded this to an Ihug staff member who is active on NZNOG mailing list. Hopefully they might be able to look at it. -- http://wand.net.nz/~iam4 WAND Network Research Group University of Waikato New Zealand

Hmmm Gavin who could reach it on IHUG, now can't either Here's my traceroute too: Traceroute has started ... traceroute to hoiho.wlug.org.nz (210.55.18.250), 30 hops max, 40 byte packets 1 ipcop.happypenguin.co.nz (x.x.x.x) 2.135 ms 0.735 ms 0.536 ms (My Network and altered to protect the guilty) 2 x.x.x.x (X.x.x.x) 58.902 ms 61.785 ms 78.658 ms (My Network and altered to protect the guilty) 3 203-109-156-250.ihug.net (203.109.156.250) 122.968 ms 68.334 ms 62.443 ms 4 vl118-tig-nz-core-1.ihug.net (203.109.156.217) 71.099 ms 70.371 ms 68.303 ms 5 203-109-156-193.ihug.net (203.109.156.193) 73.045 ms 76.539 ms 71.145 ms 6 203-109-156-138.ihug.net (203.109.156.138) 70.009 ms 87.615 ms 72.619 ms 7 g1-0-1642.u12.telstraclear.net (203.98.18.161) 64.024 ms 73.208 ms 67.666 ms 8 * * * 9 g0-1-0-4.akcr8.global-gateway.net.nz (210.55.202.49) 96.707 ms 95.794 ms 93.568 ms 10 v4.aksw7.global-gateway.net.nz (210.55.202.51) 100.419 ms 97.348 ms 96.887 ms 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * *

On 19/10/2005, at 5:58 PM, Ian McDonald wrote:

On 19/10/05, John R. McPherson <jrm21(a)cs.waikato.ac.nz> wrote:

...

On Wed, Oct 19, 2005 at 03:20:36AM +0000, Glenn Enright wrote:

...

still bugging ihug, still cant reach it... :(

if I traceroute a 202.49.148.x address from www.wlug.org.nz, it goes via global-gateway to optus.net.au to ihug.net.

Doesn't sound like anything we can change from our side of things.

John McPherson

I have forwarded this to an Ihug staff member who is active on NZNOG mailing list. Hopefully they might be able to look at it.

-- http://wand.net.nz/~iam4 WAND Network Research Group University of Waikato New Zealand

_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug

For the moment I will let Ian deal with it, as he is talking with IHUG on it, but if he gets a run around, I will log a fault with helpdesk. On 20/10/2005, at 9:51 AM, Matt Brown wrote:

On Thu, 2005-10-20 at 09:19 +1300, Gavin Denby wrote:

...

Hmmm Gavin who could reach it on IHUG, now can't either

Here's my traceroute too:

Traceroute has started ...

traceroute to hoiho.wlug.org.nz (210.55.18.250), 30 hops max, 40 byte packets 1 ipcop.happypenguin.co.nz (x.x.x.x) 2.135 ms 0.735 ms 0.536 ms (My Network and altered to protect the guilty)

Tracerouting from hoiho to your IP (I think..., mail headers are a wonderful thing), shows that the problem is almost certainly within iHug.

Host Loss% Snt Last Avg Best Wrst StDev 1. frontgate.tintz.co.nz 0.0% 47 0.6 0.5 0.5 0.6 0.0 2. vlan-2075.tkbr4.global-gateway.n 0.0% 47 5.6 8.9 5.3 69.3 10.0 3. gi1-0-0-30.tkbr1.global-gateway. 0.0% 47 5.4 20.3 4.9 177.5 37.3 4. ATM9-0-0-50.sn1.optus.net.au 2.1% 47 35.0 49.1 31.4 146.4 21.3 5. AsiaNetcom.sn1.optus.net.au 0.0% 47 30.7 31.9 30.3 41.2 2.3 6. ??? 7. ??? 8. 203-109-156-140.ihug.net 2.2% 46 30.8 33.5 30.2 59.4 5.4 9. Gig0-1.117-tig-nz-akl-lns-2.ihug 0.0% 46 30.8 33.3 30.5 52.9 4.5 10. ???

Have you tried logging a fault with their helpdesk... tiresome I know, but the more we bug them about it the better :)

On Fri, 2005-10-21 at 22:22 +0000, Glenn Enright wrote:

After speaking with ihug technicians, it would seem that it's something to do with the lack of a peering agreement with Telecom. Traceroutes to Telecom end in a similar way, although I have no problems reading THEIR website (natch). Ihug were very helpful, and I've had another suggestion to try using a proxy site such as http://anonymizer.com which works.

That sounds bogus to me, at the very least (if the problem is really caused due to a lack of peering) iHug should simply be sending the traffic to their upstream provider (TelstraClear). You'll have a longer path but you should get there eventually. There isn't really any reason for them to make sites unavailable simply because they don't have a peering agreement. All of iHug bliink traffic appears to go iHug -> TCL -> GG -> wlug with the same path followed in reverse. I can't see why they would refuse to route your traffic that way as well. Not very acceptable service from them in my opinion, and if I were you I wouldn't let it end there! -- Matt Brown matt(a)mattb.net.nz Mob +64 275 611 544 www.mattb.net.nz