Upgraded 19.07 to 21.02 and router stopped working

[trendy]

@xorbug @anon50098793 any ideas?

@lockheed

Which service is missing?

@lockheed

# service firewall restart 
sh: service: not found

[anon50098793]

@lockheed

# service firewall restart 
sh: service: not found

afaik...

• above is about the 'service' function from /etc/profile not existing
• lxc is probably similar to qemu in that the init process is 'special'... but pretty sure that kind of stuff would be mentioned where you downloaded your stuff

[trendy]

Thanks! Any idea about the firewall not being configured?

[anon50098793]

@anon50098793

lxc is probably similar to qemu in that the init process is 'special'

afaik, when you run openwrt in qemu and probably lxc certain changes need to be made to the way somethings startup...

not an expert in this area but it should be explained where the dude downloaded his image... as they probably made all the necessary modifications or some or none... answer changes depending on that...

i.e.; this message;

@lockheed

Warning: Section @defaults[0] requires unavailable target extension FLOWOFFLOAD, disabling

is probably referring to the lxc host-os kernel... etc. etc.

[lockheed]

If it adds anything to the discussion, on 19.07 (also in LXD) I get the same:

# service firewall restart 
sh: service: not found

yet the router has been working properly since over a year now.

[anon50098793]

did you keep settings / restore a backup file across those versions?

[xorbug]

Ok I just checked quickly... two things:

@lockheed

# service firewall restart 
sh: service: not found

Probably you are lxc-attaching right? Because attach notoriously doesn't export all paths and variables. It's the same for me. If you go over ssh, and I guess lxc-console as well, it's everything in place tho.

@lockheed

Warning: Section @defaults[0] requires unavailable target extension FLOWOFFLOAD, disabling

Probably you restored a configuration from another router? Because SFO should not be available for x86_64. See Software flow offloading for containerized OpenWrt

As also @anon50098793 said, that's related to the host kernel.Kernels from major distros (at least Debian based) appear to work well without any specific tuning, at least i had no issues so far. And in any case it's just a warning, should be safe to ignore.

[lockheed]

did you keep settings / restore a backup file across those versions?

I tried with restore, and with manual setup from scratch. Same result both times.

Probably you are lxc-attaching right? Because attach notoriously doesn't export all paths and variables. It's the same for me. If you go over ssh, and I guess lxc-console as well, it's everything in place tho.

Great point. That's right. I use LXD, so it's lxc exec but this is just a wrapper for lxc commands.
So after logging through ssh, I got a correct response from the service:
https://pastebin.com/raw/ygH5Agfu

[trendy]

Apart from the FLOWOFFLOAD warning, it seems that no firewall rules are created from the uci configuration. OP has problem with lan users not accessing the internet and it turned out that masquerade was not created.

[xorbug]

Most probably it's exactly this...

[lockheed]

Just to close this: the problem was rendered moot by installing OpenWRT with a 22.03 LXD image which became available in the meantime in the official LXD repo.

[psherman]

If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.
Thanks!