[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Virtual port on a QUBE2
- Subject: Re: [cobalt-users] Virtual port on a QUBE2
- From: "Jason Aspinall" <jaspinall@xxxxxxxxxxxxxxx>
- Date: Wed May 31 00:57:13 2000
----- Original Message -----
From: "Kris Dahl" <krislists@xxxxxxxxxxxxx>
To: <cobalt-users@xxxxxxxxxxxxxxx>
Sent: Tuesday, May 30, 2000 6:07 PM
Subject: Re: [cobalt-users] Virtual port on a QUBE2
> Try using a different virtual interface.
>
> I.e. instead of calling your config file
> /etc/sysconfig/network-scripts/eth0:0
> call it
> /etc/sysconfig/network-scripts/eth0:1
Doesn't appear to :( Some cron job or whatever is access these custom files
of mine, altering the content, and therefore breaking what I've done :| If
I set the config file as to what I think should be there, start the virtual
port up with "ifup", I can ping the IP across my LAN, but no-one 'external'
can get a ping reply...
I've telnetting in from home to the box to set the port up, and then tried
pinging it.. no joy :(... So how come I can ping the Qube internally (over
my LAN) on my desired IP, yet not see it outside?
Of the bank of IP's my ISP has given me, only one is in use by the Qube2 (as
allocated through the GUI), so pinging any of the other IPs on the Cisco
1601 the Qube2 is attached to would give a no response result (as there is
nothing connected to it 'listening' on the unallocated IPs) - bar this new
one that I can ping internally once the eth0:0(1) config is initialised...
Surely someone out there is doing a little spot of virtual hosting on their
Qube2? C'mon...come outta the woodwork and make me feel like an idiot as to
why this doesn't want to work :)
Cheers
--
Jason Aspinall
Lion Laboratories Limited, Barry, UK, CF63 2BE
Tel +44(0)1446 744244 Fax +44(0)1446 720937