General

Profile

Max Mustermann

  • Login: 28680546
  • Registered on: 07/18/2010
  • Last connection: 02/08/2014

Issues

open closed Total
Assigned issues 0 0 0
Reported issues 0 8 8

Activity

02/08/2014

05:51 AM pfSense Feature #3426: NanoBSD shorter F1 boot prompt display
In pfsense-tools / builder_scripts / builder_common.sh, line #2202
@boot0cfg -B -b ${CLONEDIR}/${NANO_BOOTLOADER} ...
Max Mustermann

02/02/2014

04:50 AM pfSense Feature #3430 (Rejected): Service Forwarding: SMTP Forwarding host for each WAN link
Most dutch consumer ISP's don't allow access to TCP port 25 other then on their own network. When having multiple WAN... Max Mustermann

02/01/2014

05:43 PM pfSense Feature #3427 (Rejected): Shorten 83 second reboot time on NanoBSD class 10 USB device on i3 (2013) PC hardware
Having current hardware (a 2013 Intel Nuc) running i3-3217U processor, and running pfSense of a class 10 microSDHC de... Max Mustermann
04:54 PM pfSense Feature #3426 (Resolved): NanoBSD shorter F1 boot prompt display
The boot process of pfSense-2.1.1-PRERELEASE-4g-amd64-nanobsd_vga-20140131-1030.img is approximately delayed by 12 se... Max Mustermann
01:55 PM pfSense Bug #3425 (Rejected): Enabling PowerD fails with repeating "kernel: acpi_perf0: Px transition to 774 failed" and "kernel: acpi_perf0: set freq failed, err 6"
Running pfSense-2.1.1-PRERELEASE-4g-amd64-nanobsd_vga-20140131-1030.img
on
Intel(R) Core(TM) i3-3217U CPU @ 1.80G...
Max Mustermann

08/01/2010

06:58 PM pfSense Bug #784 (Rejected): Documentation: Firewall: Rules: Floating rules, Interface Groups, Interfaces: in which order are these groups processed?
Reading "The Definitive Guide ...", online documentation and this bug tracker, none of them give me a clue,
in whic...
Max Mustermann
06:09 AM pfSense Bug #783 (Resolved): incorrect interface (If) label displayed on firewall_nat.php
Running: 2.0-BETA4-512mb-20100731-1322-nanobsd
Instead of displaying the user assigned label 'WAN1', firewall_nat....
Max Mustermann
05:27 AM pfSense Bug #779: Updating port forwarding associated firewall filter rule to interface group name, leads to incorrect interface labels in NAT port forwarding web interface
ok Max Mustermann

07/31/2010

07:51 PM pfSense Bug #779 (Closed): Updating port forwarding associated firewall filter rule to interface group name, leads to incorrect interface labels in NAT port forwarding web interface
Creation of NAT (port forwarding) rules with Interface groups is filed under #701 as feature request.
Though with ...
Max Mustermann
07:33 PM pfSense Feature #701: Interface groups with NAT
Current 20100731-1322 implementation is incorrect:
- having 'WAN1', 'WAN2' and 'WAN' as grouping of WAN1+WAN2
- <fi...
Max Mustermann

Also available in: Atom