| fffeeeee | hello guys, I am having trouble translating this configuration to netplan: https://docs.hetzner.com/robot/dedicated-server/network/net-config-debian/#routed-brouter | 14:26 |
|---|---|---|
| fffeeeee | can you help me out? is there a comparison tool that can tell what is the effective difference between an interfaces and netplan configuration? | 14:28 |
| slyon | hey fffeeeee! netplan had a ifupdown-migrate script... but I'm not sure this still exists today... | 14:36 |
| slyon | can you specify the problem a bit more? Is there any specific interface which does not work as intended? | 14:37 |
| fffeeeee | slyon it's not clear to me where should I add hierarchically the bridge settings, under the main eth0 > bridges, or should i just define a virbr1 next to eth0? | 14:53 |
| slyon | yes, you would define it next to eth, i.e. you would have "ethernets->eth0" and "bridges->virbr1" definitions in your netplan YAML config, compare to: https://netplan.io/reference/#properties-for-device-type-bridges%3A | 14:55 |
| fffeeeee | ok thank you! the hierarchical levels in whitespace configuration files (including yaml) always confuse me | 14:58 |
| === akp55_ is now known as akp55__ | ||
| sakth | Hi, how to persistently disable/bring down an interface without removing its entries from netplan.yaml? | 17:45 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!