Re: interfaces lo:1 lo:2 lo:3? (for remote ssh tunnels)
On Fri, Jun 25 at 01:24PM +0800, John Summerfield wrote:
> Will Trillich wrote:
> >On Fri, Jun 25 at 11:46AM +0800, John Summerfield wrote:
> >>Will Trillich wrote:
> >>>can linux have multiple 127.0.0.1 interfaces? if so, how?
>
> I'm not talking to myself, I'm talking to someone else. Therefore I
> shouldn't use a local interface.
i think one of us doesn't understand the problem solved by
port-forwarding...?
turns out the vast majority of these connections will be coming
from beyond a remote firewall (remote from where the server is
located on the 'net):
client
192.168.9.9
|
192.168.0.1
client firewall
11.22.33.44
|
| internet
|
22.44.66.88
server's firewall
10.1.1.1
|
10.1.2.3
server
the server can't open a port on the client machine, cuz it can't
get past the client firewall. the client CAN ssh past the server
virewall (that's how the latter is set up) to the server itself
and establish a remote-to-local forwarding rule. if the server
can be made to chat with a localhost interface using a port to
match the forwarding setup, it will work -- for one user per
loopback interface.
> There's no objection to using eth0:${n}, and you can also use dummy:
>
> How many do you want?
> for n in 1 2 3 4 5 6 7 8 9; do ifconfig dummy0:$n 192.168.19.${n};done
about those dummy interfaces... can they be made into loopback
devices? and if so, how?
--
I use Debian/GNU Linux version 3.0;
Linux boss 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i586 unknown
DEBIAN NEWBIE TIP #35 from Joris Lambrecht <jlambrec@landis.be>
:
Looking for some LINUX TUTORIALS? Check out this
book at sourceforge:
http://rute.sourceforge.net/node19.html
Also see http://newbieDoc.sourceForge.net/ ...
Reply to: