| slyon | I'm glad you found the answer about initramfs-tools creating /run/netplan/intname.yaml on askubuntu.com! | 08:15 |
|---|---|---|
| slyon | PeGaSuS: I'm not sure if I fully get your question... but as kjetilho said, you should not be using two "gateway6"/default routes. In a situation like this you should rather manually define your routes and assign corresponding metrics/priorities accordingly, instead of having conflicting gateway6 definitions | 08:24 |
| PeGaSuS | slyon: well, honestly I've never had to do anything related to networking. so I just followed the instructions from tunnelbroker. I suppose that the tunnel gateway6 is also needed? the rest on en0 was already there, for the exception of the tunnel IPS that I've added | 08:26 |
| PeGaSuS | also all the routes were there since day 1 | 08:27 |
| slyon | Have then tunnel "gateway6" and eno0 "gateway6" been there from the start? | 08:29 |
| PeGaSuS | en0 gateway6 is there from the start. the tunnel gateway6 was added by me | 08:30 |
| PeGaSuS | default config since day one was: https://paste.ubuntu.com/p/vCNg8nkBN5/ | 08:35 |
| PeGaSuS | I know it's probably a mess, but blame Kimsufi. it's how they deliver the vps | 08:35 |
| PeGaSuS | in this case it's even a dedicated box | 08:36 |
| kjetilho | well, if *all* your via values for the individual routes are the same as your gateway6 value, the extra routes are superfluous. | 08:41 |
| kjetilho | (I would do a grep to check, but paste.ubuntu.com requires me to login using an Ubuntu One account to download as text(!) | 08:42 |
| slyon | Okay, so you added all the tunnel config, incl gateway6. Which default gateway do you want to use? Do you want to route your traffic via the eno0 network or via the tunnel network? I guess you should remove/comment the gateway6, which you do NOT want to use | 08:45 |
| PeGaSuS | kjetilho: https://termbin.com/iipi | 08:46 |
| PeGaSuS | slyon: if I remove the gateway6 from the tunnel can I still use the /64 subnet from the tunnel? | 08:47 |
| kjetilho | PeGaSuS: is this tunnel a general tunnel or just for access to some internal networks? | 08:47 |
| PeGaSuS | general tunnel, for outgoing connections | 08:48 |
| kjetilho | general tunnel as in "usable to access the whole of Internet" | 08:48 |
| slyon | PeGaSuS: Yes, if you define a route to that /64 subnet, via your GW address | 08:48 |
| slyon | PeGaSuS: but as you seem to want to use the tunnel by default, I'd suggest keeping the gateway6 in the tunnel config, but removing it from the eno0 network | 08:49 |
| PeGaSuS | but if I define the GW for the tunnel subnet I stop having the 1 native IPv6? | 08:49 |
| kjetilho | what is your native IPv6? | 08:49 |
| slyon | why is that? | 08:50 |
| kjetilho | ahhh, now I get it. so 2001:41d0:a:f5d3::/58 is the stuff which should *not* go via the he-tunnel | 08:51 |
| PeGaSuS | exactly. that's the IPv6 assigned natively to the machine | 08:51 |
| PeGaSuS | and I'd love to use the native IPv6 and also the IPv6 /64 subnet from the tunnel in simultaneous | 08:52 |
| kjetilho | the list of subnets make my head hurt. what would break if you tried to route all OVH traffic using your native IPv6? 2001:41d0::/44 is the block in whois. | 08:52 |
| kjetilho | (the computer doesn't mind the long list, though.) | 08:53 |
| PeGaSuS | I have no idea. I don't know if Kimsufi would be very pleased with that though | 08:53 |
| kjetilho | oh! the long list is there to avoid a route entry for 2001:41d0:a:f5ff:ff:ff:ff:ff itself | 08:54 |
| PeGaSuS | I've asked them for a native /64 subnet, but no answer until now (only 12h have passed) | 08:55 |
| kjetilho | I should have noticed the "countdown" earlier :) | 08:55 |
| PeGaSuS | I really don't understand why Kimsufi only gives one IPv6 address. probably because they rely on OVH network? | 08:59 |
| kjetilho | I don't understand why you have a /58 for your address. that is highly unusual | 08:59 |
| PeGaSuS | Kimsufi stupidity? :x | 08:59 |
| kjetilho | what is Kimsufi? | 09:00 |
| PeGaSuS | they're like an OVH subsidiary probably. the dedi box is from them | 09:00 |
| PeGaSuS | so, I asked for a /64 IPv6 subnet from Kimsufi (which seems to have some kind of relationship with OVH) and they kindly refused and said that if I want a /64 I should buy a dedicated server from OVH which is only like 6x expensive. | 16:16 |
| kjetilho | so you have a single address inside a /58? | 16:17 |
| PeGaSuS | yep, that's it | 16:17 |
| kjetilho | that's really weird | 16:17 |
| kjetilho | of course, the /58 only has room for 64 /64-subnets, so they would need a bigger allocation to start with | 16:18 |
| PeGaSuS | so, I guess I'm stuck with tunnelbroker. so, about the gateway6 thing, I should only have one at a time. but with my very limited knowledge about networking if I remove the native gateway6, will the native IPv6 be usable? what if I remove the tunnel gateway6? | 16:20 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!