Re: [GLLUG] IPv6 addresses

2021-07-19 Thread Chris Bell via GLLUG
On Monday, 19 July 2021 13:40:28 BST Tim Woodall via GLLUG wrote:

> 
> Ah, yes. I misread the OP.
> 
> https://community.bt.com/t5/Archive-Staging/IPV6-Settings/td-p/1699523
> and
> https://www.ispreview.co.uk/index.php/2016/11/bt-broadband-lines-now-support
> -ipv6-internet-addresses.html
> 
> Seems to suggest that you should get a /56. Does the OP get a /64 from
> the same /56 each time or is it a different /56 each time?

I have re-checked, and the IPv6 address appears to have settled, and that 
could be true, although I am unable to check at the moment. So far I am not 
sure about DNS
-- 
Chris Bell
Website chrisbell.org.uk



-- 
GLLUG mailing list
GLLUG@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/gllug

Re: [GLLUG] IPv6 addresses

2021-07-19 Thread James Courtier-Dutton via GLLUG
Hi,

I think something associated with the ipv6 disussion and ISPs.
Although they might give you ipv6 addresses, their dsl router probably
provides no firewalling for it.
I added my own firewall for ipv6.

Kind regards

James
-- 
GLLUG mailing list
GLLUG@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/gllug

Re: [GLLUG] IPv6 addresses

2021-07-19 Thread Tim Woodall via GLLUG

On Mon, 19 Jul 2021, John Winters via GLLUG wrote:


On 19/07/2021 11:25, Tim Woodall via GLLUG wrote:

On Sun, 18 Jul 2021, Chris Bell via GLLUG wrote:


My sister has a relatively new domestic BT broadband connection. The IPv4
address was expected to be dynamic despite BT claiming to have sufficient 
IPv4
addresses, while the IPv6 address so far has had a static /48 but dynamic 
/64.

[snip]


I'm not completely sure how you have static /48 but dynamic /64. Can you
not assign yourself a fixed /64 from the /48 if that's what you want?


Presumably the sister is getting allocated a /64 which varies, but always 
comes from the same /48.




Ah, yes. I misread the OP.

https://community.bt.com/t5/Archive-Staging/IPV6-Settings/td-p/1699523
and
https://www.ispreview.co.uk/index.php/2016/11/bt-broadband-lines-now-support-ipv6-internet-addresses.html

Seems to suggest that you should get a /56. Does the OP get a /64 from
the same /56 each time or is it a different /56 each time?


--
GLLUG mailing list
GLLUG@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/gllug

Re: [GLLUG] IPv6 addresses

2021-07-19 Thread John Winters via GLLUG

On 19/07/2021 11:25, Tim Woodall via GLLUG wrote:

On Sun, 18 Jul 2021, Chris Bell via GLLUG wrote:


My sister has a relatively new domestic BT broadband connection. The IPv4
address was expected to be dynamic despite BT claiming to have 
sufficient IPv4
addresses, while the IPv6 address so far has had a static /48 but 
dynamic /64.

[snip]


I'm not completely sure how you have static /48 but dynamic /64. Can you
not assign yourself a fixed /64 from the /48 if that's what you want?


Presumably the sister is getting allocated a /64 which varies, but 
always comes from the same /48.


John

--
Xronos Scheduler - https://xronos.uk/
All your school's schedule information in one place.
Timetable, activities, homework, public events - the lot
Live demo at https://schedulerdemo.xronos.uk/

--
GLLUG mailing list
GLLUG@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/gllug

Re: [GLLUG] IPv6 addresses

2021-07-19 Thread Tim Woodall via GLLUG

On Sun, 18 Jul 2021, Chris Bell via GLLUG wrote:


My sister has a relatively new domestic BT broadband connection. The IPv4
address was expected to be dynamic despite BT claiming to have sufficient IPv4
addresses, while the IPv6 address so far has had a static /48 but dynamic /64.
Is there a cost involved in providing a static address, or are UK customers
considered to be incapable of safely using a static address? Perhaps it just
allows them to charge extra for a "business" broadband.



I'm not completely sure how you have static /48 but dynamic /64. Can you
not assign yourself a fixed /64 from the /48 if that's what you want?

If you're going to be publishing the /64 in DNS somewhere then
<48-prefix>:::/64 would probably make sense. If you're not then some
random 16 bits might make more sense.

Tim.


--
GLLUG mailing list
GLLUG@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/gllug