Traffic shaping wizard not working
-
Or maybe someone else has an idea what to do? I'd be curious to know how reset any traffic shaping related configuration manually too.
-
Any interface with a non-empty "IPv4 upstream gateway" is considered a WAN interface. The Wizard refuses to work if there're no LAN interfaces.
Therefore, in order to configure/reconfigure the Traffic Shaper via the Wizard, there must be at least one LAN-type interface, i.e. one without "IPv4 upstream gateway".
-
Any interface with a non-empty "IPv4 upstream gateway" is considered a WAN interface. The Wizard refuses to work if there're no LAN interfaces.
Therefore, in order to configure/reconfigure the Traffic Shaper via the Wizard, there must be at least one LAN-type interface, i.e. one without "IPv4 upstream gateway".
The only interface that has an upstream gateway configured is my WAN interface. I have left it to use DHCP and it acquires all information that is needed. All other interfaces are LAN interfaces and they do not have any upstream gateways configured.
-
Sorry. I've tried to reproduce the error but I can't. The Wizard works repeatedly on every possible VLAN configuration I tested. It works repeatedly even in case of untagged VLAN. (See attached figures.)
Tested on ESXi v.5.5.
-
Thank you for your posts.
I don't know how / why this might make any difference, but both of you seem to be using VLANs.
Does my LAN interface need to be a VLAN in order to use the traffic shaper?
My LAN technically is on a VLAN too, but it's an untagged port. -
Does my LAN interface need to be a VLAN in order to use the traffic shaper?
I don't think so. Attached figure pfsense_lab_config1 (see my previous post) shows that the LAN interface can be untagged VLAN.
-
Ok, sorry I didn't look closely enough.
I recently restored my config onto a VM because of a hardware failure of my main system ::) and was able to configure the traffic shaper using the wizard flawlessly… Now of course this time the interface names changed from ixl and igb to all vmx.
I'll report back as soon as my main box comes back repaired and when I've had time to configure it from scratch. -
I would rather not have to reinstall pfsense and restore my config. I would really like to figure out what went on. Can anyone point me in the direction of command line documentation so I can take a look into this? Or any other ideas. I am really just trying to keep this thread alive.
-
So my board came back and my bare metal pfsense is up and running again, installed from scratch. I remain unable to set up a new traffic shaper configuration with 2 WAN and 1 LAN interfaces.
-
I think I might have found the reason for this (at least on my end). System logs show the following message:
rc.bootup: The gateway: WANGW is invalid or unknown, not using it.Neither of my gateways are named WANGW. Now do I really have to change one gateway's name back to WANGW?
??
-
@phming Just to liven this one up again ive got this problem. My hardware is a Nuc with the onboard lan doing the WAN connection and the LAN being taken care of by a USB dongle. I got the same message when it was setup the opposite way round...