Page MenuHomeVyOS Platform
Feed All Transactions
AuthorObjectTransactionDate
jjakobT2222: openvpn: requires "multihome" option to listen on all addresses with udp protocol
jjakob updated the task description. 
Apr 4 2020, 1:10 PM
jjakobT2222: openvpn: requires "multihome" option to listen on all addresses with udp protocol
jjakob added a project: VyOS 1.3 Equuleus. 
Apr 4 2020, 1:10 PM
jjakobT2222: openvpn: requires "multihome" option to listen on all addresses with udp protocol
jjakob created this task. 
Apr 4 2020, 1:10 PM
jjakobT2222: openvpn: requires "multihome" option to listen on all addresses with udp protocol
jjakob set Difficulty level to Unknown (require assessment). 
Apr 4 2020, 1:10 PM
jjakobT2222: openvpn: requires "multihome" option to listen on all addresses with udp protocol
jjakob claimed this task. 
Apr 4 2020, 1:10 PM
Unknown Object (User)T2197: Cant add vif-s interface into a bridge
Unknown Object (User) edited projects, added VyOS 1.2 Crux (VyOS 1.2.6); removed VyOS 1.3 Equuleus. 
Apr 4 2020, 1:05 PM
Unknown Object (User)T2197: Cant add vif-s interface into a bridge
Unknown Object (User) changed the task status from Open to In progress. 
Apr 4 2020, 1:05 PM
Unknown Object (User)T2197: Cant add vif-s interface into a bridge
Unknown Object (User) added a comment. 
Apr 4 2020, 1:05 PM
c-poT1318: PPPoE client CLI redesign
c-po mentioned this in Restricted Diffusion Commit. 
Apr 4 2020, 12:54 PM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po mentioned this in Restricted Diffusion Commit. 
Apr 4 2020, 12:46 PM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po mentioned this in Restricted Diffusion Commit. 
Apr 4 2020, 12:46 PM
alainlamarT2211: vyos-1x: VHT channel width not set accordingly
alainlamar added a comment. 
Apr 4 2020, 12:01 PM
alainlamarT2212: vyos-1x: WiFi card antenna count not set accordingly
alainlamar added a comment. 
Apr 4 2020, 11:56 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po mentioned this in Restricted Diffusion Commit. 
Apr 4 2020, 11:55 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po mentioned this in Restricted Diffusion Commit. 
Apr 4 2020, 11:55 AM
alainlamarT2213: vyos-1x: WiFi mode ieee80211ac should also activate ieee80211n
alainlamar added a comment. 
Apr 4 2020, 11:46 AM
RaevenT2221: Ability to remove a VRF that has a next-hop-vrf as target
Raeven assigned this task to c-po. 
Apr 4 2020, 10:55 AM
RaevenT2221: Ability to remove a VRF that has a next-hop-vrf as target
Raeven set Difficulty level to Unknown (require assessment). 
Apr 4 2020, 10:54 AM
RaevenT2221: Ability to remove a VRF that has a next-hop-vrf as target
Raeven set Version to VyOS 1.3-rolling-202004031458. 
Apr 4 2020, 10:54 AM
RaevenT2221: Ability to remove a VRF that has a next-hop-vrf as target
Raeven created this task. 
Apr 4 2020, 10:54 AM
RaevenT2221: Ability to remove a VRF that has a next-hop-vrf as target
Raeven added a project: VyOS 1.3 Equuleus. 
Apr 4 2020, 10:54 AM
RaevenT2221: Ability to remove a VRF that has a next-hop-vrf as targetApr 4 2020, 10:54 AM
RaevenT2221: Ability to remove a VRF that has a next-hop-vrf as target
Raeven changed the subtype of this task from "Task" to "Bug". 
Apr 4 2020, 10:54 AM
RaevenT2221: Ability to remove a VRF that has a next-hop-vrf as target
Raeven created this object with edit policy "Custom Policy". 
Apr 4 2020, 10:54 AM
RaevenT2221: Ability to remove a VRF that has a next-hop-vrf as target
Raeven created this object with visibility "Public (No Login Required)". 
Apr 4 2020, 10:54 AM
RaevenT2221: Ability to remove a VRF that has a next-hop-vrf as target
Raeven created this task. 
Apr 4 2020, 10:54 AM
RaevenT2221: Ability to remove a VRF that has a next-hop-vrf as target
Raeven set Is it a breaking change? to Perfectly compatible. 
Apr 4 2020, 10:54 AM
RaevenT2221: Ability to remove a VRF that has a next-hop-vrf as target
Raeven updated the task description. 
Apr 4 2020, 10:54 AM
RaevenT2221: Ability to remove a VRF that has a next-hop-vrf as target
Raeven set Why the issue appeared? to Will be filled on close. 
Apr 4 2020, 10:54 AM
RaevenT2221: Ability to remove a VRF that has a next-hop-vrf as target
Raeven created this object in space S1 VyOS Public. 
Apr 4 2020, 10:54 AM
ViacheslavT2156: PIM op-mode commands
Viacheslav added a comment. 
Apr 4 2020, 10:54 AM
c-poT1318: PPPoE client CLI redesign
c-po mentioned this in Restricted Diffusion Commit. 
Apr 4 2020, 10:39 AM
c-poT2220: PPPoE option "default-route force" not existent in upstream Debian PPP version
c-po closed this task as Invalid. 
Apr 4 2020, 10:34 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing tableApr 4 2020, 10:34 AM
c-poT2220: PPPoE option "default-route force" not existent in upstream Debian PPP version
c-po added a comment. 
Apr 4 2020, 10:34 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po mentioned this in Restricted Diffusion Commit. 
Apr 4 2020, 10:31 AM
c-poT2220: PPPoE option "default-route force" not existent in upstream Debian PPP version
c-po claimed this task. 
Apr 4 2020, 10:27 AM
c-poT2220: PPPoE option "default-route force" not existent in upstream Debian PPP version
c-po updated the task description. 
Apr 4 2020, 10:27 AM
c-poT2220: PPPoE option "default-route force" not existent in upstream Debian PPP version
c-po created this task. 
Apr 4 2020, 10:27 AM
c-poT2220: PPPoE option "default-route force" not existent in upstream Debian PPP version
c-po set Version to 1.3-rolling-202004031458. 
Apr 4 2020, 10:27 AM
c-poT2220: PPPoE option "default-route force" not existent in upstream Debian PPP version
c-po created this task. 
Apr 4 2020, 10:27 AM
c-poT2220: PPPoE option "default-route force" not existent in upstream Debian PPP version
c-po changed the subtype of this task from "Task" to "Bug". 
Apr 4 2020, 10:27 AM
c-poT2220: PPPoE option "default-route force" not existent in upstream Debian PPP version
c-po created this object with edit policy "Custom Policy". 
Apr 4 2020, 10:27 AM
c-poT2220: PPPoE option "default-route force" not existent in upstream Debian PPP version
c-po set Why the issue appeared? to Will be filled on close. 
Apr 4 2020, 10:27 AM
c-poT2220: PPPoE option "default-route force" not existent in upstream Debian PPP version
c-po created this object with visibility "Public (No Login Required)". 
Apr 4 2020, 10:27 AM
c-poT2220: PPPoE option "default-route force" not existent in upstream Debian PPP version
c-po edited this Maniphest Task. 
Apr 4 2020, 10:27 AM
c-poT2220: PPPoE option "default-route force" not existent in upstream Debian PPP version
c-po set Is it a breaking change? to Unspecified (possibly destroys the router). 
Apr 4 2020, 10:27 AM
c-poT2220: PPPoE option "default-route force" not existent in upstream Debian PPP version
c-po added subscribers: c-po, Active contributors, Maintainers. 
Apr 4 2020, 10:27 AM
c-poT2220: PPPoE option "default-route force" not existent in upstream Debian PPP version
c-po added a project: VyOS 1.3 Equuleus. 
Apr 4 2020, 10:27 AM
c-poT2220: PPPoE option "default-route force" not existent in upstream Debian PPP version
c-po set Difficulty level to Easy (less than an hour). 
Apr 4 2020, 10:27 AM
c-poT2220: PPPoE option "default-route force" not existent in upstream Debian PPP version
c-po created this object in space S1 VyOS Public. 
Apr 4 2020, 10:27 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po renamed this task from VRf default route of PPPoE and WWAN interfaces do not get added into proper routing table to VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table. 
Apr 4 2020, 10:25 AM
c-poT2206: Split WireGuard endpoint into proper host and port nodes
c-po moved this task from Need Triage to In Progress on the VyOS 1.3 Equuleus board. 
Apr 4 2020, 10:21 AM
c-poT2213: vyos-1x: WiFi mode ieee80211ac should also activate ieee80211n
c-po moved this task from Need Triage to In Progress on the VyOS 1.3 Equuleus board. 
Apr 4 2020, 10:20 AM
c-poT2213: vyos-1x: WiFi mode ieee80211ac should also activate ieee80211n
c-po added a comment. 
Apr 4 2020, 10:20 AM
c-poT2213: vyos-1x: WiFi mode ieee80211ac should also activate ieee80211n
c-po changed the task status from Open to In progress. 
Apr 4 2020, 10:20 AM
c-poT2213: vyos-1x: WiFi mode ieee80211ac should also activate ieee80211n
c-po claimed this task. 
Apr 4 2020, 10:20 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po moved this task from Need Triage to In Progress on the VyOS 1.3 Equuleus board. 
Apr 4 2020, 10:19 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po changed the task status from Open to In progress. 
Apr 4 2020, 10:19 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po triaged this task as High priority. 
Apr 4 2020, 10:19 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po claimed this task. 
Apr 4 2020, 10:19 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po changed Why the issue appeared? from Will be filled on close to Issues in third-party code. 
Apr 4 2020, 10:19 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po created this object with visibility "Public (No Login Required)". 
Apr 4 2020, 10:19 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po set Is it a breaking change? to Unspecified (possibly destroys the router). 
Apr 4 2020, 10:19 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po added subscribers: c-po, Maintainers, Active contributors. 
Apr 4 2020, 10:19 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po created this task. 
Apr 4 2020, 10:19 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po set Why the issue appeared? to Will be filled on close. 
Apr 4 2020, 10:19 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po updated the task description. 
Apr 4 2020, 10:19 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po changed the subtype of this task from "Task" to "Bug". 
Apr 4 2020, 10:19 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po created this task. 
Apr 4 2020, 10:19 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po added a project: VyOS 1.3 Equuleus. 
Apr 4 2020, 10:19 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po set Difficulty level to Normal (likely a few hours). 
Apr 4 2020, 10:19 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po created this object in space S1 VyOS Public. 
Apr 4 2020, 10:19 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po created this object with edit policy "Custom Policy". 
Apr 4 2020, 10:19 AM
c-poT2219: VRF default route of PPPoE and WWAN interfaces do not get added into proper routing table
c-po set Version to 1.3-rolling-202004031458. 
Apr 4 2020, 10:19 AM
maznuT2218: Add support for the peeringdb module in salt (upgrade salt-minion to 2019.2)
maznu added a comment. 
Apr 4 2020, 9:56 AM
maznuT2218: Add support for the peeringdb module in salt (upgrade salt-minion to 2019.2)
maznu updated the task description. 
Apr 4 2020, 9:55 AM
maznuT2218: Add support for the peeringdb module in salt (upgrade salt-minion to 2019.2)
maznu set Is it a breaking change? to Unspecified (possibly destroys the router). 
Apr 4 2020, 9:54 AM
maznuT2218: Add support for the peeringdb module in salt (upgrade salt-minion to 2019.2)
maznu set Version to -. 
Apr 4 2020, 9:54 AM
maznuT2218: Add support for the peeringdb module in salt (upgrade salt-minion to 2019.2)
maznu added subscribers: maznu, Maintainers, Active contributors. 
Apr 4 2020, 9:54 AM
maznuT2218: Add support for the peeringdb module in salt (upgrade salt-minion to 2019.2)
maznu created this object in space S1 VyOS Public. 
Apr 4 2020, 9:54 AM
maznuT2218: Add support for the peeringdb module in salt (upgrade salt-minion to 2019.2)
maznu set Difficulty level to Unknown (require assessment). 
Apr 4 2020, 9:54 AM
maznuT2218: Add support for the peeringdb module in salt (upgrade salt-minion to 2019.2)
maznu created this task. 
Apr 4 2020, 9:54 AM
maznuT2218: Add support for the peeringdb module in salt (upgrade salt-minion to 2019.2)
maznu updated the task description. 
Apr 4 2020, 9:54 AM
maznuT2218: Add support for the peeringdb module in salt (upgrade salt-minion to 2019.2)
maznu set Why the issue appeared? to Will be filled on close. 
Apr 4 2020, 9:54 AM
maznuT2218: Add support for the peeringdb module in salt (upgrade salt-minion to 2019.2)
maznu created this task. 
Apr 4 2020, 9:54 AM
maznuT2218: Add support for the peeringdb module in salt (upgrade salt-minion to 2019.2)
maznu created this object with edit policy "Custom Policy". 
Apr 4 2020, 9:54 AM
maznuT2218: Add support for the peeringdb module in salt (upgrade salt-minion to 2019.2)
maznu created this object with visibility "Public (No Login Required)". 
Apr 4 2020, 9:54 AM
runarT2215: Make “default no-ipv4-unicast” the default setting
runar added a subscriber: runar. 
Apr 4 2020, 9:49 AM
runarT2216: Containerized third-party applications for VyOS
runar added a subscriber: runar. 
Apr 4 2020, 9:49 AM
c-poT1988: Migrate wirelessmodem to new XML/Python style interface
c-po mentioned this in Restricted Diffusion Commit. 
Apr 4 2020, 9:40 AM
jjakobT2217: Comparing old and new configurations in scripts (daemon reloads and restarts)
jjakob created this object in space S1 VyOS Public. 
Apr 4 2020, 9:38 AM
jjakobT2217: Comparing old and new configurations in scripts (daemon reloads and restarts)
jjakob created this task. 
Apr 4 2020, 9:38 AM
jjakobT2217: Comparing old and new configurations in scripts (daemon reloads and restarts)
jjakob set Why the issue appeared? to Will be filled on close. 
Apr 4 2020, 9:38 AM
jjakobT2217: Comparing old and new configurations in scripts (daemon reloads and restarts)
jjakob triaged this task as Low priority. 
Apr 4 2020, 9:38 AM
jjakobT2217: Comparing old and new configurations in scripts (daemon reloads and restarts)
jjakob set Version to -. 
Apr 4 2020, 9:38 AM
jjakobT2217: Comparing old and new configurations in scripts (daemon reloads and restarts)
jjakob set Difficulty level to Unknown (require assessment). 
Apr 4 2020, 9:38 AM
jjakobT2217: Comparing old and new configurations in scripts (daemon reloads and restarts)
jjakob created this task. 
Apr 4 2020, 9:38 AM
jjakobT2217: Comparing old and new configurations in scripts (daemon reloads and restarts)
jjakob set Is it a breaking change? to Behavior change. 
Apr 4 2020, 9:38 AM
jjakobT2217: Comparing old and new configurations in scripts (daemon reloads and restarts)
jjakob created this object with edit policy "Custom Policy". 
Apr 4 2020, 9:38 AM