19.1 completely messed up my network

[lebowski]

Since i've upgraded to 19.1, my network became completely unusuable. What i've encountered:

-my squeezebox is suddenly offline, cant see its servers
-android phones cant load webpages, google news unable to load content, apps cant load content (on separate access points, nothing has changed there)
-debian netinstall cant load content from ftp source

Websites cant load, sudden timeouts, destinations unreachable.

The situation became so dramatic that i had to poweroff the opnsense firewall and put a temp tplink router in place. "everything" came bank to life.

I'm running opnsense on an intel celeron j1900 supermicro appliance with intel gbit nics. Everything worked fine up until the update to 19.1  .

[iam]

Could be also a MTU problem:
https://forum.opnsense.org/index.php?topic=11425.0

[franco]

Please ask your DHCP server administrator why they are giving out silly MTU recommendations.

19.1.1 is out now to ignore this. It was an operating system change that was responsible for this.


Cheers,
Franco

[logo2002]

Hi,

I got the same issue and that was due to the MTU.

You can check it by running the ifconfig command on the OpnSense CLI.

A topic already exist in the forum and the update 19.1.1 seems to be released soon.

Logo

[tbandixen]

A topic already exist in the forum and the update 19.1.1 seems to be released soon.

it is released since some minutes

[lebowski]

It worked! I can now breathe again... ps. I'm on ziggo, one would think that they know better with almost 4 million customers. I guess not.

[franco]

Another ziggo user confirmed this as well: 19.1 bad, 19.1.1 good.


Cheers,
Franco

[lebowski]

Wen will the download images be updated to 19.1.1 ? It seems the download page still points to 19.1 images.

[the-mk]

you have to upgrade after 19.1 installation via web-ui or console to 19.1.1

[lebowski]

That i understand, but wouldnt it be a good idea to use 19.1.1 as the "first" version in te 19.1 range, and skip the 19.1 image alltogether, since these cause so much trouble with the automtu issue? Has given me a lot of headaches imho

It could even be so that duo to the automtu issue a user is unable to update to 19.1.1 alltogether. Took me multiple tries duo to a completely corrupted connection.

[lattera]

That i understand, but wouldnt it be a good idea to use 19.1.1 as the "first" version in te 19.1 range, and skip the 19.1 image alltogether, since these cause so much trouble with the automtu issue? Has given me a lot of headaches imho

It could even be so that duo to the automtu issue a user is unable to update to 19.1.1 alltogether. Took me multiple tries duo to a completely corrupted connection.

We'll look at generating new installation images once we address some of the other issues that popped up, including recent FreeBSD security announcements.

[franco]

The upgrade path from 18.7 is now landing in 19.1.1 directly.

Images are harder: it takes two days to assemble them and test them and we still have a few loose ends to look into which we cannot if we keep chasing tails with building images spending time with tasks that keep us from looking into loose ends...


Cheers,
Franco

[jjanzz]

It worked! I can now breathe again... ps. I'm on ziggo, one would think that they know better with almost 4 million customers. I guess not.

Which modem did they got you? One of those new ConnectBoxes?