it's one interface with two ip-addresses set up by the provider
*******
*-network
description: Ethernet interface
product: MCP51 Ethernet Controller
vendor: nVidia Corporation
physical id: 14
bus info: pci@0000:00:14.0
logical name: eth0
version: a3
serial: 00:19:99:23:07:a1
size: 100MB/s
capacity: 1GB/s
width: 32 bits
clock: 66MHz
capabilities: pm bus_master cap_list ethernet physical mii 10bt
10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=forcedeth
driverversion=0.64 duplex=full ip=xx.xxx.xxx.50 latency=0 link=yes
maxlatency=20 mingnt=1 multicast=yes port=MII speed=100MB/s
resources: irq:23 memory:f2202000-f2202fff ioport:8c38(size=8)
*********
PROD# ifconfig
eth0 Link encap:Ethernet HWaddr 00:19:99:23:07:a1
inet addr:xx.xxx.xxx.50 Bcast:xx.xxx.xxx.50 Mask:255.255.255.255
inet6 addr: xxxx::xxx:xxxx:fe23:7a1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:39140493 errors:0 dropped:0 overruns:0 frame:0
TX packets:41299455 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5145305162 (4.7 GiB) TX bytes:25999465836 (24.2 GiB)
Interrupt:23 Base address:0x8000
eth0:0 Link encap:Ethernet HWaddr 00:19:99:23:07:a1
inet addr:xx.xxx.xx.39 Bcast:xx.xxx.xx.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:23 Base address:0x8000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3113201 errors:0 dropped:0 overruns:0 frame:0
TX packets:3113201 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
El miércoles, 31 de octubre de 2012 00:05:38 UTC+1, Ben Noordhuis escribió:
>
> On Tue, Oct 30, 2012 at 7:16 PM, Karl <[email protected] <javascript:>>
> wrote:
> > Hi,
> > (Debian 6, Node 8.10, express 3, zappa 4.10)
> > I have requested a second ip number for my remote box
> > and want two run a second nodejs app on that ip. The ip
> > runs on the same card I guess (remote box)
> >
> > So I have
> > web1.net on ip1
> > web2.com on ip2
> >
> > and use iptables to redirect from 80 and 443 to
> > my ports
> > PROD# iptables -L -t nat
> > Chain PREROUTING (policy ACCEPT)
> > target prot opt source destination
> > REDIRECT tcp -- anywhere www.web1.net tcp dpt:www redir
> > ports 3003
> > REDIRECT tcp -- anywhere www.web2.com tcp dpt:www
> redir
> > ports 3004
> > REDIRECT tcp -- anywhere www.web1.net tcp dpt:https
> redir
> > ports 3443
> > REDIRECT tcp -- anywhere www.web2.com tcp dpt:https
> redir
> > ports 3445
> >
> > and ensure-https to protocol change all 80 traffic to 443:
> >
> > var ensure=require('ensure-https');
> > var options={
> > 'forceHost':undefined, // If this is set then the destination URL is
> > forced to this hostname
> > 'host':'localhost', // This is the default host to use (for
> HTTP/0.9
> > clients) (default: localhost)
> > 'sslHost':443, // This is the port of your HTTPS server if
> it is
> > not 443 (default: 443)
> > 'statusCode':301 // This is the HTTP Status-Code to use
> > (default: 301)
> > };
> > var server=ensure.createServer(options);
> > server.listen(3004,'ip1...');
> >
> > and the same for the other one, ip2 (web2.com).
> >
> > My *problem*: web1.net works fine when users enter
> > www.web1.net or https://web1.net or even https://web1.net:3443
> > but web2.com will only work if I give the https://web2.net:3445 format
> > otherwise I get "unable to connect"
> >
> > They have two separate certificates, they works with all browsers I
> tried.
> >
> > /etc/hostname has "www.bodywrappers.net"
> >
> > /etc/hosts has
> > 127.0.0.1 localhost.localdomain localhost
> > ip1... www.web1.net web1.net
> > ip1.. sxxxxxxx.online.de (this is a rented box)
> > ip2... www.web2.com web2.com
> > The A records are redirected <-> from a different provider but that
> works
> > with web1.net
> >
> > /etc/networks/interfaces
> > auto lo eth0
> > iface lo inet loopback
> >
> > iface eth0 inet dhcp
> >
> > auto eth0:0
> > iface eth0:0 inet static
> > address ip2...
> > netmask 255.255.255.0
> > network ip2....0
> > broadcast ip2....255
> >
> > Thanks, I'm a bit lost. Feel free to comment more compact solutions,
> too, of
> > course. Still a bit green here.
>
> What does `/sbin/ipconfig` print? If you have only one interface with
> one address, you can - realistically speaking - forget about
> multi-domain SSL.
>
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
