Carl Brewer
2006-Jan-23 02:30 UTC
Setting an alias as the "default" IP address, or something similar?
Hello,
Ive had a poke around through various linux routing documents,
but haven''t found what I think is an elegant solution to a
routing issue I''m having with a hosting provider and RHEL ES 4 running
in a VMware VM.
Here''s a diagram of the situation :
Default route
at provider our host (A)
72.3.230.1/26 ---- 72.3.230.30/26 the VM (B)
192.168.239.1/24 ----- 192.168.239.2/24
72.3.205.160/32
I need to have the 72.3.205.160 address be used by the
linux box B in the VM as its default IP address - ie :
when traffic goes out from it (originating) it needs
to go out the 72.3.205.160/32 interface and then
via the 192.168.239.2 to .1 (default route).
This setup is because the hosting vendor will only allocate
us /32 addresses in addition to the base IP address they supply, which
is fine if we run them as aliases on eth0 on our host, but doesn''t work
so well in a VM (you can''t attach a route to a /32 that I''m
aware of, if you can, I''d *love* to know how!)
Does anyone here have a suggestion for the neatest way to
do this? At present I have the 192.168 network and a static
route on A pointing the 72.3 address via 192.168.239.2 as that
seemed to be the easiest way to do it, and inbound traffic
works fine, but I haven''t found a way to make the box in the
VM use the 72.3.205.160 address as its source when it originates
traffic, so things like DNS queries etc don''t work unless I
also NAT outgoing traffic on A, which I''d prefer not to do unless
there''s no alternative. Maybe a bridge between the two? I
don''t
really have a handle on the VMware bridge setup (it''s VMware
workstation 5.0 at the moment). so maybe it''s something that
would be better done in VMware, but I''d prefer to use a purely IP
routing solution if possible so we''re not tied to VMware (at some
point I want to migrate this to xen or seperate hardware).
Should I maybe use a tunnel? I have no experience with tunneling, and
not really sure of how it would solve the problem
Any suggestions?
Thanks!
Carl
--
======================Vivitec Pty. Ltd.
Suite 6, 51-55 City Rd.
Southbank, 3006.
Ph. +61 3 8626 5626
Fax +61 3 9682 1000
=======================
Alexander Samad
2006-Jan-23 03:22 UTC
Re: Setting an alias as the "default" IP address, or something similar?
On Mon, Jan 23, 2006 at 01:30:48PM +1100, Carl Brewer wrote:> > > Hello, > Ive had a poke around through various linux routing documents, > but haven''t found what I think is an elegant solution to a > routing issue I''m having with a hosting provider and RHEL ES 4 running > in a VMware VM. > > Here''s a diagram of the situation : > > > Default route > at provider our host (A) > 72.3.230.1/26 ---- 72.3.230.30/26 the VM (B) > 192.168.239.1/24 ----- 192.168.239.2/24 > 72.3.205.160/32 >hi maybe I am missign something but can''t your just use this ip r a default via 192.168.239.1 src 72.3.205.160 plus you might need this as well ip r a 192.168.239.0/24 src 192.168.239.2 You might want to look at bridging, the vm interface sort of becomes the external interface and teh vm nic driver keeps the traffic different> > I need to have the 72.3.205.160 address be used by the > linux box B in the VM as its default IP address - ie : > when traffic goes out from it (originating) it needs > to go out the 72.3.205.160/32 interface and then > via the 192.168.239.2 to .1 (default route). > > This setup is because the hosting vendor will only allocate > us /32 addresses in addition to the base IP address they supply, which > is fine if we run them as aliases on eth0 on our host, but doesn''t work > so well in a VM (you can''t attach a route to a /32 that I''m > aware of, if you can, I''d *love* to know how!) > > Does anyone here have a suggestion for the neatest way to > do this? At present I have the 192.168 network and a static > route on A pointing the 72.3 address via 192.168.239.2 as that > seemed to be the easiest way to do it, and inbound traffic > works fine, but I haven''t found a way to make the box in the > VM use the 72.3.205.160 address as its source when it originates > traffic, so things like DNS queries etc don''t work unless I > also NAT outgoing traffic on A, which I''d prefer not to do unless > there''s no alternative. Maybe a bridge between the two? I don''t > really have a handle on the VMware bridge setup (it''s VMware > workstation 5.0 at the moment). so maybe it''s something that > would be better done in VMware, but I''d prefer to use a purely IP > routing solution if possible so we''re not tied to VMware (at some > point I want to migrate this to xen or seperate hardware). > > Should I maybe use a tunnel? I have no experience with tunneling, and > not really sure of how it would solve the problem > > > Any suggestions? > > Thanks! > > Carl > > > > > -- > ======================> Vivitec Pty. Ltd. > Suite 6, 51-55 City Rd. > Southbank, 3006. > Ph. +61 3 8626 5626 > Fax +61 3 9682 1000 > ======================> _______________________________________________ > LARTC mailing list > LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc >_______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Carl Brewer
2006-Jan-23 06:49 UTC
Re: Setting an alias as the "default" IP address, or something similar?
Alexander Samad wrote:> On Mon, Jan 23, 2006 at 01:30:48PM +1100, Carl Brewer wrote: >> >> Hello, >> Ive had a poke around through various linux routing documents, >> but haven''t found what I think is an elegant solution to a >> routing issue I''m having with a hosting provider and RHEL ES 4 running >> in a VMware VM. >> >> Here''s a diagram of the situation : >> >> >> Default route >> at provider our host (A) >> 72.3.230.1/26 ---- 72.3.230.30/26 the VM (B) >> 192.168.239.1/24 ----- 192.168.239.2/24 >> 72.3.205.160/32 >> > hi > > maybe I am missign something but can''t your just use this > > ip r a default via 192.168.239.1 src 72.3.205.160 > > plus you might need this as well > ip r a 192.168.239.0/24 src 192.168.239.2I just needed the first one, thankyou. That worked a treat. Out of curiosity, I have that command currently in rc.local, but is there a better place to put it in the redhat startup sequence? Normally it''d do in /etc/sysconfig/network but I''m not sure of the possibility of putting that sort of thing in there? -- ======================Vivitec Pty. Ltd. Suite 6, 51-55 City Rd. Southbank, 3006. Ph. +61 3 8626 5626 Fax +61 3 9682 1000 =======================
Alexey Toptygin
2006-Jan-23 19:21 UTC
Re: Setting an alias as the "default" IP address, or something similar?
On Mon, 23 Jan 2006, Carl Brewer wrote:>> hi >> maybe I am missign something but can''t your just use this >> >> ip r a default via 192.168.239.1 src 72.3.205.160 >> >> plus you might need this as well >> ip r a 192.168.239.0/24 src 192.168.239.2 > > I just needed the first one, thankyou. That worked a treat. > > Out of curiosity, I have that command currently in rc.local, but is > there a better place to put it in the redhat startup sequence? Normally > it''d do in /etc/sysconfig/network but I''m not sure of the possibility of > putting that sort of thing in there?I haven''t used RedHat in a while, but IIRC you can put GATEWAY=192.168.239.1 into /etc/sysconfig/network-scripts/ifcfg-<interface> file Alexey
Alexander Samad
2006-Jan-23 20:47 UTC
Re: Setting an alias as the "default" IP address, or something similar?
On Mon, Jan 23, 2006 at 05:49:02PM +1100, Carl Brewer wrote:> Alexander Samad wrote: > >On Mon, Jan 23, 2006 at 01:30:48PM +1100, Carl Brewer wrote: > >> > >>Hello, > >>Ive had a poke around through various linux routing documents, > >>but haven''t found what I think is an elegant solution to a > >>routing issue I''m having with a hosting provider and RHEL ES 4 running > >>in a VMware VM. > >> > >>Here''s a diagram of the situation : > >> > >> > >> Default route > >> at provider our host (A) > >> 72.3.230.1/26 ---- 72.3.230.30/26 the VM (B) > >> 192.168.239.1/24 ----- 192.168.239.2/24 > >> 72.3.205.160/32 > >> > >hi > > > >maybe I am missign something but can''t your just use this > > > >ip r a default via 192.168.239.1 src 72.3.205.160 > > > >plus you might need this as well > >ip r a 192.168.239.0/24 src 192.168.239.2 > > I just needed the first one, thankyou. That worked a treat. > > Out of curiosity, I have that command currently in rc.local, but is > there a better place to put it in the redhat startup sequence? Normally > it''d do in /etc/sysconfig/network but I''m not sure of the possibility of > putting that sort of thing in there?Hi Sorry not sure about redhat, but rc.local sounds like the place to put it> > > > -- > ======================> Vivitec Pty. Ltd. > Suite 6, 51-55 City Rd. > Southbank, 3006. > Ph. +61 3 8626 5626 > Fax +61 3 9682 1000 > ======================> _______________________________________________ > LARTC mailing list > LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc >_______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Carl Brewer
2006-Jan-23 22:10 UTC
Re: Setting an alias as the "default" IP address, or something similar?
Alexey Toptygin wrote:> On Mon, 23 Jan 2006, Carl Brewer wrote: > >>> hi maybe I am missign something but can''t your just use this >>> >>> ip r a default via 192.168.239.1 src 72.3.205.160 >>> >>> plus you might need this as well >>> ip r a 192.168.239.0/24 src 192.168.239.2 >> >> >> I just needed the first one, thankyou. That worked a treat. >> >> Out of curiosity, I have that command currently in rc.local, but is >> there a better place to put it in the redhat startup sequence? Normally >> it''d do in /etc/sysconfig/network but I''m not sure of the possibility of >> putting that sort of thing in there? > > > I haven''t used RedHat in a while, but IIRC you can put > GATEWAY=192.168.239.1 > into /etc/sysconfig/network-scripts/ifcfg-<interface> fileThat does the equivalent to the src route above? -- ======================Vivitec Pty. Ltd. Suite 6, 51-55 City Rd. Southbank, 3006. Ph. +61 3 8626 5626 Fax +61 3 9682 1000 =======================
Alexey Toptygin
2006-Jan-23 22:22 UTC
Re: Setting an alias as the "default" IP address, or something similar?
On Tue, 24 Jan 2006, Carl Brewer wrote:> Alexey Toptygin wrote: >> On Mon, 23 Jan 2006, Carl Brewer wrote: >> >>>> hi maybe I am missign something but can''t your just use this >>>> >>>> ip r a default via 192.168.239.1 src 72.3.205.160 >>>> >>>> plus you might need this as well >>>> ip r a 192.168.239.0/24 src 192.168.239.2 >>> >>> >>> I just needed the first one, thankyou. That worked a treat. >>> >>> Out of curiosity, I have that command currently in rc.local, but is >>> there a better place to put it in the redhat startup sequence? Normally >>> it''d do in /etc/sysconfig/network but I''m not sure of the possibility of >>> putting that sort of thing in there? >> >> >> I haven''t used RedHat in a while, but IIRC you can put >> GATEWAY=192.168.239.1 >> into /etc/sysconfig/network-scripts/ifcfg-<interface> file > > That does the equivalent to the src route above?No, sorry, I wasn''t reading very carefully. It''ll add the default route, but without the src. There was some way to run a script every time you bring up an interface, but I don''t remember what it was. Alexey
Denis Ovsienko
2006-Jan-24 07:16 UTC
Re: Setting an alias as the "default" IP address, or something similar?
> Out of curiosity, I have that command currently in rc.local, but is > there a better place to put it in the redhat startup sequence? > Normally it''d do in /etc/sysconfig/network but I''m not sure of the > possibility of putting that sort of thing in there?There are two ways: 1. create /sbin/ifup-local, which will run ''ip ro add'' or ''ip ro replace''. Your routing table will be adjusted each time the interface is brought up (with default route). 2. Wait until I find time for preparing /etc/net for Fedora Extras. Wait until I get my work accepted into Fedora Extras. Wait until /etc/net moves to Fedora Core. Wait until next RedHat Linux is built from that Fedora Core. Buy one and have fun specifying any route attributes in interface configuration files. -- DO4-UANIC