IPv6 problem with a Billion 7800n

Started by faircot, Jul 02, 2011, 21:55:03

Previous topic - Next topic

0 Members and 3 Guests are viewing this topic.

faircot

I've recently bought a Billion 8700n and I'm very pleased with it, with one issue.
I've turned on IPv6 in the router's config and the various test sites show that it's connecting natively via IPv6. The problem is that certain (but not all) IPv6 sites including thinkbroadband, IDNet and AAISP for example are desperately slow to display content and won't completely load in Opera or IE9. Occasionally I've had to restart the router to regain Internet connectivity.
If I turn off native IPv6 and connect to these sites through a Terodo tunnel, they load normally.
The question: is this a router specific issue or just teething troubles with these particular sites?

Edit: Sorry should have said that I'm connecting through bog standard ADSL. No 21st century technology here!

Bill

Similar problem here, although the tbb sites do load properly eventually, (Opera 11.50 and Safari 5.05 on Mac). Tbb IPv6 speed tests are diabolical (upload is OK, but download is ~ 200Kbps on FTTC :mad:), but OK elsewhere. BQM is pretty horrible, see sig.

It's not the 7800N... I had a chat with the tbb owners recently about strange results with their IDNet lines- John Hunt uses a Cisco router. But it's evidently not high priority >:(

Which IDNet and AAISP sites are you referring to, haven't had any problems with those.


Oops- v6 BQM isn't in my sig- here:

Bill
BQMs-  IPv4  IPv6

faircot

Thanks for that, Bill. I'm glad it's not the router - I was running out of config options and getting a tad annoyed.

As you say, it's impossible to run a speed test on thinkbroadband and it takes me around a minute to display the BQM. The two other URLs I've found to be slow under IPv6 are http://www.idnet.net and http://aaisp.net.uk. I'll kepp a list of others as I come across them.

Here's my BQM graph - it looks a little better that yours, I think although all connections have been erratic for the last day or so.

Regards


Bill

Interesting... BQMs here only take 5 seconds or so, the IDNet page loads instantly (but no indication whether it's v4 or v6), the AAISP one is definitely very slow on IPv6.

The common feature (in an admittedly limited range of options) seems to be IDNet :dunno:

The other thing I see is that I don't always connect to the tbb main site (same with AAISP?) with IPv6, about as often as not it's v4. I can tell which I've got by how fast it loads.

Have you tried this site:

http://ipv6-test.com/

It's got some useful tests, but for the ping test you'll have to open up the firewall to incoming v6 pings.
Bill
BQMs-  IPv4  IPv6

faircot

Quote from: Bill on Jul 02, 2011, 22:49:00

Have you tried this site:

http://ipv6-test.com/

It's got some useful tests, but for the ping test you'll have to open up the firewall to incoming v6 pings.

I have tried it, Bill.

Here's the results from just a minute ago. No problems there!



I can't run a ping test 'cos I can't figure out how to prevent the 8700's firewall from blocking them. Job for the morning.

Steve

I was going to ask Bill the easy way to let ping through the IPv6 firewall :)
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Bill

Quote from: faircot on Jul 02, 2011, 23:25:04
I can't run a ping test 'cos I can't figure out how to prevent the 8700's firewall from blocking them. Job for the morning.

Quote from: Steve on Jul 02, 2011, 23:28:29
I was going to ask Bill the easy way to let ping through the IPv6 firewall :)

Advanced => Configuration => Firewall => Packet Filter:

Rule name: anything
IP version: IPv6
Internal IP address: IPv6 address of your host
External IP address: leave blank
Protocol: RAW
Protocol number: 58
Action: forward
Direction: incoming

Grateful thanks to a tbb member :thumb:

Much more useful if your host has a fixed IP on your LAN, and when it works, back it up in a .conf file!
Bill
BQMs-  IPv4  IPv6

Steve

Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Steve

Quick question, to fix the host IPv6 address does the router have to have a static IPv6 address as well?
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Bill

No, I'm running dynamic on the router and fixed on the host with no bothers. I just used the address that the IDNet servers gave me, I didn't care what it was.

Last time I tried to fix the IPv6 address of  the router I had to fix the IPv4 address as well, and ended up with all sorts of bothers... and as I couldn't think of any good reason why I'd ever need a fixed IPv6 address on the router (a distinct benefit of no NAT) I just thought "Sod it" and let it float ;D
Bill
BQMs-  IPv4  IPv6

Steve

Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Steve

Working fine Bill, I had to turn stealth mode off on the OS X firewall too  :blush:
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Bill

Incidentally, one thing which seemed a bit odd to me- if you want to run a local web server that's accessible over the 'net (OS X comes with Apache, as I'm sure you've discovered) you don't use the firewall.

Once you've set up Web Sharing in sysprefs, it's just Advanced => Configuration => Virtual Server => Port Mapping and select the preset HTTP with the (IPv4) address of the host.
Bill
BQMs-  IPv4  IPv6

Bill

Quote from: Steve on Jul 03, 2011, 00:19:07
Working fine Bill, I had to turn stealth mode off on the OS X firewall too  :blush:

Ah, I forgot that... I didn't have it turned on!
Bill
BQMs-  IPv4  IPv6

faircot

Quote from: Bill on Jul 02, 2011, 23:36:05
Advanced => Configuration => Firewall => Packet Filter:

Rule name: anything
IP version: IPv6
Internal IP address: IPv6 address of your host
External IP address: leave blank
Protocol: RAW
Protocol number: 58
Action: forward
Direction: incoming


I can't figure out what my internal IP address is. The rule dialogue box is looking for a range but presumably it's the IP of a particular local machine it's looking for, ie 192.168.1.100 (in v6 speak though!)

Steve

http://www.whatismyipv6.net/


As there's no NAT with IPv6, that's your host address in Bill's instructions
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

faircot

Thanks Steve
I had put this address in on three occasions last night but this morning it worked  :slap:

The IPv6 ping test shows a latency of around 35ms for a IP4 ping and 58ms for a IP6 one. I don't know if that's expected or not?

Steve

It's similar to mine with regard the latency of IPv6 vs IPv4, it's not the huge difference that one see with the TBB IPv6 ping monitor.I think we'd have to ask IDNet for clues to the reason why, it could be due to inefficient IPv6 routing as I guess IPv4 routing is efficient with more routing/peering options :dunno:
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Bill

Quote from: faircot on Jul 03, 2011, 09:22:58
The IPv6 ping test shows a latency of around 35ms for a IP4 ping and 58ms for a IP6 one. I don't know if that's expected or not?

I get around 22msec for v4 and 45msec for v6, so broadly comparable. But like Steve it's steady, no wild excursions like the BQM shows.

Your IPv6 address should be available somewhere in your network settings, but if it's a Windows machine I've no idea where!
Bill
BQMs-  IPv4  IPv6

faircot

Quote from: Bill on Jul 03, 2011, 12:05:26

Your IPv6 address should be available somewhere in your network settings, but if it's a Windows machine I've no idea where!

Running ipconfig, the right address that corresponds to the one here Ping appears to be called 'temporary IPv6 address'. Why, search me?

Bill

Quote from: faircot on Jul 03, 2011, 12:47:46appears to be called 'temporary IPv6 address'. Why, search me?

That sounds like you're running the computer with a dynamic IP. Nothing wrong with that in itself, but it will probably change after a reboot- the router firewall rule will still forward pings to the "old" address thus the remote ping will stop working.

You need to set the computer to use a fixed IPv6 address, but I can't help with how to do that on a Windows machine, sorry >:(
Bill
BQMs-  IPv4  IPv6