General

Profile

Stefan Heck

  • Registered on: 04/13/2016
  • Last connection: 06/30/2016

Issues

Activity

06/30/2016

03:54 AM pfSense Bug #6564 (Duplicate): Alias URL TABLE(IP) failed loading when WebGUI set to HTTPS
After setting System -> Advanced -> Protocol to HTTPS
the download of Alias URL TABLES(ip) does not work anymore whe...

06/06/2016

08:35 AM pfSense Bug #6099: igmpproxy does not recognize upstream interface
Just to compare with the same Version on my System:
MY router (192.168.1.254) periodily sends a Membership query (...
06:34 AM pfSense Bug #6099: igmpproxy does not recognize upstream interface
@Andrew
yes indeed
While the IP 192.168.1.35 sends a Membership request to 224.0.252.15211:56:36,591: Should ins...
03:42 AM pfSense Bug #6099: igmpproxy does not recognize upstream interface
@Andre Vink
Did you try the Version I have mentioned above? It is the same as the current Version from ViToni plus e...
02:49 AM pfSense Bug #6099: igmpproxy does not recognize upstream interface
You mix up different issues in this thread.
The robustness if igmpproxy has nothing to do with "not recognize upst...

06/01/2016

12:24 PM pfSense Bug #6099: igmpproxy does not recognize upstream interface
Phillip
You may create a Account on
https://forum.pfsense.org/index.php?board=6.0
and send me your Email Adresse ...

05/31/2016

07:21 AM pfSense Bug #6099: igmpproxy does not recognize upstream interface
Victor,
the Change you have suggested does not work for me.
I also have the Problem that the streams stop respo...
03:45 AM pfSense Bug #6099: igmpproxy does not recognize upstream interface
@Victor Toni
I did some Debugging today and finally got your Code working
in mroute-api.c function addMRoute the ...

05/24/2016

02:50 AM pfSense Feature #6228: Please provide a means for IGMPv3 and MLDv2 support
I would like to support this request for an updated and more efficient support for multicast.
As a user of the IPTV...

05/12/2016

02:40 AM pfSense Bug #6347: Stop / Restarting Service (/status_services.php)
Ok, sorry, it was indeed a Cache Problem and I haven't realized the changed behavior

Also available in: Atom