Migrating to IPv6

kpa

If that's really the case your ISP are morons. If you're given a /48 there must be transit network involved to make any use of the /48 in any practical way, usually this transit is a /64 from a prefix that is completely distinct from the routed /48 although it's possible to use the first /64 from the /48 as the transit.

No, you don't subnet a flat /48 that is terminated at the ISP router without some serious hackery involving tools like NDP proxy (which is not included in pfSense to drive the point home) etc. The situation is completely analogous to IPv4 where routed subnets must have a transit network involved as well, you don't magically subnet a /24 down to smaller subnets just like that, you have to have transit networks in place.

creiss

Nono,

It seems that would be me- I never explicitly asked for a transfer network due to my lack of any skill with ipv6. Luckily this is not in production (thankfuly) so I can toy around with it until it works.

I requested a transfer net for my ipv6 allocation.

At least this makes a whole of a lot more sense now.
Thanks for helping. I'll let you know when I run into the next pitfall.

-Chris.

creiss

Jeesh,

So I have my transfer net:

2a01:xyxy:5000:3::1/64 Their End
2a01:xyxy:5000:3::2/64 My End

I upped 2a01:xyxy:5000:3::2/64 as the WAN ip for pfsense. Ping6 form somewhere on the planet to 2a01:xyxy:5000:3::2 yields success. I added the default route to 2a01:xyxy:5000:3::1. Beyond that I have no clue on how to proceed.

If I take the first /64 of my /47 (2a01:xyxy:6000::1/47)

Yields me with 2a01:xyxy:6000::1/64…

Okay I admin I am at a total and utter loss here. My brain, after weeks of bashing against IPv6 can not connect the dots, or any dots here. In my 20 years in meddling with the Internet I never asked this: But can anyone tell me what IP goes hwere to get a single ping from a server to the outside? How to I do the transfer net pfsense style?

Thanks,
Christian.

Derelict

You keep saying /47. Is it really /47?

creiss

Hey,

yes, confirmed: /47. It's either /64 or /47. /64 was too small for people here so I went for /47.

JKnott

You keep saying /47. Is it really /47?

Nothing wrong with a /47. While not common, it's twice the size of a /48.

johnpoz

So you go from a /64 to a /47 which is 128K /64's - wtf is this DC thinking??

Well put ::1 on pfsense lan side interface - then on box on this lan use ::2 in your /64 set its gateway to ::1

Allow ipv6 on that interface and your ready to rock.. You can get fancy with auto handing out IPs, etc. etc. after you get your pinging working.

Then to allow internet to get to that box - just put the rules on your wan to allow the IPv6 to where you want to allow it an what protocol, etc.

Derelict

Zero reason to stray from the expected /48, which lies not only on a hex digit boundary but a : group boundary as well.

If it is going to be split into multiple /48s it should probably be a routed /40 or /44 instead.

But whatever. Like you said it's not against any rules. Just unexpected.

creiss

@johnpoz:

Well put ::1 on pfsense lan side interface - then on box on this lan use ::2 in your /64 set its gateway to ::1

Hey,

Thanks <3
And 2a01:xyxy:5000:3::2/64 in WAN with 2a01:xyxy:5000:3::1/64 as default GW, right?

-Chris

creiss

HOLY JEBUS!

After whacking my head against this and doubting my networking skills… I got it running. Turns out: A rogue IPMI from (older) testing times was also using the same IP used for the transfer net. This resulted in some kind of wierdness.

Deactivated ipv6 on said ipmi, everything is working.

Thanks all you rock!
I can rest easy tonight.

\o/
-Chris.