Page MenuHomeVyOS Platform

g.skupien (Gabriel Skupien)
Disabled

Projects

User Details

User Since
Apr 3 2020, 9:07 AM (34 w, 2 d)
Roles
Disabled

Recent Activity

Jun 11 2020

g.skupien renamed T2587: Cannot enable the interface when the MTU is set to less than 1280 from Cannot enable the interface when the MTU is set to Cannot enable the interface when the MTU is set to less than 1280.
Jun 11 2020, 7:20 PM · VyOS 1.3 Equuleus
g.skupien claimed T2587: Cannot enable the interface when the MTU is set to less than 1280.
Jun 11 2020, 7:02 PM · VyOS 1.3 Equuleus
g.skupien created T2587: Cannot enable the interface when the MTU is set to less than 1280.
Jun 11 2020, 7:01 PM · VyOS 1.3 Equuleus

Jun 9 2020

g.skupien added a comment to T2515: Ethernet interface is automatically disabled when removing it from bond.

PR: https://github.com/vyos/vyos-1x/pull/449

Jun 9 2020, 8:59 PM · VyOS 1.3 Equuleus

Jun 4 2020

g.skupien added a comment to T2515: Ethernet interface is automatically disabled when removing it from bond.

One more question/proposition.
Before ethX is added to the bond its IP addresses are being removed (that's good). Then, when ethX is removed from the bond it is being left as disabled. If we manually re-enable that interface the interfaces-ethernet.py script is run and it configures all its settings (including IPv6 link-local address). Therefore, maybe it is not that bad idea to leave the interface disabled when it leaves the bond. So, what if we just add a warning message to inform users that bond leaving interface will stay disabled until it is manually re-enabled.

Jun 4 2020, 2:03 PM · VyOS 1.3 Equuleus
g.skupien added a comment to T2476: Bond member description change leads to network outage.

PR for 1.2: https://github.com/vyos/vyatta-cfg-system/pull/124

Jun 4 2020, 8:36 AM · VyOS 1.2 Crux (VyOS 1.2.6), VyOS 1.3 Equuleus
g.skupien closed T2514: "mac" setting for bond members as Resolved.
Jun 4 2020, 8:33 AM · VyOS 1.3 Equuleus
g.skupien added a comment to T2527: bonding: the last slave interface is not deleted.

PR: https://github.com/vyos/vyos-1x/pull/442

Jun 4 2020, 8:29 AM · VyOS 1.3 Equuleus

May 28 2020

g.skupien renamed T2515: Ethernet interface is automatically disabled when removing it from bond from IPv6 link-local address is gone after removing the interfaces from bond to Ethernet interface is automatically disabled when removing it from bond.
May 28 2020, 8:37 PM · VyOS 1.3 Equuleus
g.skupien added a comment to T2515: Ethernet interface is automatically disabled when removing it from bond.

I just did a few more tests and the reason why IPv6 is gone is that the interface is being automatically disabled after it leaves bond membership. I will change the description accordingly.

May 28 2020, 8:34 PM · VyOS 1.3 Equuleus
g.skupien added a comment to T2515: Ethernet interface is automatically disabled when removing it from bond.

@jjakob, thanks for your opinion. What if we just add a couple of lines into the apply() function in the interfaces-bonding.py:
https://github.com/vyos/vyos-1x/compare/current...L6NqLW:T2515?expand=1

May 28 2020, 7:51 PM · VyOS 1.3 Equuleus

May 27 2020

g.skupien changed the status of T2527: bonding: the last slave interface is not deleted from Open to Confirmed.
May 27 2020, 8:53 PM · VyOS 1.3 Equuleus
g.skupien changed the status of T2515: Ethernet interface is automatically disabled when removing it from bond from Open to Confirmed.
May 27 2020, 8:53 PM · VyOS 1.3 Equuleus
g.skupien claimed T2527: bonding: the last slave interface is not deleted.
May 27 2020, 8:10 PM · VyOS 1.3 Equuleus
g.skupien created T2527: bonding: the last slave interface is not deleted.
May 27 2020, 8:10 PM · VyOS 1.3 Equuleus

May 26 2020

g.skupien added a comment to T2514: "mac" setting for bond members.

PR created, https://github.com/vyos/vyos-1x/pull/431.

May 26 2020, 10:24 AM · VyOS 1.3 Equuleus

May 25 2020

g.skupien claimed T2515: Ethernet interface is automatically disabled when removing it from bond.
May 25 2020, 9:06 PM · VyOS 1.3 Equuleus
g.skupien created T2515: Ethernet interface is automatically disabled when removing it from bond.
May 25 2020, 9:06 PM · VyOS 1.3 Equuleus
g.skupien created T2514: "mac" setting for bond members.
May 25 2020, 8:09 PM · VyOS 1.3 Equuleus
g.skupien changed the status of T2476: Bond member description change leads to network outage from Confirmed to Backport candidate.

@jjakob, yes, thank you.
PR for 1.3: https://github.com/vyos/vyos-1x/pull/434
I will summit PR for 1.2 once 1.3 is released and tested.

May 25 2020, 9:48 AM · VyOS 1.2 Crux (VyOS 1.2.6), VyOS 1.3 Equuleus

May 19 2020

g.skupien claimed T2476: Bond member description change leads to network outage.
May 19 2020, 1:51 PM · VyOS 1.2 Crux (VyOS 1.2.6), VyOS 1.3 Equuleus
g.skupien changed the status of T2476: Bond member description change leads to network outage from Open to Confirmed.
May 19 2020, 12:19 PM · VyOS 1.2 Crux (VyOS 1.2.6), VyOS 1.3 Equuleus
g.skupien added a comment to T2476: Bond member description change leads to network outage.

@runar, thanks for clarification! I will change the initial description accordingly.

May 19 2020, 12:12 PM · VyOS 1.2 Crux (VyOS 1.2.6), VyOS 1.3 Equuleus

May 18 2020

g.skupien added a project to T2476: Bond member description change leads to network outage: VyOS 1.3 Equuleus.
May 18 2020, 8:52 PM · VyOS 1.2 Crux (VyOS 1.2.6), VyOS 1.3 Equuleus
g.skupien created T2476: Bond member description change leads to network outage.
May 18 2020, 8:51 PM · VyOS 1.2 Crux (VyOS 1.2.6), VyOS 1.3 Equuleus

May 9 2020

g.skupien claimed T377: DHCP-relay agent package replacement.
May 9 2020, 10:21 AM · VyOS 1.3 Equuleus
g.skupien claimed T1978: dhcp-relay doesn't need multiple interfaces.
May 9 2020, 10:15 AM · Restricted Project, vyatta-cfg-dhcp-relay
g.skupien updated subscribers of T1978: dhcp-relay doesn't need multiple interfaces.

@dmbaturin @c-po
Not sure why did we merge these PRs. The isc-dhcp-relay does require at least two interfaces to work. This was discussed in details in T1276 and T2408.
As result the latest documentation is inaccurate what could make users confused.

May 9 2020, 10:13 AM · Restricted Project, vyatta-cfg-dhcp-relay

May 8 2020

g.skupien added a comment to T2440: VyOS on Proxmox.

I forget - I did not observe any disability in router behavior. At least with simple configuration that I tested.
Observed messages may be a bit worrying for users at the very beginning of using VyOS.

May 8 2020, 7:54 PM
g.skupien created T2440: VyOS on Proxmox.
May 8 2020, 7:39 PM
g.skupien merged T1945: FRR: Committing large number of peers in configuration results in temporarily incomplete config resulting in route leaks into T2215: Make “default no-ipv4-unicast” the default setting.
May 8 2020, 7:09 PM · VyOS 1.3 Equuleus
g.skupien merged task T1945: FRR: Committing large number of peers in configuration results in temporarily incomplete config resulting in route leaks into T2215: Make “default no-ipv4-unicast” the default setting.
May 8 2020, 7:09 PM · VyOS 1.3 Equuleus
g.skupien added a comment to T1945: FRR: Committing large number of peers in configuration results in temporarily incomplete config resulting in route leaks.

This can be mitigated by:

  1. add to ALL ipv4 peers "address-family ipv4-unicast" set
May 8 2020, 7:08 PM · VyOS 1.3 Equuleus
g.skupien merged T1698: prefix-list and/or route-map not configured before referencing BGP neighbor is configured (BGP session established before filters applied) into T1945: FRR: Committing large number of peers in configuration results in temporarily incomplete config resulting in route leaks.
May 8 2020, 6:41 PM · VyOS 1.3 Equuleus
g.skupien merged task T1698: prefix-list and/or route-map not configured before referencing BGP neighbor is configured (BGP session established before filters applied) into T1945: FRR: Committing large number of peers in configuration results in temporarily incomplete config resulting in route leaks.
May 8 2020, 6:41 PM
g.skupien added a comment to T1698: prefix-list and/or route-map not configured before referencing BGP neighbor is configured (BGP session established before filters applied).

I confirm that this can be mitigated by:

  1. add to ALL ipv4 peers "address-family ipv4-unicast" set
set protocols bgp xxxxxx neighbor x.x.x.x address-family ipv4-unicast
  1. disable default ipv4 peering
set protocols bgp xxxxxx parameters default no-ipv4-unicast
May 8 2020, 6:40 PM
g.skupien claimed T1698: prefix-list and/or route-map not configured before referencing BGP neighbor is configured (BGP session established before filters applied).
May 8 2020, 10:54 AM

May 4 2020

g.skupien added a comment to T1276: dhcp relay + VLAN fails.

@Gislaved, I have just tested it on the KVM (proxmox) with VirtIO and I coudn't reproduce it. It works with exactly the same defects as I mentioned in my previous message. Tested on the both LTS and 1.3-rolling-202005031216.

May 4 2020, 7:19 PM · VyOS 1.3 Equuleus

Apr 30 2020

g.skupien updated subscribers of T2408: DHCP Relay upstream and downstream interfaces.
Apr 30 2020, 7:56 PM · VyOS 1.3 Equuleus
g.skupien added a comment to T1276: dhcp relay + VLAN fails.

Enhancement created.
Question to ISC submitted (https://gitlab.isc.org/isc-projects/dhcp/-/issues/104)

Apr 30 2020, 7:49 PM · VyOS 1.3 Equuleus
g.skupien triaged T2408: DHCP Relay upstream and downstream interfaces as Normal priority.
Apr 30 2020, 7:15 PM · VyOS 1.3 Equuleus
g.skupien added a comment to T1276: dhcp relay + VLAN fails.

@ddiguru
I confirm all the issues that you have observed. I was able to reproduce them in the both our LTS and currect rolling releases.

  1. Issue with a wrong giaddr address. This sounds like a bug in the isc-dhp-relay package. Fortunately, those extra packets with a wrong giaddr address could be eliminated in newer versions by using "-id" and "-iu" instead of muliple "-i" options. isc-dhcp-relay allows for this since v4.3.5. I will create a Feature Request to modify the VyOS config syntax and isc-dhcp-relay config file accordingly. In the meantime I will try to confirm with ISC people that this indeed is a bug.
  2. Issue with duplicate packets. isc-dhp-relay seems to unnecessarily relay unicast packets (I have no idea why it does so). That's why you see all unicast packets doubled. Looks like another bug :) The good news is that it is more cosmetic issue. I already submitted the ticket for it (https://gitlab.isc.org/isc-projects/dhcp/-/issues/102)
Apr 30 2020, 7:04 PM · VyOS 1.3 Equuleus

Apr 28 2020

g.skupien closed T1227: rip PW can't be set at interface config as Resolved.

This is solved in both the current LTS and rolling releases.

Apr 28 2020, 7:50 PM · VyOS 1.3 Equuleus

Apr 27 2020

g.skupien closed T1381: Enable DHCP option 121 processing as Resolved.

The issue has been solved by the above merge.

Apr 27 2020, 7:26 PM · VyOS 1.3 Equuleus

Apr 13 2020

g.skupien added a comment to T1381: Enable DHCP option 121 processing.

Test results on the VyOS 1.3-rolling-202004020117:
Basically, the DHCP option 121 is handled as expected but two issues were observed i.e.:

  1. Static routes advertised by the DHCP server in option 121 are not automatically removed from the FIB when the "address dhcp" setting is removed from the interface. Disable/enable the interface doesn't change anything. The only option to get rid of them is to restart the router.

A similar behavior is observed when the "address dhcp" config is replaced with static IP address in one go. In that case disable/enable the interface at least makes them removed from the FIB but they are still present in the FRR as "inactive" . The only option to get rid of them is to restart the router.

Apr 13 2020, 10:04 AM · VyOS 1.3 Equuleus

Apr 7 2020

g.skupien closed T1114: VyOS 1.2 tftp issue, NAT client could not boot via tftp server, same setup on VyOS 1.1.8 works fine as Resolved.

The automatic helper assignment is enabled in both the LTS and the current rolling releases. The only thing that is needed to make the TFTP working is to allow the udp/69 and "related" traffic.

Apr 7 2020, 8:02 PM
g.skupien closed T1095: Connection tracking NAT / FIREWALL as Resolved.

The automatic helper assignment is enabled in both the LTS and the current rolling releases. The only thing that is needed to make the FTP working is to allow the tcp/21, "related" and "established" traffic.

Apr 7 2020, 6:28 PM

Apr 5 2020

g.skupien closed T1693: DNS Forwarding Services not responding with Allow-From as Invalid.

I was not able to recreate that issue. Both /24 and /8 networks were tested.
All the tests have been done on the VyOS 1.3-rolling-202004020117.

Apr 5 2020, 9:42 AM · VyOS 1.3 Equuleus