<span class="gmail_quote"><br><br></span><div><span class="e" id="q_10996e85d0d528a1_0">On 2/23/06, <b class="gmail_sendername">Scott James Remnant</b> <<a href="mailto:scott@ubuntu.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
scott@ubuntu.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 2/23/06, Nicolas Kassis <<a href="mailto:nic.kassis@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">nic.kassis@gmail.com</a>> wrote:<br><br>> Related to networking being messed up in dapper, I reported a bug I have
<br>> been experiencing bug 32570. My two prism54 cards (one internal and the
<br>> other pcmcia) receive the same eth0 name and cause a clash. Anyone else<br>> has this issue ?<br>><br>This means that you've named one of the cards "eth0" in /etc/iftab,<br>but not the other -- and the other got allocated that name by the
<br>kernel.<br><br>The easiest way to fix this is just to name the other card with a line like:<br><br> eth1 mac xx:xx:xx:xx:xx:xx<br><br>in /etc/iftab, where the xx's get replaced by the MAC address of that card.<br><br>
<br>The _clashed moniker is just a temporary one, by the way -- it's there<br>so I can clearly see the renaming working. By Beta release that will<br>change to just using the next free number, so the card would be "eth1"
<br>(assuming you hadn't allocated that in /etc/iftab).<br></blockquote></div><br><br></span></div>Ok thanks. Sorry for the bug report.<br><br>Nic<br>