Re: ip aliasing problems
Goran,
That was it!
Thanks,
Kenneth
On 6/22/05, Göran Axelsson <axelsson@acc.umu.se> wrote:
> Hi Kenneth!
>
> Do you really need a gateway on the second interface?
> I would guess your problem is in the order the gateways appears in the
> routing table.
> As the DHCP probably takes longer time to get it's data than the static
> interface it ends up as the second gateway in the routing tables.
>
> I would try to remove the gw definition for the second interface just to
> see what happens.
> It would also be interesting to see what "route" would return as the
> routing table.
> I haven't tried this myself so there's no guarantees that this is the
> solution.
>
> Good luck!
>
> /Göran
>
> Kenneth Stephen wrote:
>
> >Hi,
> >
> > I have the following in my /etc/network/interfaces script :
> >
> >auto eth0 eth0:1
> >iface eth0 inet dhcp
> >#
> ># Added on 06/22/2005 in order to define infrastructure needed for running
> ># DNS on this machine for the local network
> >#
> >iface eth0:1 inet static
> > address 192.168.1.130
> > network 192.168.1.0
> > netmask 255.255.255.0
> > broadcast 192.168.1.255
> > gateway 192.168.1.1
> >
> > This brings up eth0 and eth0:1 correct at boot time. default-if
> >reports "eth0" as being the default. However, I'm having trouble with
> >my firewalling rules because it appears that when I communicate with
> >an external network (example : lynx http://www.debian.org ), the
> >source ip on the packets is set to 192.168.1.130 instead of the ip
> >address that is assigned to eth0 . Is there a way I can change this
> >behaviour so that the outgoing packets have the source ip of the eth0
> >interface?
> >
> >Thanks,
> >Kenneth
> >
> >
> >
>
>
Reply to: