Hi,
Ok, but then we should debug that procedure, not invent something else; I
guess you can do it via iptables, with DNAT, after assigning IP B to eth0:1,
but proxy ARP is the standard solution.
thanks, I will look over it and mail my results. :-)
Florian
--
On Friday 24 March 2006 13:07, Florian Effenberger wrote:
> Hi,
>
> > And you didn't read the "proxy ARP" tip on the page I indicated you.
>
> I did, but everytime I try the commands on the virtual networking page,
> my network goes down...
Ok, but then we should debug that procedure, not invent s
Hi,
And you didn't read the "proxy ARP" tip on the page I indicated you.
I did, but everytime I try the commands on the virtual networking page,
my network goes down...
Florian
---
This SF.Net email is sponsored by xPML, a groundbreaking
On Friday 24 March 2006 10:47, Florian Effenberger wrote:
> Hi,
>
> I've achieved something. By giving tap0 192.168.0.254, eth0 (inside UML)
> 192.168.0.1 and setting 192.168.0.254 as a gateway in UML, I can connect
> to the outside world using NAT.
> However, what I'm still working on is a soluti
Hi,
I've achieved something. By giving tap0 192.168.0.254, eth0 (inside UML)
192.168.0.1 and setting 192.168.0.254 as a gateway in UML, I can connect
to the outside world using NAT.
However, what I'm still working on is a solution to forward packets
received on IP B to the UML using iptables
On Thursday 23 March 2006 10:57, Florian Effenberger wrote:
> Hi,
> >> eth0 IP: 85.123.123.10
> > Let's say "IP A"
> >> eth0:1 IP: 85.123.123.15
> > "IP B"
> > That could be due to a network hang fixed _after_ 2.4.25 - upgrade to my
> > 2.4.x -bs2 patchset on my homepage.
> I run 2.6.8. :-)
Hi,
thanks for your mail.
eth0 IP: 85.123.123.10
Let's say "IP A"
eth0:1 IP: 85.123.123.15
"IP B"
That could be due to a network hang fixed _after_ 2.4.25 - upgrade to my 2.4.x
-bs2 patchset on my homepage.
I run 2.6.8. :-)
host: tap0 uses "IP A", eth0:1 is removed.
UML: eth0 is as
On Monday 20 March 2006 17:41, Florian Effenberger wrote:
> Hi there,
>
> I run UML on Debian 3.1. It works fine, I can boot the virtual machine,
> the filesystem and kernel do run. However, I'm having a hard time doing
> the networking stuff.
> My host machine has kernel 2.6.8 with Debian 3.1, my
Hi there,
I run UML on Debian 3.1. It works fine, I can boot the virtual machine,
the filesystem and kernel do run. However, I'm having a hard time doing
the networking stuff.
My host machine has kernel 2.6.8 with Debian 3.1, my UML machine 2.4.25
with Debian 3.1. My network setup is as foll