Re: [IPCop-user] change IP address and gateway

[Wes F. <wf...@an...>]

Somehow the guy that set this up didn't need to use the aliases.  I don't
have any set up right now.  But if I go to Status - Network Status in the
Web GUI, I have eth0 (internal), eth1, eth1:0, and eth1:1 (all eth1 are
external).  The IPCOP distribution includes the ifconfig command, but does
that make permanent changes?  Also, does changing the gateway in the setup
automatically make changes to the routing table?
Thanks,
Wes

-----Original Message-----
From: Lawrence Bean [mailto:lb...@u4...] 
Sent: Thursday, July 19, 2007 1:30 PM
To: wf...@an...
Cc: ipc...@li...
Subject: Re: [IPCop-user] change IP address and gateway

wf...@an... writes:
>in the setup there is only a place to set up one IP address for
>'RED'.

set your "main" public IP as the red interface, and set the other public
IPs in the WebGUI in Network->Aliases. Your new ISP will neeed to be able
to point all new public IPs to the same RED hardware address. You will
probably also have to look at your Firewall->PortForwarding to ensure the
proper new public IPs are being routed to the proper private IPs.
>
>am I correct in stating that I can just change the gateway
>to the new gateway and our website and email
>would work correctly?

Yes, unless for some reason you've needed the outgoing private IP
addresses mapped to alias public IPs. This is sometimes needed for email
servers so source-reverse-lookup works correctly at the downstream post
office.

>Incoming traffic
>would come over the old IP addresses until the DNS changes propagated, but
>outgoing traffic would go over the new IP addresses?

Well, no, I don;t think so. As soon as you make the change, anything
routed to the old address(es) will be bounced back (I expect). But you can
ask your DNS provider set the DNS Time-to-live to a short downtime (e.g.
one hour), allow that to propagate, then make the swap. After the swap,
you can reset the DNS TTL to a default value.