sorry for my english
Why always given the same ip address of the client
how to clear information about the client to issue a new ip address
Client deleted on the server and on the client laptop
server restart does not help
because of this sometimes there is a conflict of addresses issued
use secure nat
Why always given the same ip address of the client
-
- Posts: 2
- Joined: Mon Jan 16, 2017 9:05 am
-
- Posts: 336
- Joined: Sat Aug 15, 2015 7:41 pm
Re: Why always given the same ip address of the client
I think SE in SecureNAT mode give out the IP in ascending order, so if your DHCP is 192.168.30.1, then it will give out 192.168.30.2 then 3 then 4, etc..
If you have a problem with this behavior, an easy solution would be to change the subnet for now, maybe to 192.168.40.1 then SE will start handing out IPs from the new subnet.
If you want more grained control over the DHCP server, then use a bridge instead of SecureNAT and use your own DHCP server
If you have a problem with this behavior, an easy solution would be to change the subnet for now, maybe to 192.168.40.1 then SE will start handing out IPs from the new subnet.
If you want more grained control over the DHCP server, then use a bridge instead of SecureNAT and use your own DHCP server
-
- Posts: 2
- Joined: Mon Jan 16, 2017 9:05 am
Re: Why always given the same ip address of the client
and how to set up, or rather a related party dhcp server?
-
- Posts: 336
- Joined: Sat Aug 15, 2015 7:41 pm
Re: Why always given the same ip address of the client
I just thought that you don't even need a bridge to configure your own DHCP.
You can disable the virtual DHCP server in SecureNAT, and then use own DHCP server for the SE traffic, i.e. for subnet 192.168.30.0/24
Here are some good DHCP configuration examples
https://access.redhat.com/documentation ... erver.html
But more importantly, I don't understand how can a an IP clash happen when using the virtual DHCP of SE. Can this behaviour be reproduced? Can you show an example and maybe the logfile when connecting from two client s and the same IP is handed out?
You can disable the virtual DHCP server in SecureNAT, and then use own DHCP server for the SE traffic, i.e. for subnet 192.168.30.0/24
Here are some good DHCP configuration examples
https://access.redhat.com/documentation ... erver.html
But more importantly, I don't understand how can a an IP clash happen when using the virtual DHCP of SE. Can this behaviour be reproduced? Can you show an example and maybe the logfile when connecting from two client s and the same IP is handed out?