Page MenuHomePhabricator

mb300sd (mb300sd)
User

Projects

User does not belong to any projects.

User Details

User Since
May 19 2017, 3:54 AM (126 w, 12 h)

Recent Activity

Fri, Sep 27

mb300sd added a comment to T1672: Wireguard keys not automatically moved.

Been pretty busy lately, but ran a quick test tonight. Wireguard keys are properly moved in my VM.

Fri, Sep 27, 3:54 AM · VyOS 1.3 Equuleus

Thu, Sep 19

mb300sd added a comment to T1672: Wireguard keys not automatically moved.

Already fixed manually, but I can test on yesterday's vm backup if needed.

Thu, Sep 19, 9:15 PM · VyOS 1.3 Equuleus
mb300sd added a comment to T1673: vif bridge-group not migrated to bridge member interface.

Not sure what you mean by pre and post-commit config blocks.

Thu, Sep 19, 8:43 PM · VyOS 1.3 Equuleus
mb300sd created T1674: Support [virtual] dvd device in add system image.
Thu, Sep 19, 8:02 PM · VyOS 1.3 Equuleus
mb300sd added a comment to T1673: vif bridge-group not migrated to bridge member interface.

The loading error is caused by bridging a l2tpv3 interface, didn't see the cause at first because of the other errors. Since the bridge is now created at priority 470, and l2tpv3 is 800, when before an interface would be added to the bridge as it is created.

Thu, Sep 19, 7:56 PM · VyOS 1.3 Equuleus
mb300sd added a comment to T1673: vif bridge-group not migrated to bridge member interface.

After adding the vif to bridge member interfaces, I get a config load error on boot. Running config, load, commit, works. Something to do with the order the configs get applied?

Thu, Sep 19, 7:04 PM · VyOS 1.3 Equuleus
mb300sd renamed T1673: vif bridge-group not migrated to bridge member interface from bridge-group missing from vif to vif bridge-group not migrated to bridge member interface.
Thu, Sep 19, 6:59 PM · VyOS 1.3 Equuleus
mb300sd changed Is it a breaking change? from behavior to syntax on T1673: vif bridge-group not migrated to bridge member interface.
Thu, Sep 19, 6:55 PM · VyOS 1.3 Equuleus
mb300sd added a comment to T1673: vif bridge-group not migrated to bridge member interface.

Just noticed bridge has a member interface parameter now. The vif bridge-group config was not migrated.

Thu, Sep 19, 6:55 PM · VyOS 1.3 Equuleus
mb300sd created T1673: vif bridge-group not migrated to bridge member interface.
Thu, Sep 19, 6:51 PM · VyOS 1.3 Equuleus
mb300sd created T1672: Wireguard keys not automatically moved.
Thu, Sep 19, 6:49 PM · VyOS 1.3 Equuleus

Sep 5 2019

mb300sd added a comment to T770: Bonded interfaces get updated with incorrect hw-id in config..

@hagbard I no longer have the hardware the issue was found on, or anything else with identical interfaces to bond at the moment.

Sep 5 2019, 12:15 AM · VyOS 1.2 Crux, VyOS 1.3 Equuleus

Jul 20 2019

mb300sd added a comment to T1497: "set system name-server" generates invalid/incorrect resolv.conf.

I wonder if the bgp daemon is being started before the hostname is changed by the config script. Seems possible since we added a lock so it executes later.

Jul 20 2019, 1:16 AM · VyOS 1.3 Equuleus
mb300sd added a comment to T1497: "set system name-server" generates invalid/incorrect resolv.conf.

@zsdc Hostname is still showing as 'debian' in 1.2.0-rolling+201907191807

Jul 20 2019, 1:13 AM · VyOS 1.3 Equuleus

Jul 18 2019

mb300sd added a comment to T1458: Regression in 1.2.1-S2 hostname & logging.

@zsdc Rolling builds appear to be broken. ( T1533 ) Nothing newer than 201907150337.

Jul 18 2019, 6:09 PM
mb300sd created T1533: Rolling builds broken!.
Jul 18 2019, 6:08 PM · VyOS 1.3 Equuleus

Jul 15 2019

mb300sd added a comment to T1497: "set system name-server" generates invalid/incorrect resolv.conf.

Noticed this today. Possibly another related bug, seems to have appeared the same time the previous ones were fixed. Hostname in bgp is showing up as 'debian', the hostname command, /etc/hostname, /etc/resolv.conf show the correct hostname.

Jul 15 2019, 5:59 PM · VyOS 1.3 Equuleus

Jul 11 2019

mb300sd created T1520: Advanced network monitoring: nTop or similar.
Jul 11 2019, 4:54 PM · VyOS 1.3 Equuleus

Jul 8 2019

mb300sd added a comment to T1497: "set system name-server" generates invalid/incorrect resolv.conf.

Had a long 4th of July weekend, but the issue appears to be resolved in 1.2.0-rolling+201907080337.

Jul 8 2019, 2:46 AM · VyOS 1.3 Equuleus

Jul 3 2019

mb300sd added a comment to T1504: DHCP-provided DNS servers are not propagated to resolv.conf.

Possibly a related problem here in T1497, we're still chasing an issue where disable-dhcp-nameservers isn't working on startup.

Jul 3 2019, 2:47 AM · VyOS 1.3 Equuleus, VyOS 1.2 Crux (VyOS 1.2.2)

Jul 2 2019

mb300sd added a comment to T1497: "set system name-server" generates invalid/incorrect resolv.conf.

Yeah, that's the one I just installed.

Jul 2 2019, 9:16 PM · VyOS 1.3 Equuleus
mb300sd added a comment to T1497: "set system name-server" generates invalid/incorrect resolv.conf.

Still using the dhcp servers on 1.2.0-rolling+201907022116. Will post back in a few hours if the one with a bunch of lines happens again.

Jul 2 2019, 8:51 PM · VyOS 1.3 Equuleus
mb300sd added a comment to T1497: "set system name-server" generates invalid/incorrect resolv.conf.

Not sure when the messed up one with all the lines happens, it wasn't right after commit, seemed to be after sitting for a few hours, but it was broken again when I tried to add system image just now.

Jul 2 2019, 8:40 PM · VyOS 1.3 Equuleus
mb300sd added a comment to T1497: "set system name-server" generates invalid/incorrect resolv.conf.

@UnicronNL yes. On boot it creates the resolv.conf with DHCP nameservers and missing the domain/search options. If I commit, it generates one with my configured servers and the domain/search options.

Jul 2 2019, 8:36 PM · VyOS 1.3 Equuleus
mb300sd added a comment to T1497: "set system name-server" generates invalid/incorrect resolv.conf.

Updated to latest rolling, 1.2.0-rolling+201907020337

Jul 2 2019, 2:40 AM · VyOS 1.3 Equuleus

Jul 1 2019

mb300sd added a comment to T1497: "set system name-server" generates invalid/incorrect resolv.conf.

IPv6 is all static - he.net tunnels. Will try the rolling when it's up.

Jul 1 2019, 6:09 PM · VyOS 1.3 Equuleus
mb300sd added a comment to T1497: "set system name-server" generates invalid/incorrect resolv.conf.

It's at&t's dhcp server, I have no idea what they run.

Jul 1 2019, 5:03 PM · VyOS 1.3 Equuleus

Jun 30 2019

mb300sd added a comment to T1497: "set system name-server" generates invalid/incorrect resolv.conf.

The difference might be because my IPv6 server is first, but I'm also experiencing the non-update when I try to add 1.1.1.1 to see if having an IPv4 server first helps.

Jun 30 2019, 7:59 PM · VyOS 1.3 Equuleus

Jun 29 2019

mb300sd created T1497: "set system name-server" generates invalid/incorrect resolv.conf.
Jun 29 2019, 8:49 PM · VyOS 1.3 Equuleus

Jun 26 2019

mb300sd added a comment to T1458: Regression in 1.2.1-S2 hostname & logging.

I think there's still an issue in the latest rolling. The hostname is not being set to the one in the config.

Jun 26 2019, 1:22 AM

Jun 25 2019

mb300sd changed the subtype of T1466: Add EAPOL login support from "Task" to "Feature Request".
Jun 25 2019, 11:13 PM · VyOS 1.3 Equuleus
mb300sd added a project to T1466: Add EAPOL login support: VyOS 1.2 Crux.

Trying to figure out how to do this via xml. Seems like it generates the .def files from the xml Does it require rebuilding the whole image to test?

Jun 25 2019, 11:13 PM · VyOS 1.3 Equuleus

Jun 21 2019

mb300sd created T1466: Add EAPOL login support in the S1 VyOS Public space.
Jun 21 2019, 6:32 PM · VyOS 1.3 Equuleus

Jun 16 2019

mb300sd created T1441: Add support for IPSec XFRM interfaces.
Jun 16 2019, 10:07 PM · VyOS 1.3 Equuleus

Mar 28 2019

mb300sd added a comment to T1317: OpenVPN configuration fails if it depends on another interface..

Not sure if the l2tp/vti modification merits inclusion - that depends on personal configuration of which tunnel is inside the other. I think the original config is correct for the more common use case of having l2tp secured by ipsec.

Mar 28 2019, 3:57 PM · VyOS 1.3 Equuleus
mb300sd added a comment to T1317: OpenVPN configuration fails if it depends on another interface..

That worked, thanks. Had to set it to 901, the vpn node was 900. Added a sed to the preconfig script so it survives updates.

Mar 28 2019, 3:26 AM · VyOS 1.3 Equuleus

Mar 27 2019

mb300sd added a comment to T1317: OpenVPN configuration fails if it depends on another interface..

I switched to a L2TPv3 tunnel for better performance than OpenVPN, still will not come up at boot if it depends on the vti interface.

Mar 27 2019, 7:14 PM · VyOS 1.3 Equuleus

Mar 26 2019

mb300sd added a comment to T1317: OpenVPN configuration fails if it depends on another interface..

Probably not the most common config, but I already have IPSec tunnels between all my sites, but need the L2 bridge and ovpn's fragmentation for my TV STB to function correctly through a tunnel. Perhaps adding a depends-on-interface option to all interfaces would be the most generic way to resolve this. I will try and see how difficult this is to implement in the config scripts when I have some time in the next week or 2.

Mar 26 2019, 8:35 PM · VyOS 1.3 Equuleus
mb300sd created T1317: OpenVPN configuration fails if it depends on another interface. in the S1 VyOS Public space.
Mar 26 2019, 8:29 PM · VyOS 1.3 Equuleus

Oct 7 2018

mb300sd added a comment to T852: Router responding to arp requests for all addresses, breaks Windows networking!.

I also have ipsec/vti.

Oct 7 2018, 9:20 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc2)
mb300sd added a comment to T852: Router responding to arp requests for all addresses, breaks Windows networking!.

I rechecked the solarflare card - issue still exists. Didn't catch it last time because my config got a little messed up with all the image swapping.

Oct 7 2018, 7:04 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc2)

Oct 3 2018

mb300sd added a comment to T852: Router responding to arp requests for all addresses, breaks Windows networking!.

Finally got back up here to test. Swapped out the Mellanox NIC with a Solarflare card on latest, works. 201807292210 image with Mellanox card, works. Latest image and different Mellanox card, broken. Definitely looks like a driver issue, the new kernel seems to have a far older version. No virtualization involved.

Oct 3 2018, 5:12 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc2)

Sep 19 2018

mb300sd added a comment to T852: Router responding to arp requests for all addresses, breaks Windows networking!.

I've tried the oldest build, but it still has the issue. Is there any way to extract an image from another router? The timing does line up for it being a driver issue, I'm going to see if swapping to a different NIC helps next time I drive over, debugging remotely atm, so no rebooting allowed for a few days.

Sep 19 2018, 6:20 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc2)
mb300sd added a comment to T852: Router responding to arp requests for all addresses, breaks Windows networking!.

Does anyone know where I can find a build on the old kernel? I deleted mine swapping images at some point. Starting to think that might be when it started.

Sep 19 2018, 5:08 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc2)
mb300sd added a comment to T852: Router responding to arp requests for all addresses, breaks Windows networking!.

It's what Windows does when you first assign an IP address - checks if it's in use and refuses to use it if it is. Linux boxes don't so they have working IPv4.

Sep 19 2018, 5:06 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc2)
mb300sd added a comment to T852: Router responding to arp requests for all addresses, breaks Windows networking!.

IPv6 is all on different subnets, and I actually have working IPv6 networking while IPv4 is broken. v6 uses NDP instead of ARP so shouldn't be able to cause this.

Sep 19 2018, 4:42 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc2)

Sep 18 2018

mb300sd added a comment to T852: Router responding to arp requests for all addresses, breaks Windows networking!.

Config's pretty huge, here's the LAN interface. Need to go through and sanitize the rest. No proxy arp or similar anywhere, "arp" doesn't appear in the config at all. Issue occurs on all vlans.

Sep 18 2018, 9:16 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc2)
mb300sd created T852: Router responding to arp requests for all addresses, breaks Windows networking!.
Sep 18 2018, 7:37 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc2)

Sep 9 2018

mb300sd added a comment to T826: L2TP/IPSec broken in latest rolling release.

Do you have a copy of 1.2.0-rolling+201808230337 to share? I'd like to get wireguard working, but need L2TP working as well. It's no longer on the download page.

Sep 9 2018, 7:20 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc1)

Sep 8 2018

mb300sd created T838: "monitor firewall" reads from /var/log/messages, but firewall logs are in /var/log/vyos-rsyslog.
Sep 8 2018, 5:58 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc1)

Aug 7 2018

mb300sd created T770: Bonded interfaces get updated with incorrect hw-id in config..
Aug 7 2018, 2:48 PM · VyOS 1.2 Crux, VyOS 1.3 Equuleus

Aug 2 2018

mb300sd closed T754: Enable DNSSEC in DNS forwarder as Resolved.

Looks like it was merged, closing, thanks :)

Aug 2 2018, 7:59 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc1)
mb300sd updated the task description for T760: Allow named interfaces.
Aug 2 2018, 6:15 PM · VyOS 1.3 Equuleus
mb300sd added a comment to T754: Enable DNSSEC in DNS forwarder.

https://github.com/vyos/vyos-1x/pull/24

Aug 2 2018, 6:29 AM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc1)
mb300sd created T762: Include rulseset in firewall.
Aug 2 2018, 4:33 AM · VyOS 1.3 Equuleus

Jul 30 2018

mb300sd created T760: Allow named interfaces.
Jul 30 2018, 6:38 PM · VyOS 1.3 Equuleus

Jul 28 2018

mb300sd created T754: Enable DNSSEC in DNS forwarder.
Jul 28 2018, 5:06 AM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc1)

Jul 27 2018

mb300sd added a comment to T698: Change broke bridging.

As far as I could tell before, it was triggered by my unique attempt to bridge a vlan to openvpn.

Jul 27 2018, 7:16 AM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc3)
mb300sd added a comment to T698: Change broke bridging.

Finally had some down time I could to use to debug this, but it appears to be fixed in the latest revisions. Going back to 201806151501 still breaks it though.

Jul 27 2018, 7:14 AM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc3)

Jun 20 2018

mb300sd added a comment to T698: Change broke bridging.

Little more testing..

Jun 20 2018, 9:10 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc3)
mb300sd added a comment to T698: Change broke bridging.

relevant parts below. The interfaces seem to be added to the bridge, but the bridge interface is not assigned an ip address.

Jun 20 2018, 8:40 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc3)

Jun 18 2018

mb300sd created T698: Change broke bridging.
Jun 18 2018, 8:26 PM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc3)

May 29 2018

mb300sd created T664: DNS forwarder config broken with more than 2 zones.
May 29 2018, 4:34 AM · VyOS-1.2.0-GA, VyOS 1.2 Crux (VyOS 1.2.0-rc1)

May 19 2017

mb300sd changed Why the issue appeared? from none to other on T310: Cannot add tunnel interface to bridge.
May 19 2017, 4:00 AM
mb300sd set Version to vyos-999.201705172137-amd64 on T310: Cannot add tunnel interface to bridge.
May 19 2017, 4:00 AM
mb300sd created T310: Cannot add tunnel interface to bridge.
May 19 2017, 3:58 AM