Robin,

For an interface the be "enabled" using the web configurator, a link 
must be present... which mean, a cable should be plugged into the interface.
This way, you should be able to enable the interface.

Can you please send me the whole pf.log file rather than just copy paste 
some parts.

Thanks

On 9/20/12 10:37 , Robin Kipp wrote:
> Hi Derek and all,
> thanks a lot for pointing out the log file as well.
> I've just re-installed Debian and Pf, and it looks like I'm having some kind 
> of issue with the network interfaces. When I now look at the Network section 
> of the configurator, interfaces eth1 and eth2 are shown as disabled, whereas 
> eth0 and eth3 have an "enabled" status.
> When I click on one of the disabled interfaces, I get the following on the 
> web interface:
>
> Error! Interface eth1 has not been enabled, should check server side logs for 
> details.
> Well, I checked /usr/local/pf/logs/packetfence.log but couldn't find anything 
> helpful in there:
> | Action                                                     | Time      |
> +------------------------------------------------------------+-----------+
> | /interface/begin                                           | 0.001005s |
> | /interface/object                                          | 0.003405s |
> | /interface/up                                              | 0.005336s |
> | /end                                                       | 0.008827s |
> |  ->  pfappserver::View::JSON->process                       | 0.003760s |
> '------------------------------------------------------------+-----------'
>
>   (Catalyst::finalize)
>
> Furthermore, I checked the error_log and admin_error_log files, but those are 
> completely empty.
> So, I really don't understand what is wrong here. All the interfaces are 
> defined in /etc/network/interfaces as static interfaces, with distinctive IP 
> addresses. Here's the output that I get from ifconfig:
>
> eth0      Link encap:Ethernet  HWaddr 00:00:24:ce:80:34
>            inet addr:192.168.178.10  Bcast:192.168.178.255  Mask:255.255.255.0
>            inet6 addr: fe80::200:24ff:fece:8034/64 Scope:Link
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:1053 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:1003 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:114761 (112.0 KiB)  TX bytes:1030095 (1005.9 KiB)
>            Interrupt:19 Memory:a1000000-a1020000
>
> eth1      Link encap:Ethernet  HWaddr 00:00:24:ce:80:35
>            inet addr:192.168.10.1  Bcast:192.168.10.255  Mask:255.255.255.0
>            UP BROADCAST MULTICAST  MTU:1500  Metric:1
>            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>            Interrupt:16 Memory:a2000000-a2020000
>
> eth2      Link encap:Ethernet  HWaddr 00:00:24:ce:80:36
>            inet addr:192.168.10.2  Bcast:192.168.10.255  Mask:255.255.255.0
>            UP BROADCAST MULTICAST  MTU:1500  Metric:1
>            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> collisions:0 txqueuelen:1000
>            RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>            Interrupt:16 Memory:a3000000-a3020000
>
> eth3      Link encap:Ethernet  HWaddr 00:00:24:ce:80:37
>            inet addr:192.168.10.3  Bcast:192.168.10.255  Mask:255.255.255.0
>            inet6 addr: fe80::200:24ff:fece:8037/64 Scope:Link
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:217 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:62564 (61.0 KiB)  TX bytes:468 (468.0 B)
>            Interrupt:17 Memory:a4000000-a4020000
>
> lo        Link encap:Local Loopback
>            inet addr:127.0.0.1  Mask:255.0.0.0
>            inet6 addr: ::1/128 Scope:Host
>            UP LOOPBACK RUNNING  MTU:16436  Metric:1
>            RX packets:25 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:0
>            RX bytes:1978 (1.9 KiB)  TX bytes:1978 (1.9 KiB)
>
> I've tried restarting Pf and even rebooted the server, but I keep getting 
> this very same message over and over again, and cannot enable the other 
> interfaces...
> Thanks for any help with this issue!
> 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)


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to