[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-developers] Qube 2 External IP Blocked
- Subject: Re: [cobalt-developers] Qube 2 External IP Blocked
- From: Malcolm McLeary <mmcleary@xxxxxxx>
- Date: Wed Jul 23 15:21:00 2003
- List-id: Discussion Forum for developers on Sun Cobalt Networks products <cobalt-developers.list.cobalt.com>
Hi Matthew,
on 24/7/03 4:57 AM, Matthew Eckmann wrote:
> The Internal IP assigned to the webserver's 2nd NIC can get out to the
> internet through the Qube 2, but the external IP assigned to the
> webserver's first NIC is being blocked by the Qube 2. Can't get out to
> the internet and external requests to the webserver can't get in (kinda
> the point to having a webserver...).
What is the purpose of your Web Server having two NICs if they are both
connected to the same LAN? It sounds link one has been assigned an internal
address and the other an external address, but both are physically connected
to the internal LAN.
If I understand what you are saying, the Qube 2 is set up to do Network
Address Translation. In this scenario I believe you can use port forwarding
to redirect traffic to the Qubes external address to an internal host, but I
don't believe you can do it for a 2nd public address.
Aren't NAT and Routing mutually exclusive capabilities?
"Multi-NAT" is possible in a "real" firewall, but I believe its beyond the
scope of a Qube 2 without serious customisation.
Cheers, Malcolm