No nothing else on that network. It's a lab environment to test so there
are only 3 devices Client, Server and Cisco switch.
Can't telnet to port 80 or 443. Weird thing is with packet fence service
stopped I can ping 192.168.2.10 -> 192.168.2.1. If I leave the ping running
and the start the packetfence service you can actually see the server stop
responding when packetfence is halfway through starting services. So it
must be the packetfence configuration.
On Thu, Mar 22, 2012 at 3:08 PM, Francois Gaudreault <[email protected]
> wrote:
> Hi Andrew,
>
> This sounds really weird to me.
>
> Is it possible you have something else using 192.168.2.1 on that VLAN?
> If on the PF server, you telnet 192.168.2.1 80, do you get something?
>
> I mean starting PF with the iptables should allow ping. We do not block
> it.
>
> --
> Francois Gaudreault, ing. jr
> [email protected] :: +1.514.447.4918 (x130) :: www.inverse.ca
> Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
> (www.packetfence.org)
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> Packetfence-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Packetfence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
