[SOLVED] VLAN interfaces

Started by nivek1612, July 10, 2019, 02:35:09 PM

Previous topic - Next topic
July 10, 2019, 02:35:09 PM Last Edit: July 11, 2019, 10:03:21 AM by franco
After upgrade to 19.7.rc1 all my VLANs with the exception of the default LAN where inoperable, no access to them and devices on then not able to reach the internet. No obvious error messages i could see.

Quick save of the effected VLAN interfaces from the console resolved the issue. Any logs I can provide that might help ?
OPNsense 24.7.* on Qotom i5-5250U with AAISP FTTP 900/120
OPNsense 24.7.* on Qotom i7-4500U with Orange FR FTTP 1000/400

Team Rebellion Member
One of Marjohns TESTERS :-)

Sounds like https://twitter.com/quybaohoang/status/1148897734859956224

Can you mail me an ifconfig from right after boot and after apply?


Thanks,
Franco

I have to admit I didn't save the config right after boot I have the current one obviously which is after the apply

I do have config from a few weeks ago which will not have changed if that helps
OPNsense 24.7.* on Qotom i5-5250U with AAISP FTTP 900/120
OPNsense 24.7.* on Qotom i7-4500U with Orange FR FTTP 1000/400

Team Rebellion Member
One of Marjohns TESTERS :-)

According to the other reporter a reboot is enough to bring back the issue.

ok rebooting now
OPNsense 24.7.* on Qotom i5-5250U with AAISP FTTP 900/120
OPNsense 24.7.* on Qotom i7-4500U with Orange FR FTTP 1000/400

Team Rebellion Member
One of Marjohns TESTERS :-)

Yep that did it sending the two config files now to you email add
OPNsense 24.7.* on Qotom i5-5250U with AAISP FTTP 900/120
OPNsense 24.7.* on Qotom i7-4500U with Orange FR FTTP 1000/400

Team Rebellion Member
One of Marjohns TESTERS :-)

So we would call this "a series of unfortunate events" for WAN dailup interfaces in particular which made this hard to catch. ;)

https://github.com/opnsense/core/commit/6ae356678

# opnsense-patch 6ae356678


Cheers,
Franco

July 11, 2019, 09:54:59 AM #7 Last Edit: July 11, 2019, 09:56:39 AM by nivek1612
That fixed the VLAN issue thanks Franco

Interestingly flowd_aggregate   Insight Aggregator will no longer start at boot. Is this connected ?

trying to start from the GUI I see the following in log but still doesn't start

Jul 11 08:54:34   /flowd_aggregate.py: startup, check database.

I reset the netflow data and all is good again



OPNsense 24.7.* on Qotom i5-5250U with AAISP FTTP 900/120
OPNsense 24.7.* on Qotom i7-4500U with Orange FR FTTP 1000/400

Team Rebellion Member
One of Marjohns TESTERS :-)

Thanks for confirming  8)

There may be an incompatibility in database layout while the flowd aggregator went from upstream code in compiled code for Python 2.7 (which not only needed replacement for Python 2 EoL but also gave us other behind-the-scenes trouble) to our own new Python-based code for Python 3. I would say the best way is to reset the database indeed.

A similar issue exists with Squid 3 -> Squid 4 transition with its SSL cache database.


Cheers,
Franco