Description of problem:
NetworkManager can use only wired media sources for DLS connections, what is
wrong! I use pppoe connections under windows and mac osx trough my wifi card
without any problem. My current network topology is: adsl modem with ethernet
switch connected to wifi access-point, i have also fedora server connected to
adsl switch for dhcpd&&ddns services. When my laptop open they try to establish
wifi source without getting ip4 address, after that i click on pppoe connection
to get real internet ip4 address.
thx for support!
out of curiousity, can more than one machine connect to PPPoE via your provider through your wifi access point at the _same time_?
As i understand pppoe protoclon that is true.
1) My Other notebook ->
2) My NoteBook -> My Wifi access -> My network -> 4) ADSL Hub -> ISP.
3) My stnand Alone ->
Each of them can have self pppoe connection 1, 2, 3, 4 have external IP address.
I really test only two connection at same time 2) and 4). Because i do not need so match of external ip's set.
other point is i shure about defect in design of networkmanager topology. because i do not see media source as self described node in network manager setting dialogs.
more correct way work for networks you can find in OS X and windows Vista. These booth os have good network manager and you can create infinite amount of customized network in right way.
for example when you connect your note book to some network with dhcpd they putt mac address and network address space to network id, accoicied with custom name. then when you remove you notebook from network, and initiate vpn connection to your office place. vista detect your new virtual network adapter and setup right setting for virtual network and network name. that the right way to make network manager to work.
what network manager must have, here is nodes:
* media source can be a: ethernet, vpn, wifi, bluetooth, irda, pppoe
* network can be: ip netowrk with dhcpd, ip network without dhcpd
* custom networks: can be combination of two types of nodes (network+media source)
thx for listning
One another example.
In that case described above, we can cover all possible connections.
when i connect my pc to ethernet i got ip from dhcpd server and i got server mac address + network mask. now knowbase layer can be configured by user and i can set dhcpdid client data, for example.
now i have new network source with custom network name "auto eth0" in connection list. as user i can custumize that connection name as "my home network".
after that i come out from home and go to office, then install vpn connection too my home. network manager must got same network id (dhcp server mac address + network/mask) and show same name.
Networkmanager must have main menu with connection names only. That names linked to network source.
Advanced dialog must show media source list (network layers\knowbase layer) separated by type and hardlinked to real devices.
Last true for pppoe because i can link network layers by each other. VPN can be linked to eth0 or wifi. PPPOE can be linked also to VPN or eth0 or WIFI. And only Cursom Network Manager show real network name.
If network do not have dynamic address allocation, then we must create new media source in advanced menu.
thx again! any comments? sssory for bad english.
i wana say more:
Same vpn, pppoe connections can produce different network id and have different connection name in different time.
Connections can have favorite star, and only favorites shown in drop down box under taskicon area.
Also i can show full connections list dialog and add/remove some associated name.
Reporter, are you still running Fedora 9, or have you upgraded to Fedora 10 or
Rawhide? In either case, can you let us know whether the issue is still happening, and give the current version of the kernel and NM packages you're
using. Thank you.
Fedora Bugzappers volunteer triage team
Hi. I switched to F10.
As i understand noting changed here.
NM still do not have feature to choice source for DSL connections. It only work as DSL for ethernet, and not DSL for wifi.
That is bug/feature.
Changing title to reflect the enhancement request.
Fedora Bugzappers volunteer triage team
*** Bug 495491 has been marked as a duplicate of this bug. ***
This bug has been triaged
Fedora Bugzappers volunteer triage team
Is someone working on this?
Alice one of the bigger providers here in Germany has this problem.
They are giving their customers a DSL modem with internal wifi hardware and you have to use DSL over wifi to use their internet service.
I have still not found an easy way to configure this in Fedora.
Adding FutureFeature keyword to mark feature request as per
*** Bug 556284 has been marked as a duplicate of this bug. ***
Is there a fix for this issue?
It's a very small change of source to enable PPPoE over wifi,why it's still not been fixed?
This small change will bring a huge improvement and a exciting user-experience to us who want PPPoE over wifi .
I hope it will be coming soon!
Thank you guys working hard for the Networkmanager！
It's not a small change actually, but it'll happen.
I also thank you guys for all your hard work. NetworkManager is best thing since sliced bread ;)
@Dan Williams what changes need to be made? is the a blueprint for this? I would be willing to do some work, and recruit and train helpers, but need a plan.
flossk.org is very interested in this, for kosovo provider ipko it is needed.
we have a fedora ambassador and are working on two conferences this year
I can just confirm that this is still not implemented in latest NM in F13. It would be a great feature to have.
*** Bug 585530 has been marked as a duplicate of this bug. ***
I hit the same problem as well, is there any code around yet ?
(In reply to comment #20)
> I hit the same problem as well, is there any code around yet ?
Not yet, no.
I had to configure by hand the old network package, and rp-pppoe. Changing the ifcfg- file setting "ETH" from "eth0" to "wlan0" the magic happens.
Better than nothing, but obviously it should be better if NetworkManager can support it...
Still not happening in Fedora 15.
Will it be available in F15 in upcoming updates...
(In reply to comment #1)
> out of curiousity, can more than one machine connect to PPPoE via your provider
> through your wifi access point at the _same time_?
This is a very interesting question. Here are my thoughts, please feel to correct if you think they're wrong.
Telephone line -> DSL Modem -> Access point -> Your laptop (wireless)
DSL modems can act as a bridge and just pull open the ATM cells and give you a layer 2 network to authenticate with, etc... -OR- they can handle the PPPoE for you and then leave you with a regular ethernet network that probably has DHCP from the server, etc...
An AP itself actually has a mini layer 2 switch that hooks it's ethernet port up to "all the 802.11 ports- eg: different laptops". The catch is that wireless traffic generally has a huge collision domain, whereas really switched wired networks don't :) If the switch itself was doing the auth, there's no reason why multiple laptops couldn't simultaneously use the same AP and single DSL modem AFAIK.
Assuming that the AP doesn't somehow scrape out the PPPoE traffic (it probably shouldn't), then you'd be able to use your laptop to auth with PPPoE and be set. The only limitation that I know of for having two different laptops both try to PPPoE auth is that I assume there might be a limitation on the service providers end as to how many simultaneous connected sessions are allowed. I'd bet it works though :) Would probably definitely work with two different accounts.
I actually came here, since I noticed I couldn't do wireless PPPoE over network manager, and decided to comment, because I actually wanted to plug a WAP54g AP, into my crappy DSL modem, and see if network manager could take care of the PPPoE auth wirelessly, the way it does so beautifully over a wired network.
Fix network manager, and I'll happily test all this for you,
(In reply to comment #17)
> what changes need to be made? is the a blueprint for this?
Currently the daemon assumes that only NMDeviceEthernet can do PPPoE, so the code to handle PPPoE is all in nm-device-ethernet.c. You'd need to make NMDeviceWifi be able to do the same thing, which will involve some amount of code reorganization; possibly moving the PPPoE handling down into NMDevice? Or else moving the complicated bits into another file so that nm-device-wired and nm-device-wifi can just call functions there at the right points.
The ethernet-only assumption is probably also made in various other places in the source tree. (Eg, the settings plugins probably only try to read in PPPoE settings on ethernet connections, etc.)
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
It looks like this has been fixed, see https://bugzilla.gnome.org/show_bug.cgi?id=559134 for details.