| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Allow explicit mask specification in bandwidth limiter. This backwards
compatible and implements ermal suggestions.
|
|
|
|
| |
functionality
|
|
|
|
|
|
| |
Working on a better fix
This reverts commit 0d59cc942f2ee225eccdb375e25f58a6f04fa9c4.
|
| |
|
|
|
|
|
|
| |
Will be done again for 2.2
This reverts commit 705950edbc09270fccbec0c5d8dd99b004704c6e.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This function does 2 unecessary things:
. Remove the IP address from interface set as Track, what is wrong and
should be done by dhcp6c
. Set a fixed IP when track6-interface is SLAAC, what never happens
since it's impossible to track a SLAAC interface
|
| |
|
| |
|
|
|
|
| |
value change from administrator.
|
|\
| |
| | |
Optimize which OpenVPN instances are restarted
|
| |
| |
| | |
When interfaces go down and up we need to know which interface (vr1, vr2 etc) each OpenVPN instance is using so we can optimize our decision about which instances to resync. That data is not in the conf file (the conf file contains the IP address the instance binds to). This change puts the interface name into a little file in /var/etc/openvpn for later use.
|
| | |
|
|/
|
|
|
|
| |
It's not the correct fix
This reverts commit e8307ae03e2769bd0ebaa4b9441ac797b50a3800.
|
| |
|
|\
| |
| | |
Restore default route after HOTPLUG linkup
|
| |
| |
| | |
When a link comes up, call interface_configure with p2=true. This makes it run various extra routines such as system_routing_configure - which will put back the default route or other static routes that might have been removed when the link was down.
|
| |
| |
| | |
There were some includes needed when calling into here from rc.linkup - somehow everything else that calls interface_configure(p1, "true", p3) has already included these.
|
| |
| |
| |
| | |
twice and don't checking openvpn client
|
|/
|
|
|
| |
. Do not remove link-local when it's already correct
. Let dhcp6c deal with tracked interface IP
|
|
|
|
|
| |
Various fixups to make this work. Now I can:
- Unplug an interface, any OpenVPN servers/clients in a gateway group using that interface are restarted and come up on the highest tier available interface. OpenVPN servers/clients that are only on that interface go down, of course.
- Plug in the cable again, any OpenVPN servers/clients in a gateway group using that interface are restarted and come up on the now-highest tier available interface (i.e. they fail back if the interface that just came up is higher tier). OpenVPN servers/clients that are only on that interface now come up.
|
|
|
|
| |
Make apinger pass the gateway parameter both when an alarm alarms (gateway is down) and when it comes good (gateway is up). This way the downstream openvpn and dyndns code can know what happened and do sensible stuff.
Return the friendly interface name ("wan", "opt1" etc) rather than the actual device name ("vr0", "vr1" etc). The openvpn and dynamic dns code that uses this needs to work with various entries in the config that all use the friendly interface name.
|
|
|
|
| |
own discipline without any childs
|
|
|
|
|
|
|
| |
. Always initialize it to 0 when it's undefined
. Remove unecessary initializations and checks
. Bump config version to 9.5
. Write an upgrade config function to initialize old configs properly
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
. Do not execute following actions when dnsmasq is disabled:
. Add host overrides to /etc/hosts
. Register DHCP leases in DNS Forwarder
. Register DHCP static mappings in DNS forwarder
It should fix issue reported at following forum post:
http://forum.pfsense.org/index.php?topic=58871
|
|\
| |
| | |
Merge commit to correct debugging issue
|
| |
| |
| |
| |
| |
| |
| | |
Accidentally changed this from executing the zfs command to echoing the
expected command in previous commits.
This had been set while debugging a better command to set ZFSROOT
variable.
|
|\ \
| |/
| | |
ZFSROOT not hardcoded to zpool or dataset 'tank'
|
| |
| |
| |
| | |
using just zfs, grep, and cut, with a simple regexp
|
| |
| |
| |
| |
| |
| |
| | |
For ZFS root readonly case, the WHEREISROOT variable was grep-ing for 'tank', expecting a zpool with that name.
A workaround of naming a dataset 'tank', for example, 'sys/ROOT/tank' or 'sys/tank/pfSense' is compatible, however this shouldn't be hardcoded in.
My proposed change replaces WHEREISROOT with ZFSROOT using awk. I noticed awk is used elsewhere in this script. However it is still simple code that is not resilient against unexpected circumstances, let alone failure.
|
| | |
|
| |
| |
| |
| | |
check / filesystem and /cf on nano platform since the others will be checked on php code
|
| |
| |
| |
| | |
certain IPs and bind to specific interfaces.
|
| | |
|
| |
| |
| |
| | |
testing.
|
| | |
|
| |
| |
| |
| | |
http://forum.pfsense.org/index.php/topic,61636.0.html
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
uselessly
|
|
|
|
| |
Helps: http://forum.pfsense.org/index.php/topic,61301.0.html
|
|
|
|
| |
enabled. This can be used to detect if there are dynamic hostnames on ipsec policies
|
|
|
|
| |
it on the line to be generated
|
|
|
|
| |
numbers. Fixes #2956
|
| |
|