On Sun, Apr 09, 2006 at 01:54:58PM +0100, Nic wrote:
> But I have found a solution that satisfies all my constraints and I
> thought I'd note it here (shall I put it on the wiki as well?)
The wiki is a fine place for things like this.
> dhcp client's can send a dhcp-client-identifier with their r
")
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
[EMAIL PROTECTED] said:
>> Can someone explain how to make the UML side of the tun devices have
>> unique HWAddrs?
Jason Lunz replied:
> Unless you somehow specify otherwise, though, the uml side alwa
[EMAIL PROTECTED] said:
> Now... all this works in terms of the plumbing but *all* the UMLs have
> the same eth device HWAddr (mac address) so they all get the same IP.
>
> I want them to have different IPs.
>
>
> I thought, because they were all using different tun devices that they
> would get d
t; Sent: Friday, March 24, 2006 7:43 AM
> To: user-mode-linux-user@lists.sourceforge.net
> Subject: [uml-user] tun/tap devices and uniqueness
>
>
> I've got a box with a software bridge on it running as a UML host.
>
> Each UML that runs gets it's own tun device added
I've got a box with a software bridge on it running as a UML host.
Each UML that runs gets it's own tun device added to the bridge. The
UML is then run like this:
# Start the UML
kernel
ubd0=root_fs \
con0=fd:0,fd:1 \
eth0=tuntap,$IF
where $IF is the name of the tun de
