Hi Fabrice,
Pls see attached..
Regards,
Kehinde
On Thu, Aug 24, 2017 at 1:33 AM, Durand fabrice wrote:
> no it's perfect, MYDOMAIN-b is the link to the namespace.
>
> So the issue is probably iptables, can you paste the content of
> var/conf/iptables.conf ?
>
>
>
> Le
Hi Fabrice,
See below:
[root@pfence sysctl.d]# ip route
default via 172.16.7.1 dev eth1
169.254.0.0/30 dev MYDOMAIN-b proto kernel scope link src 169.254.0.2
169.254.0.0/16 dev eth0 scope link metric 1002
169.254.0.0/16 dev eth1 scope link metric 1003
169.254.0.0/16 dev eth0.100 scope
Hi Fabrice,
See below:
[root@pfence sysctl.d]# ip netns exec MYDOMAIN ping 172.16.7.10
PING 172.16.7.10 (172.16.7.10) 56(84) bytes of data.
--- 172.16.7.10 ping statistics ---
22 packets transmitted, 0 received, 100% packet loss, time 21107ms
[root@pfence sysctl.d]# ip netns exec MYDOMAIN
Hello Fabrice,
Was thinkig, could it be a problem with the winbindd itself.
Regards,
Kehinde
On Wed, Aug 23, 2017 at 3:02 PM, Akala Kehinde
wrote:
> Hallo Fabrice,
>
> [root@pfence sysctl.d]# cat 99-ip_forward.conf
> # ip forwarding enabled by packetfence
>
Hi Louis,
Patch did the trick :)
Regards
Matt
On Wed, Aug 23, 2017 at 2:58 AM, Louis Munro wrote:
> Hi Matt,
> Can you try this patch please?
>
> https://github.com/louismunro/packetfence/commit/
> 9231fb76249289cfcfbe2db25524e2d4206fd001.diff
>
> Apply it like this:
>
> #
Ok so your issue is related to the route of the system.
do:
ip route
and:
ip route get 172.16.7.10
restart iptables
Le 2017-08-23 à 15:44, Akala Kehinde a écrit :
> Hi Fabrice,
>
> See below:
>
> [root@pfence sysctl.d]# ip netns exec MYDOMAIN ping 172.16.7.10
> PING 172.16.7.10
Let's try that:
ip netns exec MYDOMAIN ping 172.16.7.10
ip netns exec MYDOMAIN nslookup www.google.de
What is the result ?
Le 2017-08-23 à 10:55, Akala Kehinde a écrit :
> Hello Fabrice,
>
> Was thinkig, could it be a problem with the winbindd itself.
>
> Regards,
> Kehinde
>
> On Wed, Aug
Hallo Fabrice,
[root@pfence sysctl.d]# cat 99-ip_forward.conf
# ip forwarding enabled by packetfence
net.ipv4.ip_forward = 1
Checked timing already on both servers, it"s d same.
Regards,
Kehinde
On Wed, Aug 23, 2017 at 2:32 PM, Fabrice Durand via PacketFence-users <
Hello Chandra,
Create a new Root portal module and add a authentication login, then
create a new connection profile , add a filter based on per example the
ssid and assign a Root portal module that only do login.
To detect the network connectivity packetfence try to fetch a gif on
internet, so
Haproxy terminate the ssl tunnel and not apache anymore (for the portal).
So just this file is enough /usr/local/pf/conf/ssl/server.pem
Regards
Fabrice
Le 2017-08-23 à 03:24, Will Halsall via PacketFence-users a écrit :
>
> I just added the intermediate certificate to the cat process:
>
>
If Nessus support it then why not but it need to be coded in teh Nessus6
module.
Regards
Fabrice
Le 2017-08-23 à 03:01, Akala Kehinde a écrit :
> Hello Fabrice,
>
> Basically what I was trying to ask is if it's possible to attache more
> than 1 scan policy to a Nessus scan engine. Don't think
Hello Akala,
does ip_forward is enable ?
does the time of the packetfence server is the same as the AD server ?
Regards
Fabrice
Le 2017-08-23 à 02:38, Akala Kehinde a écrit :
> Hello Fabrice,
>
> Kindly see below:
>
> [root@pfence pf]# chroot /chroots/MYDOMAIN wbinfo -u
> could not obtain
Hello Fabrice,
Basically what I was trying to ask is if it's possible to attache more than
1 scan policy to a Nessus scan engine. Don't think it's possible. Except
you create another engine with another policy, and attach both scan engines
in the connection profile.
scan.conf
[ENGINE1]
Hi Guys,
I’m new to this application, so I got a question, it’s a simple one, but I
couldn’t find the right answer to my problem.
The question is same as the subject : How to disable self registration on PF7.2
And anyone can point me to the right direction to solve this one to : unable to
Hello Fabrice,
Kindly see below:
[root@pfence pf]# chroot /chroots/MYDOMAIN wbinfo -u
could not obtain winbind interface details: WBC_ERR_WINBIND_NOT_AVAILABLE
could not obtain winbind domain name!
Error looking up domain users
[root@pfence pf]# chroot /chroots/MYDOMAIN wbinfo -g
could not
I just added the intermediate certificate to the cat process:
cat /usr/local/pf/conf/ssl/server.crt /usr/local/pf/conf/ssl/server.key
/usr/local/pf/conf/ssl/intermediates.crt >/usr/local/pf/conf/ssl/server.pem
and uncommented the intermediate certificate in ssl-certificates.conf
Hell Fabrice,
And actually the FQDN of my domain name is EGELSBACH.TESTMAWOH.DE and not
TESTMAWOH.DE. None works for me.
Regards,
Kehinde
On Wed, Aug 23, 2017 at 8:38 AM, Akala Kehinde
wrote:
> Hello Fabrice,
>
> Kindly see below:
>
> [root@pfence pf]# chroot
17 matches
Mail list logo