Yesterday the IP address was 129.111.202.205 and the mac ended in de:12
If you need more, let me know. I am going to try and duplicate with this test laptop. Dwane ________________________________ From: Dziuk, Fred J [mailto:[EMAIL PROTECTED] Sent: Friday, August 31, 2007 8:46 AM To: support@pfsense.com Subject: RE: [pfSense Support] Issues with pfSense and Captive Portal Dwane, Give me the specifics like IP address, MAC address, for Number 1. The second issue may not be clearly described. I think we complete the login process (all the way to the "LOGOUT" pop-up), then click on the HOME page and it re-displays the AUP page, etc. This seems to be a problem with browser caching the redirected page, not the originally requested page. I thought from what Ed said, that getting a new page everything did NOT work. If you find a PC that has this condition, let me look at it. Fred ________________________________ From: Atkins, Dwane P [mailto:[EMAIL PROTECTED] Sent: Friday, August 31, 2007 8:36 AM To: support@pfsense.com Subject: [pfSense Support] Issues with pfSense and Captive Portal Good day. Thank you for the help you have given us in our initial usage of pfSense. We are however experiencing some issues with pfSense 1.0.1 in general and also have a CaptivePortal pre-authentication issue. First issue: I have a particular machine that is capable of going anywhere on the interenet and has yet to authenticate via the CaptivePortal. If this machine can do this, I am sure there are others. The device will show up in the DHCP lease but there is no way to give cancel their connection in 1.0.1. And the device does not show up in the CaptivePortal page at all. Second and biggest issue: We have particular users who run Safari, Firefox, and IE 7 that our initial captive portal page will allow them to authenticate our Acceptable Use Page (AUP) and then once they click Accept, it brings up the AUP again. If they log in again, it repeats the action. We have discovered that in IE, you can check the "Check for new Page on each attempt" and that will correct it. We have Empty/Deleted Cache and this does not work. Has anyone seen this before and if corrected, what was the fix action? Thank you Dwane