| === akp55__ is now known as akp55 | ||
| VJ | Hello Every one, Need a quick help with neplan configuration | 06:39 |
|---|---|---|
| VJ | Anyone willing to look into my issue? | 06:40 |
| VJ | anyone? | 06:43 |
| kjetilho | VJ: always better to ask the real question | 08:19 |
| VJ | kjetilho I want to discuss the issue to understand which I think will help me if i speak one on one and explain the issue | 08:23 |
| kjetilho | well, getting someone to volunteer one-on-one support is a lot less likely than getting a response here. | 08:46 |
| VJ | ok I have an ubuntu server 18.04 with 2 interfaces | 08:55 |
| VJ | I am unable to get the interal routing to be working | 08:55 |
| VJ | here is my yaml file | 08:55 |
| VJ | network: ethernets: ens160: addresses: [172.16.1.181/24] dhcp4: no gateway4: 172.16.1.254 nameservers: addresses: [172.16.1.241] routes: - to: 172.16.1.0/24 via: 172.16.1.254 table: 101 routing-policy: - from: 172.16.1.0 table: 101 ens192: addresses: | 08:56 |
| VJ | [192.168.1.126/24] dhcp4: no routes: - to: 192.168.1.0 via: 192.168.1.254 metric: 100 table: 102 - to: 233.0.0.0/8 via: 192.168.1.254 metric: 100 table: 103 routing-policy: - from: 192.168.1.0/24 table: 102 - from: 233.0.0.0/8 table: 103 version: 2 | 08:56 |
| VJ | what am i doing wrong? | 08:56 |
| kjetilho | do you really need this policy-routing? | 09:04 |
| VJ | well i tried without policy-routing and that didnt help | 09:05 |
| kjetilho | it's easier to read if you put the YAML in a gist on Github og snippet on Gitlab, or on a a pastebin like paste.debian.net | 09:05 |
| kjetilho | what do you want to achieve? | 09:06 |
| VJ | I am not able to reach a server which is in 233.x.x.x | 09:07 |
| VJ | if i put metric then i can reach 233.x.x.x but i lose internet connectivity | 09:07 |
| kjetilho | you should be able to add a route to 233.0.0.0/8 to the nic of your choice without any policy routing | 09:09 |
| kjetilho | you only need policy routing if locking in the source address is important. | 09:10 |
| kjetilho | sorry, I have to go back to real work :) | 09:11 |
| VJ | http://paste.debian.net/hidden/9b82afa5/ | 09:11 |
| VJ | could you plz look at it and let me know the changes | 09:11 |
| VJ | i will try quickly and update | 09:11 |
| VJ | I removed policy routing as well | 09:13 |
| VJ | http://paste.debian.net/1177458/ | 09:13 |
| VJ | didnt help | 09:13 |
| VJ | anyone ? | 10:16 |
| VJ | help me with routing issues in netplan ? | 10:16 |
| VJ | http://paste.debian.net/1177458/ | 10:16 |
| slyon | VJ is the static route you defined for ens160 your default gateway? Can you paste the output of "ip route"? | 10:21 |
| VJ | paste.debian.net/1177463 | 10:22 |
| VJ | this is the route output | 10:22 |
| VJ | and yes that the default gw | 10:23 |
| VJ | thats the interface which is connected to internet | 10:23 |
| VJ | the other interface is for internal network | 10:23 |
| VJ | i can reach internet with the current config but not to local network | 10:23 |
| VJ | specifically to 233.x.x.x netowrk even though i have put a route in place | 10:24 |
| slyon | can you analyse via "traceroute SERVER_IP"? To see where the packets are flowing to? | 10:26 |
| VJ | http://paste.debian.net/1177466/ | 10:27 |
| VJ | this is the output of traceroute | 10:27 |
| slyon | hmm.. okay that's not helpful. Why did you define "gateway4: 172.16.1.254" and the additional static route to 172.16.1.254? Both are your route to the internet right? Maybe try to get rid of the "gateway4" then, it might confuse the system | 10:30 |
| VJ | i did that as well. thta didnt help | 10:31 |
| VJ | now i ahve removed the route for the default gateway | 10:31 |
| VJ | even now, i can reach internet but not to 233.x.x.x | 10:31 |
| slyon | you removed the static route, or the "gateway4" setting? I'd recommend to remove the "gateway4" setting and only define routes manually, as the gateway setting does some magic in networkd, which might not play nicely with other routes | 10:32 |
| kjetilho | 233.x.x.x is a magic subnet - I would not use it - it is part of the space allocated to multicast | 10:33 |
| VJ | yes 233 is the server which is used for some video streaming | 10:43 |
| VJ | i see in some of the forms where netplan doesn't support multicast routing | 10:43 |
| VJ | is this true ? | 10:43 |
| VJ | if yes then i wasted my 3days :) | 10:43 |
| kjetilho | multicast routing is very different from normal routing | 10:45 |
| kjetilho | i haven't done it since 1996 or thereabouts, so I have no idea how it is best done these days | 10:46 |
| slyon | I'm not sure about multicast routing either.. this ticket suggests that you need to define the device/on-link instead of a gateway for multicast routes: https://bugs.launchpad.net/netplan/+bug/1833475 | 10:49 |
| VJ | ya i saw this and tried as well | 10:51 |
| VJ | didnt help | 10:51 |
| VJ | i added on-link: true | 10:51 |
| VJ | no luck | 10:51 |
| VJ | anyone else who has information about multicast routing in netplan ? | 11:05 |
| VJ | any one ? know can help with multicast routing in netplan? | 11:27 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!