related to T2630
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed All Stories
All Stories
All Stories
Jun 23 2020
Jun 23 2020
thomas-mangin added a comment to T2587: Cannot enable the interface when the MTU is set to less than 1280.
vyos@vyos# set interfaces tunnel tun0 description '*** SITE1 ***' [edit] vyos@vyos# set interfaces tunnel tun0 encapsulation 'gre-bridge' [edit] vyos@vyos# set interfaces tunnel tun0 local-ip '10.0.3.239' [edit] vyos@vyos# set interfaces tunnel tun0 remote-ip '10.0.32.240' [edit] vyos@vyos# set interfaces tunnel tun0 ip enable-arp-accept [edit] vyos@vyos# set interfaces tunnel tun0 ip enable-arp-announce [edit]
It would be possible to make the scripts check if IPv6 is enabled on the interface (or system?) and make the minimal MTU 1280 in that case. If IPv6 on the interface is disabled or not supported, have it go as low as it can.
This was discussed already in T2404. The problem is that NICs that expose their min/max MTU are rare. None of the NICs I have expose it, neither through sysfs nor through 'ip -d link show'. If I recap the discussion from T2404, there are 2 main ways to solve this:
a) not have any limitations regarding MTU at all and then detect an error when trying to apply the new MTU. This means no way to verify if the new mtu is correct beforehand so it doesn't comply with the verify/apply separation that's prescribed in the developer docs. I described a possible workaround using revert code in T2404.
b) have a mtu detection script that would be ran by udev on every new NIC detection (to support hotplugging NICs) that would determine the min/max mtu with a bruteforce binary search algorythm (try to set a mtu and see if it errors), then record the results in some temporary file that would get read by the config script. The idea was proposed by @thomas-mangin.
GitHub <noreply@github.com> committed rVYOSONEX70d45cdec426: Merge pull request #471 from thomas-mangin/T2588-fix (authored by dmbaturin).
Viacheslav closed T1829: Install Image script does not respect size of partition greater than 2G but less than disk size as Resolved.
@systo mark as resolved. Reopen it if necessary.
GitHub <noreply@github.com> committed rVYOSONEXe76378f0d46b: Merge pull request #470 from thomas-mangin/T2588-multi (authored by dmbaturin).
thomas-mangin added a comment to T2629: VXLAN interfaces don't actually allow you to configure most settings.
Breaking user existing configs should be a no-no. If the options can be used that way under Linux, then we should not restrict it if it is not invalid. If we intend to prevent it then we would need a way to warn users clearly and we have no framework for this ATM.
Need to add max MTU to operational mode and create a new validator using it and applying it to the xml. The only question being if the information is always available.
I see no issue with the proposed solution.
dsummers added a comment to T1293: Zone-policy implementation does not allow secondary IP on an interface to communicate.
Is this related to T2619? It sure looks like it to me.
Jun 22 2020
Jun 22 2020
A first implementation is already live with the console-server https://github.com/vyos/vyos-1x/blob/current/src/conf_mode/service_console-server.py
GitHub <noreply@github.com> committed rVYOSONEXa8ae4f46a5d0: rip: T2547: rewriten implementation in Python and XML (authored by Viacheslav Hletenko <v.gletenko@vyos.io>).
SIN3R6Y added a comment to T2629: VXLAN interfaces don't actually allow you to configure most settings.
Thinking on this, should ("source-address" / "remote") and ("group" / "source-interface") be mutually exclusive? I cant think of any reason you would want both set to be setup on the same interface, I'm not even sure you can have both. Usually ("source-address" / "remote") would be used for unicast setups, and ("group" / "source-interface") for multicast. Seems like an either or, but not both, setup would be ideal.
SIN3R6Y updated the task description for T2629: VXLAN interfaces don't actually allow you to configure most settings.
Unknown Object (User) claimed T1293: Zone-policy implementation does not allow secondary IP on an interface to communicate.
Unknown Object (User) claimed T1221: BGP - Default route injection is not processed by the specific route-map.
Unknown Object (User) closed T2225: PIM/IGMP documentation, a subtask of T1729: PIM (Protocol Independent Multicast) implementation, as Resolved.
Unknown Object (User) created T2628: Make logs more user friendly..
jjakob changed the subtype of T2627: 'system static-host-mapping' only allows one IP address per hostname, it should allow one IPv4 and one IPv6 simultaneously from "Task" to "Enhancement".
Unknown Object (User) changed the status of T1773: Make it possible to export config to JSON from Open to In progress.
Unknown Object (User) renamed T2626: Changing pseudo-ethernet mode, throws CLI error from Pseudo-ethernet not behaving like it should to Changing pseudo-ethernet mode, throws CLI error.
Unknown Object (User) created T2626: Changing pseudo-ethernet mode, throws CLI error.
This would have been fixed for isc-dhcp-client if T2590 hadn't happened in the process of me working on it, now it requires writing a new dhclient script for the WIDE client.
jjakob changed the status of T1751: DNS server addresses from DHCPv6 are not added to resolv.conf, a subtask of T2464: DNS bugs (parent task), from In progress to Blocked.
jjakob changed the status of T1751: DNS server addresses from DHCPv6 are not added to resolv.conf from In progress to Blocked.
jjakob closed T2054: Changing "system name-server" doesn't update dns forwarding config, neither does "restart dns forwarding", a subtask of T2464: DNS bugs (parent task), as Resolved.
jjakob closed T2054: Changing "system name-server" doesn't update dns forwarding config, neither does "restart dns forwarding" as Resolved.
Fixed as part of T2486
jjakob closed T2463: DHCP-received nameserver not added to vyos-hostsd, a subtask of T2464: DNS bugs (parent task), as Resolved.
Fixed as part of T2486
The above PR419 did not fix the issue as a wrong pdns-recursor process name was used (its real name is 'pdns-rec/worker'). It was fixed as part of T2486.
jjakob closed T2534: pdns-recursor override.conf error, a subtask of T2464: DNS bugs (parent task), as Resolved.
That's great, I like the config syntax. What does the interface alias do regarding the display? Maybe it could be read from the interface description? Then again the display name needs to be short as the displays are small and the interface description can be longer. Maybe default to reading the alias from the interface description and override it with the display alias.
For starting services in 1.3 we use systemd, it's simple to create new service files in src/systemd that will be put in /lib/systemd/system. Just make sure they're started manually by the config script and not as part of a target (just creating a service file without the Install section should ensure that).
GitHub <noreply@github.com> committed rVYOSONEX1d09b1a788cc: Merge pull request #452 from jjakob/T2486-dns-hostsd-fixes (authored by dmbaturin).
Restricted Repository Identity closed T2486: DNS records set via 'system static-host-mapping' return NXDOMAIN from 'service dns forwarding' after a request to a forwarded zone, a subtask of T2464: DNS bugs (parent task), as Resolved.
Restricted Repository Identity closed T2486: DNS records set via 'system static-host-mapping' return NXDOMAIN from 'service dns forwarding' after a request to a forwarded zone as Resolved by committing rVYOSONEX1d09b1a788cc: Merge pull request #452 from jjakob/T2486-dns-hostsd-fixes.
FWIW, this integration package is coming along nicely. I was able to create the XML CLI. The python code is kept to a minimum by passing a dictionary of the Config to the template engine "render". At this point, I can generate the proper LCDd.conf and lcdproc.conf based on the CLI. I now need to work on start/stop/restart as well as (basic) config validation. I have nothing for lcdexec/menu this far.
OK, another approach question.
Jun 21 2020
Jun 21 2020
I feel @Dmitry has more experience here from past topics. I hope you do not mind the reassignment.
c-po reassigned T1995: "show vpn ike sa" command always show child-sas as down from c-po to Unknown Object (User).
c-po moved T2625: Provide generic Library for package builds from Need Triage to In Progress on the VyOS 1.3 Equuleus board.
Or use a VRF T31, closing - feel free to reopen if you think this was done wrongly.
c-po changed the status of T1165: Problem with upgrade on VYOS platform with more than 3 NICs with solution. from Open to In progress.
c-po closed T480: Error if no serial interface is present (/dev/ttyS0: not a tty), a subtask of T2452: Serial console related issues, as Resolved.
Should be resolved via T2569
c-po closed T1739: Serial interface seems not to be deleted properly, a subtask of T2452: Serial console related issues, as Resolved.
Resolved via T2569
c-po changed the status of T2625: Provide generic Library for package builds from Open to In progress.