I've been working on a project with some Linksys routers. New routers
are set to use the IP address 192.168.1.1 and my network uses the
172.16.*.* address space. I've had this in my
workstation's /etc/network/interfaces file:

auto eth0
iface eth0 inet static
address 172.16.7.11
netmask 255.255.255.0
gateway 172.16.7.1

To access the Linksys routers when I first get them, I added this:

auto eth0:0
iface eth0:0 inet static
address 192.168.1.128
netmask 255.255.255.0
gateway 172.16.7.1

Then I restarted my network and I have eth0:0 with the address
192.168.1.128. Using route gives this (edited for space):

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
172.16.7.0 * 255.255.255.0 U 0 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 1000 0 0 eth0
default fw.loc.lan 0.0.0.0 UG 0 0 0 eth0
default fw.loc.lan 0.0.0.0 UG 0 0 0 eth0

(fw.loc.lan is the firewall between my LAN and the Internet.)

I don't see any reference to eht0:0 at all. I don't know if that
matters.

After restarting my network, I can't reach anything on the Internet.

Does it matter that route doesn't seem to see a difference between eth0
and eth0:0?

What do I need to do to be able to do this and not lose access to
domains on the other side of my gateway? Why does it change routing so
my computer doesn't work through the regular gateway I've set?

Thanks!

Hal


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Monday 06 August 2007 12:12, Hal Vaughan wrote:
> I've been working on a project with some Linksys routers. New routers
> are set to use the IP address 192.168.1.1 and my network uses the
> 172.16.*.* address space. I've had this in my
> workstation's /etc/network/interfaces file:
>
> auto eth0
> iface eth0 inet static
> address 172.16.7.11
> netmask 255.255.255.0
> gateway 172.16.7.1
>
> To access the Linksys routers when I first get them, I added this:
>
> auto eth0:0
> iface eth0:0 inet static
> address 192.168.1.128
> netmask 255.255.255.0
> gateway 172.16.7.1
>
> Then I restarted my network and I have eth0:0 with the address
> 192.168.1.128. Using route gives this (edited for space):
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 172.16.7.0 * 255.255.255.0 U 0 0 0 eth0
> 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
> link-local * 255.255.0.0 U 1000 0 0 eth0
> default fw.loc.lan 0.0.0.0 UG 0 0 0 eth0
> default fw.loc.lan 0.0.0.0 UG 0 0 0 eth0
>
> (fw.loc.lan is the firewall between my LAN and the Internet.)
>
> I don't see any reference to eht0:0 at all. I don't know if that
> matters.
>
> After restarting my network, I can't reach anything on the Internet.
>
> Does it matter that route doesn't seem to see a difference between eth0
> and eth0:0?
>
> What do I need to do to be able to do this and not lose access to
> domains on the other side of my gateway? Why does it change routing so
> my computer doesn't work through the regular gateway I've set?
>
> Thanks!
>
> Hal

You don't need to specify the gateway for eth0:0.

I also needed to configure devices that had distinct ip address values by
default. I had a similar setup until recently when I switched to using ip
syntax instead of the 'old way.' Here's a sample of my interfaces file:

address 123.456.789.2
netmask 255.255.255.252
gateway 123.456.789.1
up ip addr add 10.1.250.15/24 brd 10.1.250.255 dev eth0 label eth0:0
up ip addr add 10.10.10.15/24 brd 10.10.10.255 dev eth0 label eth0:1

aptitude install iproute
man ip
See if something like that will work for you.

Regards,

Anson


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Monday 06 August 2007, Anson Gardner wrote:
> On Monday 06 August 2007 12:12, Hal Vaughan wrote:
> > I've been working on a project with some Linksys routers. New
> > routers are set to use the IP address 192.168.1.1 and my network
> > uses the 172.16.*.* address space. I've had this in my
> > workstation's /etc/network/interfaces file:
> >
> > auto eth0
> > iface eth0 inet static
> > address 172.16.7.11
> > netmask 255.255.255.0
> > gateway 172.16.7.1
> >
> > To access the Linksys routers when I first get them, I added this:
> >
> > auto eth0:0
> > iface eth0:0 inet static
> > address 192.168.1.128
> > netmask 255.255.255.0
> > gateway 172.16.7.1
> >
> > Then I restarted my network and I have eth0:0 with the address
> > 192.168.1.128. Using route gives this (edited for space):
> >
> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric Ref
> > Use Iface
> > 172.16.7.0 * 255.255.255.0 U 0 0 0
> > eth0 192.168.1.0 * 255.255.255.0 U 0 0
> > 0 eth0 link-local * 255.255.0.0 U 1000 0
> > 0 eth0 default fw.loc.lan 0.0.0.0 UG 0 0
> > 0 eth0 default fw.loc.lan 0.0.0.0 UG 0
> > 0 0 eth0
> >
> > (fw.loc.lan is the firewall between my LAN and the Internet.)
> >
> > I don't see any reference to eht0:0 at all. I don't know if that
> > matters.
> >
> > After restarting my network, I can't reach anything on the
> > Internet.
> >
> > Does it matter that route doesn't seem to see a difference between
> > eth0 and eth0:0?
> >
> > What do I need to do to be able to do this and not lose access to
> > domains on the other side of my gateway? Why does it change
> > routing so my computer doesn't work through the regular gateway
> > I've set?
> >
> > Thanks!
> >
> > Hal
>
> You don't need to specify the gateway for eth0:0.

Okay, took it out and it works just fine without it.

I had this working before, but couldn't remember the settings. I knew
it was something simple. I had other suggestions in private email from
well meaning people, but they were a lot of work. I wasn't about to go
through and change my entire network to a different range just for the
5 minutes it takes to log in to the router so I can change its address.
Even though I had searched and not found the answer, I was sure it was
only a minute or two of work if I knew what to do.

> I also needed to configure devices that had distinct ip address
> values by default. I had a similar setup until recently when I
> switched to using ip syntax instead of the 'old way.' Here's a sample
> of my interfaces file:
>
> address 123.456.789.2
> netmask 255.255.255.252
> gateway 123.456.789.1
> up ip addr add 10.1.250.15/24 brd 10.1.250.255 dev eth0 label eth0:0
> up ip addr add 10.10.10.15/24 brd 10.10.10.255 dev eth0 label eth0:1
>
> aptitude install iproute
> man ip
> See if something like that will work for you.

I will be looking into that, but it'll be later in the week before I
have time to try it.

Thanks!

Hal


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org