Hello,
I still can't get packetfence to work consistenly in inline mode.
My first problem seems to be with dhcpd.
The virtual machine still has three nics.
Only the interface which leads out to the internet has a gateway in its
ifcfg script.
This (192.168.1.254) is therefore normally picked up by the kernel as the
default gateway.
In my networks.conf and pf.conf, I have identified inteface
192.168.123.0 to have dhcp enabled.
The default gateway in the interface descriptions is 192.168.123.2
When my clients get ip addresses, they get two gateways: 192.168.1.254 &
192.168.123.2
Could anyone please explain to me why they are getting 192.168.1.254?
This machine is not directly reachable to the clients and they should need
to go through 192.168.123.2 for internet access which is then routed to the
192.168.1.0/24 interface...
at least i thought that was how this would work...
At the moment, all my clients are stuck because they keep trying to reach
the 192.168.1.254 gateway...
My second problem starts once I have manually removed the excess gateways.
The external clients connected using the same wifi AP cannot reach any
address until the machine hosting the virtual machine has accessed the very
same address.
I have tried turning off all iptables & firewalls to no avail. Using
tcpdump, the packets never seem to arrive at the virtual machine. but they
get to the host (I can see this in wireshark)
Once I have accessed the very same website on the host then i can see the
packets from the client reach the virtual machine...
The virtual machine is using a bridged network from the host.
I have no idea what could be wrong. any pointers would be most appreciated!
Thanks for any replies.
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Packetfence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
