Messages

Hello all,

i recently bought a zte mc888ultra. it has two interfaces (one is 2,5gbit) and supports amazing 5g speeds.
The zte has an option of "bridge mode", which directly assigns to a client connected to a selected port the ip address from the provider instead of the local subnet one (192.168.0.1/24).
Usually the providers give cgnat ip range addresses (10.147.10.1 ecc.) but my provider gives me an option for an APN that gets a public ip.
I have tried using this bridge option with opnsense, but it only gets a local ip range ip (192.168.0.182) when i have DHCP Server enabled in the zte and NO ip at all when i disable DHCP server in the zte.

i have tried multiple times with multiple changes,request options,mac spoofing ecc.. in the wan dhcp options of the opnsense, i also followed this thread "https://forum.opnsense.org/index.php?topic=41393.0c", but no result at all. When i do a tcpdump, i get DHCP NAK message of "wrong network".

I connected my computer directly with wireshark and it took immediately the provider external WAN IP, and from the DHCP 55 options there are some options like wpad option and option 81 that where requested.
How can i request wpad/dhcp proxy and option 81 fqdn through the opnsense dhcp advanced settings that maybe can help? Is there any other think i can do?

Thank you in advance.

Hi and thank you for the replies.

In base of priority? Let's say i have generic traffic shaping rules for a subnet in the firewall/shaper section, if i add a specific firewall rule with the experimental new feature for a client in the same subnet, which shaper will be used first?

Hello all.

First of all thank you to the opnsense team for the great work and the fluent update to 25.1 with no problems.

I would like to ask something related to traffic shaping.
I have noticed in the firewall rules, a new "experimental" section for traffic shaping (choosing direction and shaper in the rule) that reminded me of the long,long past using shaping in pfsense.

Is the Firewall/Shaper section going to change towards this approach in the future or will both co-exist in opnsense?
Are there any advantages/disadvantages?

Should we prefer the classic shaper of opnsense, start migrating to the new way for traffic shaping or use it only for limiters?

Sorry for the many questions and thank you in advance for any reply.

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

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

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  ::)

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".

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?

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.

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

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

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.

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

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

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

thank you franco.

hi,

pppoe is on top of vtnet4.

thank you. will look at the backport patch.

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 Expand

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


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