Messages

1

24.1 Legacy Series / Re: Unbound alias missing on webui but implemented on queries

« on: June 01, 2024, 10:10:28 am »

Hi,
i have writen for the same issue some time ago.

https://forum.opnsense.org/index.php?topic=40651.0

2

24.1 Legacy Series / Re: Unbound DNS: Overrides - Not appearing

« on: May 24, 2024, 10:19:58 am »

hi, ofcourse. Also i verified by dns lookups that the settings are working. The problem i can't see/manage/delete what i have activated 

3

24.1 Legacy Series / Unbound DNS: Overrides - Not appearing

« on: May 23, 2024, 02:30:30 pm »

Hello,

i have opnsense latest version installed, and noticed a bug on the unbound configuration page.

I have some Host Overrides setup that work and today i tried to add an alias through "Edit Host Override Alias".

Althout i added the alias and verified it was working, in the page i see "No results found for selected host or none selected".

4

24.1 Legacy Series / Re: fq_codel console flood

« on: April 01, 2024, 02:28:03 pm »

While obviously off the Main Topic but applicable as related as I've been following this thread closely.

I've been using FQ-PIE as Scheduler in my Pipes for my Asymmetric 940/35 Spectrum Cable Internet with great results.

No Quantum or Limit settings or concern over ECN on Inbound or Outbound Queues, and no more Flood messages in Console either.

It just works.  I'm not getting a perfect +0 Download on the Waveform Test but I am consistently getting a +3 Download and +0 Upload with an A+ Score which to me is perfectly acceptable considering what I get with Traffic Shaping off.

The amount of time I've spent trying to fine tune the settings using CoDel with inconsistent results is embarrassing to state.   PIE might not work out for you but I just wanted to share my experiences since I've been plagued with all of the problems and confusion that have been posted in this thread and many others here.

<Edited for spelling and grammar error>

Hi,

Have you enabled only the scheduler or the "Pie" option too?

What's your config?

5

24.1 Legacy Series / Re: squid -k parse Requiring client certificates. Segmentation fault (core dumped)

« on: February 09, 2024, 11:27:42 am »

I also have segmentation fault error messages with squid, after upgrade to 24.1.

When i restart or stop and start squid it get "Segmentation fault (core dumped)" messages similar to @DOM_EUWest  errors , without any change from 23.7.

6

23.7 Legacy Series / traffic shaper + multiwan

« on: November 14, 2023, 04:34:28 pm »

Hello all,

i have Opnsense 23.7.8_1 installed and trying to figure out how to setup traffic shaper.
I have followed every guide in this forum and on the official guides without result.

I have a multiwan setup with a vdsl and a 4g lte connection.
In the shaper settings i have setup pipes for  dsl up & down and 4g up & down.
in the rules section i have setup a rule without destination and source, only with direction (in or out)
one for each pipe. One for the upload pipe of each connection and one for the download pipe of each connection.

The problem is that after a lot of spending hours and testing, i noticed that even if i have policy routing for a device to use a specific gateway (for example instead of the primary dsl to use the 4g) instead of using the shaper rule for the 4g connection, it respects the rule for the vdsl connection (default wan connection/gateway for opnsense) which has a lower upload.

Even if i put the non-default gateway/interface rule higher, the shaper does not respect the rule.

From what i undestand, the shaper respects from the multiwan, as gateway, the default (active) wan?

Why don't the devices with the policy routing, use the shaper for the interface configured istead?

I also have shared forwarding enabled.

**** This happens to the devices to which i connect from remote (NAT- port forward), from internal LAN the shaper works correctly.

thank you

7

23.7 Legacy Series / Re: Static Routes not being respected..?

« on: September 14, 2023, 04:25:11 pm »

Hello,

you are both correct. I completely "missed" the fact that it's a Public IP , so i should respect the policy routing instead of the default gateway.

thank you for your answers

8

23.7 Legacy Series / Static Routes not being respected..? -SOLVED-

« on: September 14, 2023, 11:16:09 am »

Hello,

i have installed opnsense 23.7.3 with multiwan setup.

Yesterday I have tried to setup a static route, towards a specific VPS IP xx.xx.xx.xx/32 and i have noticed that the route , although i can see in the status page correctly, when i do a traceroute from a LAN client towards the ip, the gateway used is not the one chosen at the static route.

9

23.7 Legacy Series / Re: pppoe MTU not being set correctly.

« on: September 08, 2023, 03:55:30 pm »

------update-------

applied the patch and now the pppoe mtu after reboot is set to 1500 

The backport patch is from the development version or the pre 23.7 version? (Just curious)

thank you franco.

10

23.7 Legacy Series / Re: pppoe MTU not being set correctly.

« on: September 08, 2023, 02:50:28 pm »

hi,

pppoe is on top of vtnet4.

thank you. will look at the backport patch.

11

23.7 Legacy Series / Re: pppoe MTU not being set correctly.

« on: September 08, 2023, 02:04:08 pm »

Hi Franco ,

thank you for the reply.

the command "opnsense-log | grep ifconfig" returns empty. no results.
this is what i get with the ifconfig command:

Code: [Select]

root@OPNsense:~ # ifconfig | grep mtu
vtnet0: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 65520
vtnet1: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 65520
vtnet2: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 65520
vtnet3: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 65520
vtnet4: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1508
vtnet5: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
vtnet6: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
vtnet7: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 65520
vtnet8: flags=8822<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
vtnet9: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 65520
vtnet10: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 65520
vtnet11: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 65520
vtnet12: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 65520
vtnet13: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 65520
vtnet14: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 65520
vtnet15: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 65520
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
enc0: flags=0<> metric 0 mtu 1536
pflog0: flags=20100<PROMISC,PPROMISC> metric 0 mtu 33160
pfsync0: flags=0<> metric 0 mtu 1500
pppoe0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> metric 0 mtu                                                                                                              1492
ovpnc1: flags=8010<POINTOPOINT,MULTICAST> metric 0 mtu 1500
ovpnc2: flags=8010<POINTOPOINT,MULTICAST> metric 0 mtu 1500
zt55cpnf57tvnd5: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 5000                                                                                                              mtu 2800
wg1: flags=80c1<UP,RUNNING,NOARP,MULTICAST> metric 0 mtu 1420
wg0: flags=80c1<UP,RUNNING,NOARP,MULTICAST> metric 0 mtu 1420
wg3: flags=80c1<UP,RUNNING,NOARP,MULTICAST> metric 0 mtu 1420


12

23.7 Legacy Series / Re: pppoe MTU not being set correctly.

« on: September 06, 2023, 03:45:37 pm »

Hello franco,

I am NOT on developement version, normal community edition. As i mentioned, if i just press save without any change to any of the Wan interface or to the PPPoE device, the PPPoE connection gets renewed with MTU 1500. But if i reboot, it starts with 1492.

Which logs should i post?

Thank you

13

23.7 Legacy Series / Re: pppoe MTU not being set correctly.

« on: September 01, 2023, 07:25:57 pm »

Hello all,

for me the problem remains, i have opnsense in a vm in proxmox with proxmox MTU 9000 on the HW interface and i use VIRTIO for opnsense.

I have a "WANRAW" parent interface set to 1512 MTU, the WAN interface with 1508 MTU and since version 23.7 when mtu started to be 1492, although now i have updated to 23.7.3, after reboot the MTU is 1492.

If i change any setting on the wan interface and press "save", then the MTU goes to 1500.

14

23.7 Legacy Series / pppoe jumbo frames -RFC 4638

« on: August 11, 2023, 08:09:51 am »

Hello all

i have a pppoe connection that supports jumbo frames for 1500 MTU. I had inserted on my WAN interface the MTU to 1508 and in the INTERFACES overview, the MTU was correctly 1500.

I have noticed that after the latest update, although the MTU of the interface is set to 1508, the MTU in the interview section is 1492.

If i just press "SAVE" on the WAN interface, it sets again the MTU to 1500 of the pppoe, but if i reboot the firewall, it returns to 1492.

Same thing if i set the MTU to 1508 on the "point-to-point->devices->pppoe" section. At first the MTU is 1500 but after a reboot, it goes to 1492.

Thank you.

15

23.1 Legacy Series / ddclient

« on: July 04, 2023, 06:05:15 pm »

Hello all,

i have changed from ddclient backend to opnsense backend for dynamic dns update because of the many problems and many errors ddclient started to give after the latest updates.

Now dynamic dns with dyndns is working better.
The problem is that i also have namecheap that i can no longer update.

Is there a possibility to add, even a curl way update so i can update namecheap with the opnsense backend?

Thank you