This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Multiple Wan Interfaces

Just bought a Astaro SW 220 Version 7. Not very impressed. Does not handle multiple wan interfaces very well at all, or I don't understand how it works.

Scenario
eth0 internal network
eth1 digi net
eth2 dsl pppoe connection

want eth1 default gateway and 90% of smtp traffic over line
eth2/dsl want to send http https vpn and secondary smtp

I can not get this done

http proxy only binds to default gateway, same with smtp proxy and vpn.

Can not get traffic to route over dsl with interface routing rules

Can someone assist

This thread was automatically locked due to age.

Parents

0 AMros over 16 years ago

you can find an article in the knowledgebase about how to route proxied traffic to a second (non-default) wan interface
rgds, andre
Cancel
Vote Up 0 Vote Down

Cancel
0 jjohnston62 over 16 years ago in reply to AMros

you can find an article in the knowledgebase about how to route proxied traffic to a second (non-default) wan interface
rgds, andre

This is the standard answer given on this site whenever someone asks about a second WAN connection, and it's a pretty lousy answer.

The article - "Policy Route a second WAN Connection" - infers a different internal subnet (DMZ) for routing the secondary WAN connection, and I'm guessing that's not what most people are looking for.

A lot of the policy routing articles are pretty outdated.

7.4 beta sounds pretty cool, but isn't real for production yet.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 jjohnston62 over 16 years ago in reply to AMros

you can find an article in the knowledgebase about how to route proxied traffic to a second (non-default) wan interface
rgds, andre

This is the standard answer given on this site whenever someone asks about a second WAN connection, and it's a pretty lousy answer.

The article - "Policy Route a second WAN Connection" - infers a different internal subnet (DMZ) for routing the secondary WAN connection, and I'm guessing that's not what most people are looking for.

A lot of the policy routing articles are pretty outdated.

7.4 beta sounds pretty cool, but isn't real for production yet.
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 BrucekConvergent over 16 years ago in reply to jjohnston62

7.400 is supposed to be released for production very soon... I think they have one more beta to put out. I'd wait for that as opposed to using policy routing, which, admittedly, is a messier way to deal with this.
Cancel
Vote Up 0 Vote Down

Cancel
0 BAlfson over 16 years ago in reply to BrucekConvergent

[I haven't looked at the beta.] Won't he still need to do policy routing if he wants to run SMTP traffic on eth1 and web access on eth2?

Cheers - Bob
Cancel
Vote Up 0 Vote Down

Cancel
0 AMros over 16 years ago in reply to BAlfson

no, will be done by "Multipath Rules" then - can decide if u communicate by source and/od dest, service, interface etc...
looks good for me - all the things we "worked around" with PR before now can be done by uplink balancing & mp-rules - with added failover functionality
a.
Cancel
Vote Up 0 Vote Down

Cancel