PPPoE connection uses wrong NIC

[Quintin Beukes <quintin last za net>]

Hey,

I am trying to connect to a wireless-broadband provider using an
iBurst modem. The driver creates a network device, which reports
itself as a wireless device (so iwconfig lists the signal strength).
It's not a GPRS/3G, so I can't take the wireless-broadband steps in
the connection editor. The DSL steps should work perfectly, except the
nic passed to pppd is my ethernet device instead of the one created by
the driver. PPPoE must happen via this device, where the driver will
pass it onto the modem via USB and the rest happens as usual.

Either way, when NetworkManager invokes pppd, it does it as follows:
Dec 29 12:31:47 quintin-VIAO NetworkManager: <debug>
[1262082707.053800] nm_ppp_manager_start(): Command line:
/usr/sbin/pppd nodetach lock nodefaultroute user <my-user> plugin
rp-pppoe.so nic-eth0 noauth nodeflate usepeerdns mru 1492 mtu 1492
lcp-echo-failure 3 lcp-echo-interval 20 ipparam
/org/freedesktop/NetworkManager/PPP/8 plugin
/usr/lib/pppd/2.4.4/nm-pppd-plugin.so

As you can see, rp-pppoe.so is passed the parameter nic-eth0. This
should instead be ib0. If I copy this line and remove the
nm-pppd-plugin and change the nic-eth0 to ib0 I can connect (in fact,
that's how I sent this e-mail).

How can I configure network manager to use the correct nic?

My current configuration file:
[connection]
id=iBurst
uuid=60d71ae5-7c0e-4bf9-a338-939fe95585b2
type=pppoe
autoconnect=false
timestamp=0

[ppp]
noauth=true
refuse-eap=false
refuse-pap=false
refuse-chap=false
refuse-mschap=false
refuse-mschapv2=false
nobsdcomp=false
nodeflate=false
no-vj-comp=false
require-mppe=false
require-mppe-128=false
mppe-stateful=false
crtscts=false
baud=0
mru=1492
mtu=1492
lcp-echo-failure=0
lcp-echo-interval=0

[ipv4]
method=auto
ignore-auto-routes=false
ignore-auto-dns=false
dhcp-send-hostname=false
never-default=false

[pppoe]
username=Anita_Geber iburst co za
password=080889SH

[802-3-ethernet]
speed=0
duplex=full
auto-negotiate=true
mtu=1492

I tried adding a mac-address line to the ethernet section, but this
results in the connection being marked as invalid, and not being
available.

Quintin Beukes