Robin, ... On 9/20/12 06:53 , Robin Kipp wrote: > Hi Carl, > >> Have you tried to open the web interface locally or via ssh >> forwarding? Besides checking pf logs for issues you could use netstat >> to see some details about where 1443 is listening. > Yes, I've been able to access https://127.0.0.1:1443 using the Lynx browser > on the machine running Pf. However, it seems like I cannot login - I can > enter the username and password, but when I attempt to login I just end up on > the login page once again, with no error on the website explaining what went > wrong. Also, ever since I setup Pf I am unable to connect to SSH for whatever > reason, I can still ping the eth0 interface but connecting to it fails. > I think the main issue is that it seems like Pf does not apply configuration > changes properly. I checked some of the files in /usr/local/pf/conf and all > seems to be configured properly, but it looks like Pf makes no modifications > to dhcpd or the network interfaces. In fact, when I do > /etc/init.d/packetfence restart > most services start up, but I get a warning stating that no listener > interfaces for DHCPD are defined. Also, ifconfig -a shows that none of the > interfaces are configured, except eth0 which was setup automatically during > the Debian installation... > >> I am assuming you used the new webconfig? You could always just start fresh. > Is webconfig the interface that comes up when you access > https://ip:3000/configurator? > If so then yes, that's what I used. What do I need to do so I can start out > fresh? I doubt that aptitude purge packetfence and then reinstalling it will > undo all of Packetfence's changes to the system, though I will try. You don't really need to "start fresh". The only configuration parameters in your case would be the different config files from within /usr/local/pf/conf and the network interfaces configurations. >> Personally I prefer to check out all the configuration files manually >> the admin guide is pretty great explanation. I have not spent time >> with the recent update but I am assuming networks.conf could help you >> resolve issues with misconfigured network. > Yep, like I said I already looked at those, and really all looks just fine in > those files. The only problem here really seems to be that Pf doesn't seem to > apply these settings to the system properly, for whatever reason... If you don't mind, I'd like a copy of your /usr/local/pf/logs/packetfence.log file to see what happened in the web configurator that can affect the network interfaces configuration. >> Thanks a lot for your help and advice! > Robin > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://ad.doubleclick.net/clk;258768047;13503038;j? > http://info.appdynamics.com/FreeJavaPerformanceDownload.html > _______________________________________________ > PacketFence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users
-- Derek Wuelfrath [email protected] :: +1.514.447.4918 (x110) :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
