Customer is on ClearOS Pro 6.4.0.
Multi WAN is installed with two external WAN ports with static IPs. Older SDSL 1/1 on eth1 and just installed FIOS 75/35 on eth2.
It seems clear to me on the MultiWAN setup that you can make entries that tie traffic on certain ports to a specific WAN port. Under "Destination Port Rules, I entered port 80 to use eth 2 and entered port 25 to use eth1.
I'm expecting the built in mail server to use eth1 to send mail (port 25) but that does not seem to be happening as I'm getting a few mail reject messages from SPAM filters showing it went out eth2. There is only reverse DNS records on eth1 so all mail MUST send on eth1. Should I do that on "Source-based Routes" ??
I'm am trying giving the SDSL a huge weight and then assuming that the port 80 on eth2 would mean the internet browsing would go through eth2 due to the "Destination Port Rules".
Multi WAN is installed with two external WAN ports with static IPs. Older SDSL 1/1 on eth1 and just installed FIOS 75/35 on eth2.
It seems clear to me on the MultiWAN setup that you can make entries that tie traffic on certain ports to a specific WAN port. Under "Destination Port Rules, I entered port 80 to use eth 2 and entered port 25 to use eth1.
I'm expecting the built in mail server to use eth1 to send mail (port 25) but that does not seem to be happening as I'm getting a few mail reject messages from SPAM filters showing it went out eth2. There is only reverse DNS records on eth1 so all mail MUST send on eth1. Should I do that on "Source-based Routes" ??
I'm am trying giving the SDSL a huge weight and then assuming that the port 80 on eth2 would mean the internet browsing would go through eth2 due to the "Destination Port Rules".
In Multiwan
Share this post:
Responses (6)
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Have you seen this post? I also posted something similar but more detailed which I can't find for the moment.
[edit]
Although having posted this I think the MultiWAN module does something similar, not using owner but destination port.
[/edit] -
Accepted Answer
David,
Unfortunately, I was never able to get it to work properly. However, that could have been because I just didn't have the chance. Each reject was considered to be the end of the world by the customer so I simply had to disable the new FIOS WAN. I created another temporary ClearOS Community on their VMWare and connected it to the FIOS. I used that Virtual Server for the Gateway. I had used different IP addresses for mail and gateway originally even though one was the actual IP address on the ClearOS Professional Server and the other was an additional Virtual IP address for the same ethernet port. That made it easy to direct mail through one server while using the other for internet.
The customer insisted that the SDSL be disconnected to save $200 per month even though they would lose that much in 10 minutes if it didn't work. By that time I had rDNS working on the FIOS and killed the SDSL. I then reconfigured the ClearOS Pro server to work on the FIOS.
I would want to test this function before I would be comfortable using it. It didn't seem to work for me unless I did something wrong in the setup shown above. Each rejected email coming back clearly showed that some were going out the wrong WAN port. -
Accepted Answer
Hi Greg,
Did you figure this out in the end?
I think what I want to achieve is similar - however the way I wanted to do it was to change the routing table's default route, but I can't seem to do this with one of the connections being a PPP.
I too was wanting to route the mail and internet down the PPP, leaving the eth for specified VPN traffic.
David
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »