TNSR Home Lab Newbie need some support

remi_imer

Hi Everyone,

I am new to TNSR and NOT a Network Pro - just someone who likes tech and fast internet :)

In prep for my upcoming 10 Gbe (dl/up) Internet connection, i installed TNSR (baremetal setup) to my Old Computer running Intel i5 4 cores, with 4GB Ram, and Mellanox ConnectX-4 pci 3.0 x8

I've followed the installation manual of TNSR to the T, up to the end of Zero-to-Ping section.

However, I just learnd from my ISP that i will be connected to their network via IPV6 and not IPV4 anymore. Which means i have to modify this code below to IPV6 right? Is there any other config i need to modify?

tnsr# configure terminal
tnsr(config)# interface WAN
tnsr(config-interface)# description Internet
tnsr(config-interface)# dhcp client ipv4
tnsr(config-interface)# enable
tnsr(config-interface)# exit

My set up will be like below.

Internet (10 Gbe)---->TNSR Edge Router----->Mikrotik 8 Port SFP+ Managed Switch------>TP Link 8 port 1gb unmanaged switch - This is where i will hook up my 2 x Wifi6 Access points for the cellphones, tablets IOT devices etc.

Thanks in advance for your support.

Kind Regards,
Remi

Derelict

@remi_imer TNSR does not yet support DHCP6 clients.

How is the IPv6 actually provisioned by the ISP?

remi_imer

@derelict

Thanks for replying.
I am not sure, i will ask my ISP for more info.
All i know is that they assigned me 1 static IPV6 IP. Whereas before it was IPV4.

Derelict

@remi_imer Static should work. A DHCP6 service with a static mapping will not. If you only have IPv6 service they might be doing something like MAP-T too. That would also be a challenge.

remi_imer

@derelict

Thanks a bunch for your reply and for confirming it will work.
Do i still have to change the code in my previous post to IPV6 or that one will work as is?

The other question i have is how can i share the internet with my other non IPV6 capable devices. I read about IPV6 tunneling, but not sure how that is configured with TNSR.

Derelict

@remi_imer Sorry but this is nowhere close to enough information to be able to say. You will need to see exactly what the ISP has to offer here and make TNSR match if possible. They must have deployed at least one of the migration strategies for this.

remi_imer

@derelict

I asked the ISP on how they provisioned their IPV6 and whether they use MAC-T but they didn't answer it directly.

This is what they replied to me.

"IPV6 IP addresses and the prefix are obtained via DHCP. Please tell us the prefix your router got, so we can store it statically.

Please note: The prefix is based on the MAC address of the router. As soon as you change the router and thus the MAC address, you will get a new prefix. Please contact us in such a case, so we can restore the previous prefix."

Not sure if this helps

remi_imer

@derelict

my ISP sent another email. They said they are using native IPV6 No MAC-T.

Derelict

@remi_imer It would be MAP-T. MAP-T is a way to encapsulate IPv4 addresses in an IPv6 address and requires a MAP-T-capable CPE to make happen.

"Native IPv6" is still not enough information. Need specific provisioning information from them.

If it is not static IPv6 then it is unlikely TNSR will be able to connect to it.

remi_imer

@derelict

I message my ISP and they told me they are not using MAP-T.

I also did some digging from their website and I found this information below.

"The IPv4 address is part of our backbone - not a Carrier-Grade-NAT address like with other providers. A fixed IPv4 or a /29 subnet are available for an additional charge. A static IPv6 /48 network is included free of charge. The addressing is done via DHCPv6-PD prefix delegation."

Not sure if this helps.

If not i guess i just have to try to plug it when my line goes live.

RobbieTT

@remi_imer
That latest quote seems to suggest IPv4 is available (dynamic address) plus a free IPv6 block; nothing atypical there. For an additional fee you can have a static IPv4 and an even-larger IPv6 block. Again, nothing unusual.

Perhaps some misunderstandings somewhere?

️

Derelict

@robbiett @remi_imer TNSR does not yet support DHCP6 in any fashion. Not on outside/client interfaces nor inside as a server.

I do not believe it is possible to get it to work on this circuit given the ISP provisioning strategy.

RobbieTT

@derelict
I understand that but was limiting my post to what the ISP can provide, which includes a static IPv4 address (for a fee) and more than a suggestion of a dynamic IPv4 otherwise.

I suspect there has been loose language used over IPv6 which may have left the impression that only IPv6 was available when it is now clear they can provide IPv4 connections.

️

remi_imer

@Derelict, @RobbieTT

Thank you both for looking into this and for giving your thoughts. It is highly appreciated.

My ISP does offer static IPV4 for their lower tier connection (1GB (dl/up) connection) which is what i currently have right now.

However their higher tier (25 Gbe (dl/up) and 10 Gbe (dl/up) seems to be on pure IPV6 only (at least what i think it is but am no expert) and hence if you want IPV4 you now have to pay extra per month.

Hope this helps.

blunden

@Derelict said in TNSR Home Lab Newbie need some support:

@robbiett @remi_imer TNSR does not yet support DHCP6 in any fashion. Not on outside/client interfaces nor inside as a server.

I do not believe it is possible to get it to work on this circuit given the ISP provisioning strategy.

Is this still the case? Given that DHCPv6 PD seems to be the most common way for ISPs to provision IPv6 to at least residential customers, I'm a bit surprised it isn't supported yet. Are all business IPv6 customers simply using static configuration?

VPP seems to support it since 2018 from what I can tell (both according to the wiki and git commit history), so in that case I'm guessing that the rest of the plumbing to hook it up to the CLI etc. hasn't been implemented yet?

https://wiki.fd.io/view/VPP/DHCPv6#DHCPv6_prefix_delegation
https://github.com/FDio/vpp/commit/81119e86bdf47f41f06218f91e52024bc4d00e7c