SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0000134: If you open 10443 allowed in on red and you are using a static ip and router on red, then you cant get to efw web page. - MantisBT
MantisBT - Endian Firewall
View Issue Details
0000134Endian FirewallNetwork related (VPN, uplinks)public2007-03-13 07:322007-12-31 19:15
marktrent 
ra-endian 
normalmajoralways
closedfixed 
2.1 
2.2-beta2 
0000134: If you open 10443 allowed in on red and you are using a static ip and router on red, then you cant get to efw web page.
Ok, I have reproduced and verified this error on many installs. If you open port 10443 inbound to allow management of EFW via red/internet and you have assigned an ip to red interface( eg 192.168.0.1 )on the same subnet as your eg: ADSL router(192.168.0.100). You then setup a forwarding rule on your ADSL router eg forward all port 10443 to 192.168.0.1 then the following happens, you get as far as endian asking for username and password, once you try and authenticate and click ok, nothing happens and eventually times out. If you are using firefox under linux you can see that the problem is that after authentication its trying to pass the 192.168.0.1 address out to the browser. This problem does not occur when you have the adsl router in bridged modem mode and are making a direct PPPOE connection from EFW on red.
No tags attached.
related to 0000324closed peter-endian Redirect with network wizard fails on IE 
png efwerror2.png (43,738) 2007-03-13 07:32
https://bugs.endian.com/file_download.php?file_id=26&type=bug
png

png efwerror1.png (58,878) 2007-03-13 07:33
https://bugs.endian.com/file_download.php?file_id=27&type=bug
png

png efwerror3.png (61,032) 2007-03-13 07:41
https://bugs.endian.com/file_download.php?file_id=28&type=bug
png
Issue History
2007-03-13 07:32marktrentNew Issue
2007-03-13 07:32marktrentFile Added: efwerror2.png
2007-03-13 07:33marktrentFile Added: efwerror1.png
2007-03-13 07:41marktrentFile Added: efwerror3.png
2007-03-13 10:01peter-endianNote Added: 0000228
2007-03-13 10:01peter-endianStatusnew => confirmed
2007-03-13 14:12marktrentNote Added: 0000229
2007-05-22 21:51pedroNote Added: 0000326
2007-10-27 21:27peter-endianStatusconfirmed => assigned
2007-10-27 21:27peter-endianAssigned To => ra-endian
2007-12-10 17:05peter-endianRelationship addedrelated to 0000324
2007-12-10 17:06peter-endianStatusassigned => resolved
2007-12-10 17:06peter-endianFixed in Version => 2.2
2007-12-10 17:06peter-endianResolutionopen => fixed
2007-12-10 17:06peter-endianNote Added: 0000692
2007-12-31 19:15raphael-endianFixed in Version2.2-beta1 => 2.2-beta2
2007-12-31 19:15raphael-endianStatusresolved => closed

Notes
(0000228)
peter-endian   
2007-03-13 10:01   
the redirect on the efw is wrong if the firewall is behind a portfw. however, efw can't know the exact external ip, so this is not going to be fixed. we need to think about a solution.

workaround:
if this happens, you can manually change the url in your browser after the redirect in order to point it to the real extern ip address rather than to the wrongly redirected internal red ip.
(0000229)
marktrent   
2007-03-13 14:12   
OK, here is a quick workaround, when putting in the url into the browser, manually specify " /cgi-bin/main.cgi " after the port number and it works immediately. e.g. instead of putting in "https://dynclient.dyndns.org:10443" [^] type in "https://dynclient.dyndns.org:10443/cgi-bin/main.cgi" [^] this works without problem.
(0000326)
pedro   
2007-05-22 21:51   
Hi, i have de same problem in my EFW 2.1. I have tried the "solution" by putting in the url manually, and work it!Thanks marktrent!
(0000692)
peter-endian   
2007-12-10 17:06   
Redirect will now be calculated by the url which will be typed in within the browser.
So this issue should be fixed..

Next beta (2.2beta2) will contain the fix.