whats the best way to radd roots for 0.0.0.0/0
becouse my emails from tower1 tower2 tower 3 tower 4
route to my server
but by my server under connetions i get the same src.address
so i cant realy see where my emails are comming from
so i keep getting an error on my mail server pop3 connetion fail with my address form my tower whitch is number to so i think i need to do a more detail routing on my towers or somthing so i can brack up the towers or clients to see wher my problem is comming from!
Something doesn’t sound right. If routed right from client through to server the source ip would be client’s ip. No matter through which tower you route.
thats what i thought the clients ip should be the same as in the usermanagers system but it isnot can you maybe give me examples of some routings?
Not sure if I understand good, but here goes routing. When routing the chance of client ip and usermanager server being in same subnet are very slim. There are quite a few examples on Google on routing. But the short of it. Let’s say we have a hypothetical system. Server with userman installed Ether 1 ip 192.168.100.1/24 this connects through a lan cable to the access point ether 1 with ip 192.168.100.2/24 then you have wlan 1 with ip 192.168.110.1/24. This is where your clients connect wirelessly with CPE wlan 1 ip 192.168.110.2/24 and ether 1 on cpe with ip 192.168. 120.1/24 and the client’s computer ip 192.168.120.2/24. As you can see ip range of server, wireless side and client side are different. In order for the client to be able to send data to the router from the client, the client have to be told the route to go to get to the server, hens than name routing. This is done with routing tables. The short of it is you tell a router which path to use to get to a certain ip range The server also have to be told the way back to the client. These days OSPF and some other fancy routing protocols do this automatically.
I can do the routing tables for the three routers but answer is getting a bit long. Have a bash at it and if you still struggle, I will have a look see.
You could bridge wlan and ether 1 in CPE and wlan and ether 1 on access point. Would be like a cable running from clients computer to your server and ip’s could be on the same subnet. This is fine for example, but the fundamental flaw is that any data received on one interface of a bridged interface is retransmitted on all other interfaces an as your system grows, more data is retransmitted, putting severe strain on the network. With routing, this does not happen because data go exactly where it should be, if set up correctly. 
Maybe this will help.