VETH doesn't survive shutdown - breaks pihole container

I have a pihole container on my router, but the VETH it works off is causing me problems. I had it configured, as per the Mikrotik video tutorial on pihole containers, on VETH1. I shut down the router, but when it rebooted the VETH1 interface was no longer there, which caused the container to not run.

On trying to create a VETH interface manually it gave error 6 - “Couldn’t add new interface - veth setup failed”. This, of course, completely kills the container.

Now I can’t create ANY veth interface - it just fails with the same error. This was all working very well until the shutdown, and I’m pretty sure I rebooted the router and it came back up (but can’t recall the specifics).

Surely this is a bug? If not, how can I fix it?

D.

This seems to be a common problem. I updated to the latest release (7.12) today and reset the interfaces. It’s working, but I’m now afraid to reboot it :smiley:

Does anyone know if this update fixed the problem?

There have be various problem in VETH since they added IPv6 support, CIDR/multiple IP. I think the upgrade/winbox/etc didn’t always handle all cases to deal with newer CIDR addressing between versions (and/or winbox may allow saving bad config).

Agree, it has been “fragile” in past releases. Generally speaking removing and recreating VETH should fix problems if upgrade has broken something.

I would recommend v7.12 since I doubt there adding more features to VETH, so hopefully that will be stable for you. But the only way to find out is reboot.

Survived both reboots and a shutdown.