I'm installing a new bordermanager 3.7 server on new hardware. at this

moment the configuration to the new isp is ok. time/http/dns/proxy all

work ok

to move from one isp to the other I have the following in mind, and
are working on it now to make this happen

i want to add one nic with public interface to the old ISP for mail.

I will use static nat on this interface to a secondary ipaddress on
the private interface(let's say 10.x.1.2/ mask

to get static nat working with filtering to/from the old isp can I use

the primary ipaddress at the public interface or should i use a
secondary ip address for this. I need static nat to our internal
mailserver till it's DNS name changed to the new's isp's ipaddress

Okay used secondary ipaddress for static nat to mailserver on private
on interface C:

new isp, nic B------------\
> nic A, primary/secondary ipaddress

private side.
old isp, nic C------------/

on C there is the secondary ipaddress

on B there is also a secondary ipaddress for future use with mail
transferred DNS to the new ISP

Secondary ip address static NAT to mail server on lan

LAN routing inetcfg:
Default route to network on nic B
network static route to lan router.

do I need a route to network from isp of nic C?

I installed the server in the LAN as explained in the post before
http (on lan b) is working.
smtp on lan C is not working, seems a routings issue as filters
result in same problem.

How can I get all mail using nic C and all other internet traffic nic

filters on C are smtp in out for private-interface C and v.v.
can smtp telnet (HELO etc mail) from public ip subnet to mailserver on
inside but not from the internet behind the isp's router (the

so why isn't it working?

i use 212.136.47.x
because of CIDR/supernet is doesn't work?