eyJhb changed the topic of #nixos-on-your-router to: NixOS on your Router || https://logs.nix.samueldr.com/nixos-on-your-router
{`-`} has joined #nixos-on-your-router
thibm has joined #nixos-on-your-router
Dezgeg has quit [Ping timeout: 272 seconds]
thibm has quit [Ping timeout: 240 seconds]
thibm has joined #nixos-on-your-router
Dezgeg has joined #nixos-on-your-router
thibm has quit [Ping timeout: 240 seconds]
thibm has joined #nixos-on-your-router
thibm has quit [Ping timeout: 240 seconds]
superherointj has joined #nixos-on-your-router
thibm has joined #nixos-on-your-router
superherointj has quit [Remote host closed the connection]
<betawaffle> does anyone know if it's possible to get networkd to stop requesting IA_NA?
<betawaffle> (for ipv6)
<betawaffle> at&t gives out a global (but non-routable) address for that
<betawaffle> the IA_PD ones are good, though
<betawaffle> i almost have ipv6 working on my router!
<hexa-> andi- is quite familiar with the dhcpv6 story
<andi-> betawaffle: huh, that sounds like the wrong thing to do from AT7T's side...
<andi-> I am not aware of a way to skip IA_NA in networkd (right now)
<betawaffle> the reason they do this is that 2001 (global but non-routable) is supposed to be for their residential gateway
<betawaffle> but i'm bypassing the gateway
<andi-> does it affect your system?
<betawaffle> ok, so if i can't skip IA_NA, is there some routing trick i can do in linux to get it to not attempt to use that as the source address?
<andi-> I mean having an unroutable addres on the interface shouldn't matter as long as everything you route has proper source addresses
<betawaffle> yeah, if that address is assigned, all ipv6 traffic tries to use that address
<betawaffle> if i remove the bad addresses, packets get sent with one of the PD assigned addresses
<andi-> i wonder if you can use source routing for that but that still wouldn't affect source address selectin
<betawaffle> also, i've got my working v6 prefixes configured statically, because i can't seem to get networkd to do the right thing with the PD stuff
<andi-> betawaffle: what version of networkd is this?
<betawaffle> the one that's part of 20.09
<betawaffle> i haven't wanted to put my router on unstable yet
<betawaffle> systemd 246 (246)
<andi-> mhm, do we have the SubnetId support there yet?
<andi-> let me check
<betawaffle> it seemed like it did, but i was having some trouble with the docs, so i took that part out
<betawaffle> so... here's the weird thing (or maybe not weird)
<betawaffle> i can ping my router and workstation over ipv6 from the internet, but i can't reach out, because the packets get the wrong src
<betawaffle> ok, let me try that
<andi-> regarding your source route selection: You can move the internet link into a VRF and route into that from the "host"
<andi-> then the source selection happens on the host and you can have whatever source addresses that exist outside of that VRF
<betawaffle> hmm, not sure how i'd set that up
<betawaffle> 2a00:1450:400a:804::2004 from :: via fe80::a2f3:e4ff:fe5a:2630 dev wan proto ra src 2001:506:7298:df9::1 metric 1024 pref medium
<betawaffle> that src is wrong
<andi-> create a netdev "Internet" with kind VRF, associate it with a routing table (e.g. 42), then set VRF=internet on the internet facing network, Create a l3 device and move one end into the VRF, route via that l3 device
<betawaffle> i've already got a vlan as my wan interface. what's the difference with a vrf?
<andi-> it allows you to have another logical layer of routing and interlinking interfaces
<andi-> all interfaces in the same VRF share the same routing table
<andi-> so if you have a few interfaces that should be able to forward towards each other but nothing else a VRF is a solution for that
<andi-> no need for complicated firewalling or policy routing
<betawaffle> ok, sec, let me reboot my router real quick
<betawaffle> hmm, for some reason i have duplicated routes
<andi-> earlier you said you set up some static prefixes that are working?
<betawaffle> i got rid of those, the SubnetId stuff *seems* to be working
<betawaffle> but again, still get the wrong source address on all outgoing stuff
<betawaffle> any idea where these dups could be coming from, or how i can find where they are coming from? https://paste.sr.ht/~betawaffle/fe02cd3c50255c31c7c98d77bde0cff8faeafc74
<andi-> are you running some sort of routing daemon?
<andi-> those with the timers are probably those that netword installed
<betawaffle> nope
<betawaffle> yeah, the timer ones came from dhcp stuff
<andi-> the device routes do not have proto kernel
<andi-> that is a bit weird
<andi-> so they are likley from userspace
<betawaffle> yeah, but i rebooted :(
<betawaffle> my computer passes ipv6 test
<andi-> yay
thibm has quit [Quit: WeeChat 2.6]
disasm has quit [Quit: WeeChat 2.0]
disasm has joined #nixos-on-your-router