Re: [pkg-wpa-devel] Bug#776338: wpa: wpasupplicant-udeb missing from kfreebsd installation media
tags -1 - patch Hi On 2015-01-26 19:52:54, Michael Gilbert wrote: > package: src:wpa > version: 2.3-1 > severity: important > tags: patch > > Hi, > > The kfreebsd installation media currently lack wpa support. Here is a > patch that adds support for building the udeb. I'm closing this bug, as your patch doesn't -and can't- work (anytime soon). Please don't inflate the bug severity, this would be a request for a new feature, not a bug. In order to work, wpasupplicant requires either libnl or libpcap. libnl is linux-any (it requires the nl80211 interface of the linux kernel), therefore wpasupplicant uses libpcap on kfreebsd-any, which however doesn't provide a udeb. If I'd take your patch as-is, the kfreebsd-any wpasupplicant udeb would therefore gain a dependency on the non-existing package libpcap0.8-udeb (instant RC bug and introducing a new package at this time in the jessie freeze is certainly not appreciated by the release team or the d-i maintainers). So the first step here would be to get libpcap to provide a udeb, at least on kfreebsd-any. The next step is d-i, or technically netcfg, itself, which only provides support for scanning via wext (wireless extension), a deprecated kernel-userspace API of the linux kernel. As kfreebsd, to the best of my knowledge, doesn't emulate this API to userspace, netcfg would need to gain support for the native kfreebsd wlan interfaces - and ideally for linux' new nl80211 API as well. The same goes for actually managing the interface from within netcfg. If I remember correctly, Kel Modderman did originally suggest an alternative way to scan via wpasupplicant (and thereby to abstract (most of, at least for scanning) the wlan interface handling from netcfg), rather than making it depend on the deprecated wext Linux API, but netcfg chose a different way. I'd be happy to provide a udeb on kfreebsd-any as well, but these kfreebsd specific issues need to be solved first. Feel free to re-open this bug (or to file a new one), once this has been resolved and tested - or has at least reached the planning state for stretch. Regards Stefan Lippers-Hollmann pgp0cv__N3J7k.pgp Description: Digitale Signatur von OpenPGP
Processed: Re: [pkg-wpa-devel] Bug#636321: wpasupplicant-udeb: TP-LINK WN722N (AR9271) not detected as usable wlan interface
Processing commands for cont...@bugs.debian.org:
> clone 636321 -1
Bug#636321: kernel-wedge: nic-wireless-modules missing ath9k_htc
Bug 636321 cloned as bug 636385.
> retitle -1 kernel-wedge: nic-wireless-modules missing rt2800{pci,usb}
Bug #636385 [kernel-wedge] kernel-wedge: nic-wireless-modules missing ath9k_htc
Changed Bug title to 'kernel-wedge: nic-wireless-modules missing
rt2800{pci,usb}' from 'kernel-wedge: nic-wireless-modules missing ath9k_htc'
> tags -1 - patch
Bug #636385 [kernel-wedge] kernel-wedge: nic-wireless-modules missing
rt2800{pci,usb}
Removed tag(s) patch.
> tags -1 + d-i
Bug #636385 [kernel-wedge] kernel-wedge: nic-wireless-modules missing
rt2800{pci,usb}
Ignoring request to alter tags of bug #636385 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
636385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636385
636321: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636321
-1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.131231596728928.transcr...@bugs.debian.org
Bug#636321: [pkg-wpa-devel] Bug#636321: wpasupplicant-udeb: TP-LINK WN722N (AR9271) not detected as usable wlan interface
clone 636321 -1
retitle -1 kernel-wedge: nic-wireless-modules missing rt2800{pci,usb}
tags -1 - patch
tags -1 + d-i
thanks
On Tuesday 02 August 2011, mathieu.mil...@gmail.com wrote:
> Hi,
> All my tests were done with the extracted archive of firmwares available at
> this address:
> http://cdimage.debian.org/cdimage/unofficial/non-free/firmware/unstable/current/
>
> I've also tested a rt2800 usb key, same symptons as the atheros usb key.
> I understand wpasupplicant-udeb is a new package and need testing, and all i
> can do is testing (i don't know much in linux dev).
Same story as with ath9k_htc, kernel-wedge omits installing the
required kernel modules.
> Stefan Lippers-Hollmann a écrit :
[...]
> > I don't know if this bug report is to be associated with
> > wpasupplicant(-udeb)
> > (or netcfg ?). Feel free to correct me.
>
> After a second look, no it's not - it's again a bug in kernel-wedge.
> The kernel module needed by your AR9271 device, namely ath9k_htc, is
> not copied to the nic-wireless-modules udeb.
>
> wpasupplicant has only two modes of operation (well, tree - if you also
> count encrypted wired ethernet, but this is not present in the udeb and
> pretty rare), wext (legacy and strongly discourages, like your ipw2200)
> and nl80211 (all mac80211 based drivers, like your rt2500usb, ath5k,
> ath9k_htc) - if it works for one of each group, it usually works for
> all. Hardware dependent bugs are then usually courtesy of kernel bugs,
> missing firmwares or - as in this case - kernel-wedge forgetting
> important kernel modules, because wpasupplicant only knows 2 kinds of
> 'hardware' (abstractions) wext or nl80211. wpasupplicant only 'gets a
> chance' to mess up again, if it has to deal with different encryption
> methods (WEP vs. WPA1/ TKIP vs. WPA2/ CCMP vs. IEEE80211X, vs. even
> more complex sceanarios), but keep in mind that in order to keep the
> wpasupplicant udeb small, more exotic flavours of encryption have been
> omitted from the udeb.
>
> Therefore please check if the required kernel modules and firmware
> blobs are present to d-i/ netcfg, before filing further bugs against
> the wpasupplicant package.
>
> > I've burned the i386 unstable netinstall as of 2011-08-01 and tried to
> > connect
> > to my WPA-PSK network.
> > Plugged in my AR9271 usb key, and got this from the logs (end of the
> > attached log):
[...]
> > Aug 2 07:55:11 kernel: [ 209.204880] usb 1-6: New USB device found,
> > idVendor=0cf3, idProduct=9271
[...]
> > No new interface detected in d-i, can't use this wifi key with d-i.
>
> No wonder, if there is no kernel module to drive it, see attached patch
> against kernel-wedge (untested).
A patch against kernel-wedge will follow, once I know the newly
assigned bug number.
Regards
Stefan Lippers-Hollmann
signature.asc
Description: This is a digitally signed message part.
Processed: Re: [pkg-wpa-devel] Bug#636321: wpasupplicant-udeb: TP-LINK WN722N (AR9271) not detected as usable wlan interface
Processing commands for cont...@bugs.debian.org: > retitle 636321 kernel-wedge: nic-wireless-modules missing ath9k_htc Bug #636321 [wpasupplicant-udeb] wpasupplicant-udeb: TP-LINK WN722N (AR9271) not detected as usable wlan interface Changed Bug title to 'kernel-wedge: nic-wireless-modules missing ath9k_htc' from 'wpasupplicant-udeb: TP-LINK WN722N (AR9271) not detected as usable wlan interface' > reassign 636321 kernel-wedge 2.78 Bug #636321 [wpasupplicant-udeb] kernel-wedge: nic-wireless-modules missing ath9k_htc Bug reassigned from package 'wpasupplicant-udeb' to 'kernel-wedge'. Bug No longer marked as found in versions wpasupplicant/0.7.3-3.1. Bug #636321 [kernel-wedge] kernel-wedge: nic-wireless-modules missing ath9k_htc Bug Marked as found in versions kernel-wedge/2.78. > tags 636321 + patch Bug #636321 [kernel-wedge] kernel-wedge: nic-wireless-modules missing ath9k_htc Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 636321: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.131229686022485.transcr...@bugs.debian.org
Processed: Re: Processed (with 1 errors): Re: Bug#636259: wpasupplicant-udeb: ipw2200 WPA no connection established
Processing commands for cont...@bugs.debian.org:
> tags 636259 + patch
Bug #636259 [kernel-wedge] kernel-wedge: nic-wireless-modules missing
lib80211_crypt_{wep,ccmp,tkip}
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
636259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636259
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.13122438196692.transcr...@bugs.debian.org
Processed (with 1 errors): Re: Bug#636259: wpasupplicant-udeb: ipw2200 WPA no connection established
Processing commands for cont...@bugs.debian.org:
> reopen 636259
Bug #636259 {Done: "Stefan Lippers-Hollmann" }
[wpasupplicant-udeb] wpasupplicant-udeb: ipw2200 WPA no connection established
> retitle 636259 kernel-wedge: nic-wireless-modules missing
> lib80211_crypt_{wep,ccmp,tkip}
Bug #636259 [wpasupplicant-udeb] wpasupplicant-udeb: ipw2200 WPA no connection
established
Changed Bug title to 'kernel-wedge: nic-wireless-modules missing
lib80211_crypt_{wep,ccmp,tkip}' from 'wpasupplicant-udeb: ipw2200 WPA no
connection established'
> reassign 636259 kernel-wedge 2.78
Bug #636259 [wpasupplicant-udeb] kernel-wedge: nic-wireless-modules missing
lib80211_crypt_{wep,ccmp,tkip}
Bug reassigned from package 'wpasupplicant-udeb' to 'kernel-wedge'.
Bug No longer marked as found in versions wpasupplicant/0.7.3-3.1.
Bug #636259 [kernel-wedge] kernel-wedge: nic-wireless-modules missing
lib80211_crypt_{wep,ccmp,tkip}
Bug Marked as found in versions kernel-wedge/2.78.
> tags + patch
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
636259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636259
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.13122433775436.transcr...@bugs.debian.org
Re: [pkg-wpa-devel] Bug#610931: Please build wpasupplicant-udeb
Hi I've now uploaded the package. Please see the attached NMU patch. Gaudenz Excerpts from Gaudenz Steinlin's message of 2011-07-30 04:08:32 +0200: > Excerpts from Kel Modderman's message of 2011-07-30 01:44:07 +0200: > > On Sat, 30 Jul 2011 06:25:00 AM Gaudenz Steinlin wrote: > > > Excerpts from Kel Modderman's message of 2011-07-27 13:30:37 +0200: > > > > On Wed, 27 Jul 2011 02:43:02 AM Gaudenz Steinlin wrote: > > > > > OK. How do you feel about me NMUing wpa_supplicant to add the udeb? I > > > > > added an updated patch for the udeb to this mail. If you are OK I'll > > > > > upload this as an NMU after libnl1-udeb enters the archive. > > > > > > > > I would be very happy for you to do that. > > > > > > After some more investigation we (I and Otavio) decided that we rather > > > want to move wpasupplicant to build against libnl3. I guess this has > > > to be done at some point anyway and it avoids to have to do the whole > > > work again for libnl3. So we created a udeb for libnl3 and will upload > > > this soon. I hope you agree to this change. If you are against it > > > please reply soon. > > > > This is a far more invasive change than just adding the udeb. Please be > > prepared to pick up the pieces in case regression in stable functionality > > are > > introduced with such a change. > > > > Doing this when moving from wpa_supplicant 0.7.x -> 0.8.x (not yet > > released) > > would be more appropriate in my opinion. > > > > I am less happy about this change, but do not oppose NMU's regardless of > > the > > risk, the rewards may be worth it. > > I can understand your concerns. > > > > > > > > > The only change needed in wpasupplicant for this is to set > > > CONFIG_LIBNL20=y > > > in the linux and udeb configs. > > > > And cross your fingers that it works just the same, without any noticable > > change to the end users. > > For what it's worth I'm using a wpasupplicant built against libnl3 > since 3 days on my laptop here at Debconf without any problems. But as > it stands this is just testing on one single driver (iwlwifi) on one > single network. Probably some wider testing would be appropriate. > > Gaudenz -- Ever tried. Ever failed. No matter. Try again. Fail again. Fail better. ~ Samuel Beckett ~ build_wpasupplicant_udeb_v3.patch Description: Binary data
Re: [pkg-wpa-devel] Bug#610931: Please build wpasupplicant-udeb
Excerpts from Kel Modderman's message of 2011-07-30 01:44:07 +0200: > On Sat, 30 Jul 2011 06:25:00 AM Gaudenz Steinlin wrote: > > Excerpts from Kel Modderman's message of 2011-07-27 13:30:37 +0200: > > > On Wed, 27 Jul 2011 02:43:02 AM Gaudenz Steinlin wrote: > > > > OK. How do you feel about me NMUing wpa_supplicant to add the udeb? I > > > > added an updated patch for the udeb to this mail. If you are OK I'll > > > > upload this as an NMU after libnl1-udeb enters the archive. > > > > > > I would be very happy for you to do that. > > > > After some more investigation we (I and Otavio) decided that we rather > > want to move wpasupplicant to build against libnl3. I guess this has > > to be done at some point anyway and it avoids to have to do the whole > > work again for libnl3. So we created a udeb for libnl3 and will upload > > this soon. I hope you agree to this change. If you are against it > > please reply soon. > > This is a far more invasive change than just adding the udeb. Please be > prepared to pick up the pieces in case regression in stable functionality are > introduced with such a change. > > Doing this when moving from wpa_supplicant 0.7.x -> 0.8.x (not yet released) > would be more appropriate in my opinion. > > I am less happy about this change, but do not oppose NMU's regardless of the > risk, the rewards may be worth it. I can understand your concerns. > > > > > The only change needed in wpasupplicant for this is to set CONFIG_LIBNL20=y > > in the linux and udeb configs. > > And cross your fingers that it works just the same, without any noticable > change to the end users. For what it's worth I'm using a wpasupplicant built against libnl3 since 3 days on my laptop here at Debconf without any problems. But as it stands this is just testing on one single driver (iwlwifi) on one single network. Probably some wider testing would be appropriate. Gaudenz -- Ever tried. Ever failed. No matter. Try again. Fail again. Fail better. ~ Samuel Beckett ~ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1311991544-sup-5662@meteor.durcheinandertal.local
Re: [pkg-wpa-devel] Bug#610931: Please build wpasupplicant-udeb
On Sat, 30 Jul 2011 06:25:00 AM Gaudenz Steinlin wrote: > Excerpts from Kel Modderman's message of 2011-07-27 13:30:37 +0200: > > On Wed, 27 Jul 2011 02:43:02 AM Gaudenz Steinlin wrote: > > > OK. How do you feel about me NMUing wpa_supplicant to add the udeb? I > > > added an updated patch for the udeb to this mail. If you are OK I'll > > > upload this as an NMU after libnl1-udeb enters the archive. > > > > I would be very happy for you to do that. > > After some more investigation we (I and Otavio) decided that we rather > want to move wpasupplicant to build against libnl3. I guess this has > to be done at some point anyway and it avoids to have to do the whole > work again for libnl3. So we created a udeb for libnl3 and will upload > this soon. I hope you agree to this change. If you are against it > please reply soon. This is a far more invasive change than just adding the udeb. Please be prepared to pick up the pieces in case regression in stable functionality are introduced with such a change. Doing this when moving from wpa_supplicant 0.7.x -> 0.8.x (not yet released) would be more appropriate in my opinion. I am less happy about this change, but do not oppose NMU's regardless of the risk, the rewards may be worth it. > > The only change needed in wpasupplicant for this is to set CONFIG_LIBNL20=y > in the linux and udeb configs. And cross your fingers that it works just the same, without any noticable change to the end users. > > Gaudenz Kel. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201107300944.07976@otaku42.de
Re: Bug#610931: Please build wpasupplicant-udeb
Excerpts from Kel Modderman's message of 2011-07-27 13:30:37 +0200: > On Wed, 27 Jul 2011 02:43:02 AM Gaudenz Steinlin wrote: > > > > OK. How do you feel about me NMUing wpa_supplicant to add the udeb? I > > added an updated patch for the udeb to this mail. If you are OK I'll > > upload this as an NMU after libnl1-udeb enters the archive. > > I would be very happy for you to do that. After some more investigation we (I and Otavio) decided that we rather want to move wpasupplicant to build against libnl3. I guess this has to be done at some point anyway and it avoids to have to do the whole work again for libnl3. So we created a udeb for libnl3 and will upload this soon. I hope you agree to this change. If you are against it please reply soon. The only change needed in wpasupplicant for this is to set CONFIG_LIBNL20=y in the linux and udeb configs. Gaudenz -- Ever tried. Ever failed. No matter. Try again. Fail again. Fail better. ~ Samuel Beckett ~ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1311970907-sup-4875@meteor.durcheinandertal.local
Re: Bug#610931: Please build wpasupplicant-udeb
On Wed, 27 Jul 2011 02:43:02 AM Gaudenz Steinlin wrote: > > OK. How do you feel about me NMUing wpa_supplicant to add the udeb? I > added an updated patch for the udeb to this mail. If you are OK I'll > upload this as an NMU after libnl1-udeb enters the archive. I would be very happy for you to do that. Thanks, Kel. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201107272130.37993@otaku42.de
Re: Bug#610931: Please build wpasupplicant-udeb
On Tue, Jul 26, 2011 at 18:43, Gaudenz Steinlin wrote: > > OK. How do you feel about me NMUing wpa_supplicant to add the udeb? I > added an updated patch for the udeb to this mail. If you are OK I'll > upload this as an NMU after libnl1-udeb enters the archive. It seems that libnl3 is already available and wpa-supplicant has support for it AFAIK so it seems better to get the patch integrated on it to avoid redoing it later. wpa-supplicant also needs to update to use this but seems worth it. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
Re: Bug#610931: Please build wpasupplicant-udeb
Excerpts from Kel Modderman's message of 2011-07-26 15:14:11 +0200:
> Hi,
>
> On Mon, 25 Jul 2011 09:34:27 AM Gaudenz Steinlin wrote:
> > > > > > > Has there been any solution for the netcfg integration already,
> > > > > > > see <201011041811.11753@otaku42.de> [1], referring to the
> > > > > > > originally proposed introduction of embedded source copies of
> > > > > > > wpasuppliant's wpa_ctrl.[hc] into netcfg. Please also keep in
> > > > > > > mind that crda/ wireless-regdb is required for accessing
> > > > > > > channels 11-13/14 on modern drivers.
> > > > > >
> > > > > > I've applied the existing WPA netcfg support patches developed by
> > > > > > Glenn Saberton, and they do appear to include a (stripped down)
> > > > > > wpa_ctrl.c.
> > > > >
> > > > > That stripped down crap probably was extracted from a sideline
> > > > > project (python-wpactrl) I was working on, and is not good long term
> > > > > solution.
> > > > >
> > > > > wpa_ctrl.{c,h} from current wpasupplicant source tree have lots more
> > > > > dependency on other stuff. Extracting and patching wpa_ctrl.{c,h} to
> > > > > be standalone is something which should be avoided - I just do not
> > > > > know how currently.
> > > > >
> > > > > Asked upstream wpa_supplicant if wpa_ctrl could be provided in a way
> > > > > where it could be a shared library but received no response.
> > > >
> > > > Is there any progress on this?
> > >
> > > Nope.
> >
> > Do you think it's worth poking about this again? The current code in
> > netcfg works (at least for the debconf wpa-psk network), but a real
> > library would be nicer ;-).
>
> It cannot hurt to ask. I've already asked before, so maybe someone else can
> this time :).
I'll see what I can do.
>
> >
> > > > > > I
> > > > > > have no idea what the story is with crda/wireless-regdb, as I said
> > > > > > before, I don't know anything about WPA. If you'd like to help
> > > > > > out, though, your knowledge would be greatly valued.
> > > > >
> > > > > I wouldn't mind helping out, don't know how though, Have little idea
> > > > > about D-I environment and took long enough to just reply to this
> > > > > request to feel a little embarrassed.
> > > > >
> > > > > Also haven't seen the proposed change to netcfg anytime in recent
> > > > > past to comment further. Can that be reviewed?
> > > >
> > > > It's in branch people/womble/wpa of
> > > > git://git.debian.org/git/d-i/netcfg.
> > > >
> > > > Gaudenz
> > >
> > > Thanks for the link.
> >
> > Do you have time to look at the code in the next days? Otherwise I'll
> > probably just merge as it is now and we can fix things later if there
> > are problems.
>
> Do not wait for any activity from me, I'm currently not very active with
> Debian work - mostly keeping up with basic maintenace related tasks.
>
> Not familiar with netcfg or the debian-installer environment at all
> yet.
OK. How do you feel about me NMUing wpa_supplicant to add the udeb? I
added an updated patch for the udeb to this mail. If you are OK I'll
upload this as an NMU after libnl1-udeb enters the archive.
>
> >
> > I have another yet unresolved problem: With the proposed udeb
> > configuration from the original patch and using the netlink driver I can
> > connect to the network, but DHCP does not work. When I build a udeb with
> > the same
> > configuration as for the normal linux package minus DBUS and smartcard
> > support it works. Do you know which options I need to include to get a
> > package where DHCP also works with the netlink driver?
>
> From the top of my head I do not know why you observe this difference in
> behaviour. Where WEXT works, nl80211 should work and vice versa.
I found out that I have to enable either CONFIG_IEEE8021X_EAPOL or
CONFIG_WPS. I don't know why it is like this, but both options don't
seem to be related to the problem. This is probably a bug in
wpa_supplicant where a #ifdef enables some code that should be enabled
unconditionally. But a quick grep through the source code did not show
something suspicious. If I get around to it I'll report a bug
upstream.
Gaudenz
--
Ever tried. Ever failed. No matter.
Try again. Fail again. Fail better.
~ Samuel Beckett ~
build_wpasupplicant_udeb_v2.patch
Description: Binary data
Re: Bug#610931: Please build wpasupplicant-udeb
Hi,
On Mon, 25 Jul 2011 09:34:27 AM Gaudenz Steinlin wrote:
> > > > > > Has there been any solution for the netcfg integration already,
> > > > > > see <201011041811.11753@otaku42.de> [1], referring to the
> > > > > > originally proposed introduction of embedded source copies of
> > > > > > wpasuppliant's wpa_ctrl.[hc] into netcfg. Please also keep in
> > > > > > mind that crda/ wireless-regdb is required for accessing
> > > > > > channels 11-13/14 on modern drivers.
> > > > >
> > > > > I've applied the existing WPA netcfg support patches developed by
> > > > > Glenn Saberton, and they do appear to include a (stripped down)
> > > > > wpa_ctrl.c.
> > > >
> > > > That stripped down crap probably was extracted from a sideline
> > > > project (python-wpactrl) I was working on, and is not good long term
> > > > solution.
> > > >
> > > > wpa_ctrl.{c,h} from current wpasupplicant source tree have lots more
> > > > dependency on other stuff. Extracting and patching wpa_ctrl.{c,h} to
> > > > be standalone is something which should be avoided - I just do not
> > > > know how currently.
> > > >
> > > > Asked upstream wpa_supplicant if wpa_ctrl could be provided in a way
> > > > where it could be a shared library but received no response.
> > >
> > > Is there any progress on this?
> >
> > Nope.
>
> Do you think it's worth poking about this again? The current code in
> netcfg works (at least for the debconf wpa-psk network), but a real
> library would be nicer ;-).
It cannot hurt to ask. I've already asked before, so maybe someone else can
this time :).
>
> > > > > I
> > > > > have no idea what the story is with crda/wireless-regdb, as I said
> > > > > before, I don't know anything about WPA. If you'd like to help
> > > > > out, though, your knowledge would be greatly valued.
> > > >
> > > > I wouldn't mind helping out, don't know how though, Have little idea
> > > > about D-I environment and took long enough to just reply to this
> > > > request to feel a little embarrassed.
> > > >
> > > > Also haven't seen the proposed change to netcfg anytime in recent
> > > > past to comment further. Can that be reviewed?
> > >
> > > It's in branch people/womble/wpa of
> > > git://git.debian.org/git/d-i/netcfg.
> > >
> > > Gaudenz
> >
> > Thanks for the link.
>
> Do you have time to look at the code in the next days? Otherwise I'll
> probably just merge as it is now and we can fix things later if there
> are problems.
Do not wait for any activity from me, I'm currently not very active with
Debian work - mostly keeping up with basic maintenace related tasks.
Not familiar with netcfg or the debian-installer environment at all yet.
>
> I have another yet unresolved problem: With the proposed udeb
> configuration from the original patch and using the netlink driver I can
> connect to the network, but DHCP does not work. When I build a udeb with
> the same
> configuration as for the normal linux package minus DBUS and smartcard
> support it works. Do you know which options I need to include to get a
> package where DHCP also works with the netlink driver?
From the top of my head I do not know why you observe this difference in
behaviour. Where WEXT works, nl80211 should work and vice versa.
Thanks, Kel.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201107262314.11491@otaku42.de
Re: Bug#610931: Please build wpasupplicant-udeb
Hi
So I actually made some progress today. Here's my status report.
Excerpts from Kel Modderman's message of 2011-07-24 00:58:08 +0200:
> On Sun, 24 Jul 2011 08:02:48 AM Gaudenz Steinlin wrote:
> > >
> > > nl80211 is the way forward. It would require libnl to be included in D-I.
> >
> > AFAICS with my iwlwifi card both nl80211 and wext work. Is there any
> > practical advantage of nl80211. If possible I would like to avoid
> > having to include another library into d-i.
>
> WEXT is deprecated upstream, nl80211 is in active development and all new
> wifi
> drivers will use it. Looking into my crystal ball I see that eventually the
> WEXT compat layer will decay into something that nobody wants to keep
> maintaining.
>
> If D-I integration of wpasupplicant were to go ahead without including
> support
> for nl80211 it would be a waste of time imo.
After discussing this on IRC we (debian-boot) agreed to include wext
and nl80211 support.
> > > > > Has there been any solution for the netcfg integration already, see
> > > > > <201011041811.11753@otaku42.de> [1], referring to the originally
> > > > > proposed introduction of embedded source copies of wpasuppliant's
> > > > > wpa_ctrl.[hc] into netcfg. Please also keep in mind that crda/
> > > > > wireless-regdb is required for accessing channels 11-13/14 on modern
> > > > > drivers.
> > > >
> > > > I've applied the existing WPA netcfg support patches developed by Glenn
> > > > Saberton, and they do appear to include a (stripped down) wpa_ctrl.c.
> > >
> > > That stripped down crap probably was extracted from a sideline project
> > > (python-wpactrl) I was working on, and is not good long term solution.
> > >
> > > wpa_ctrl.{c,h} from current wpasupplicant source tree have lots more
> > > dependency on other stuff. Extracting and patching wpa_ctrl.{c,h} to be
> > > standalone is something which should be avoided - I just do not know how
> > > currently.
> > >
> > > Asked upstream wpa_supplicant if wpa_ctrl could be provided in a way
> > > where it could be a shared library but received no response.
> >
> > Is there any progress on this?
>
> Nope.
Do you think it's worth poking about this again? The current code in
netcfg works (at least for the debconf wpa-psk network), but a real
library would be nicer ;-).
>
> >
> > > > I
> > > > have no idea what the story is with crda/wireless-regdb, as I said
> > > > before, I don't know anything about WPA. If you'd like to help out,
> > > > though, your knowledge would be greatly valued.
> > >
> > > I wouldn't mind helping out, don't know how though, Have little idea
> > > about D-I environment and took long enough to just reply to this request
> > > to feel a little embarrassed.
> > >
> > > Also haven't seen the proposed change to netcfg anytime in recent past to
> > > comment further. Can that be reviewed?
> >
> > It's in branch people/womble/wpa of
> > git://git.debian.org/git/d-i/netcfg.
> >
> > Gaudenz
>
> Thanks for the link.
Do you have time to look at the code in the next days? Otherwise I'll
probably just merge as it is now and we can fix things later if there
are problems.
I have another yet unresolved problem: With the proposed udeb
configuration from the original patch and using the netlink driver I can
connect to the network,
but DHCP does not work. When I build a udeb with the same
configuration as for the normal linux package minus DBUS and smartcard
support it works. Do you know which options I need to include to get a
package where DHCP also works with the netlink driver?
Using the wext driver DHCP works in both configurations.
This is the configuration I currently use to produce the working
package:
# Debian's wpa_supplicant build time configuration
CONFIG_DRIVER_WEXT=y
CONFIG_DRIVER_NL80211=y
CONFIG_DRIVER_WIRED=y
CONFIG_AP=y
CONFIG_IEEE8021X_EAPOL=y
CONFIG_EAP_MD5=y
CONFIG_EAP_MSCHAPV2=y
CONFIG_EAP_TLS=y
CONFIG_EAP_PEAP=y
CONFIG_EAP_TTLS=y
CONFIG_EAP_GTC=y
CONFIG_EAP_OTP=y
CONFIG_EAP_SIM=y
#CONFIG_EAP_PSK=y
CONFIG_EAP_PAX=y
CONFIG_EAP_LEAP=y
CONFIG_EAP_AKA=y
CONFIG_EAP_AKA_PRIME=y
#CONFIG_USIM_SIMULATOR=y
CONFIG_WPS=y
#CONFIG_PKCS12=y
#CONFIG_SMARTCARD=y
#CONFIG_PCSC=y
CONFIG_CTRL_IFACE=y
CONFIG_READLINE=y
CONFIG_BACKEND=file
CONFIG_MAIN=main
CONFIG_OS=unix
CONFIG_ELOOP=eloop
CONFIG_L2_PACKET=linux
CONFIG_PEERKEY=y
CONFIG_IEEE80211W=y
CONFIG_TLS=openssl
#CONFIG_CTRL_IFACE_DBUS=y
#CONFIG_CTRL_IFACE_DBUS_NEW=y
#CONFIG_CTRL_IFACE_DBUS_INTRO=y
CONFIG_IEEE80211R=y
CONFIG_DEBUG_FILE=y
CONFIG_DEBUG_SYSLOG=y
#CONFIG_PRIVSEP=y
CONFIG_DELAYED_MIC_ERROR_REPORT=y
This is the configuration where DHCP does not work when using the
netlink driver:
# Debian Installer's wpa_supplicant build time configuration
CONFIG_DRIVER_WEXT=y
CONFIG_DRIVER_NL80211=y
CONFIG_BACKEND=file
#CONFIG_NO_STDOUT_DEBUG=y
CONFIG_DEBUG_FILE=y
CONFIG_NO_AES_EXTRAS=y
#CONFIG_NO_CONFIG_WRITE=y
CONFIG_NO_CONFIG_BLOBS=y
CONFIG_MAIN=main
CONFIG_OS=unix
CONFIG_ELOOP=eloop
CONFIG_L2_PACKET=linux
CONFIG_CTRL_IFACE=y
Re: Bug#610931: Please build wpasupplicant-udeb
On Sun, 24 Jul 2011 08:02:48 AM Gaudenz Steinlin wrote:
> Hi
>
> I'm picking up the task to integrate WPA support into
> debian-installer. My goal is to have this finished by the end of
> Debconf. Is anyone of you also going to attend Debconf?
Nope.
> >
> > nl80211 is the way forward. It would require libnl to be included in D-I.
>
> AFAICS with my iwlwifi card both nl80211 and wext work. Is there any
> practical advantage of nl80211. If possible I would like to avoid
> having to include another library into d-i.
WEXT is deprecated upstream, nl80211 is in active development and all new wifi
drivers will use it. Looking into my crystal ball I see that eventually the
WEXT compat layer will decay into something that nobody wants to keep
maintaining.
If D-I integration of wpasupplicant were to go ahead without including support
for nl80211 it would be a waste of time imo.
>
> > > > diff -urN wpasupplicant-0.6.10.orig/debian/control
> > > > wpasupplicant-0.6.10/debian/control [...]
> > > > +Architecture: linux-any
> > > >
> > > > wpasupplicant is needed, and compatible with-, kFreeBSD as well, at
> > > > this moment kFreeBSD doesn't support wlan for unrelated reasons
> > > > (ifconfig not being able to configure wlan interfaces, besides the
> > > > open firmware issues, while firmwares are required for most
> > > > chipsets). So ignoring hurd, it should be "any" or at least
> > > > "linux-any kfreebsd-any".
> > >
> > > Wireless config is disabled in d-i for kfreebsd, so there's no reason
> > > to build wpasupplicant-udeb for those arches. However, if you're
> > > comfortable that a wpasupplicant-udeb will build correctly for those
> > > arches, it'd save changes down the line if/when kfreebsd gets d-i
> > > wireless support.
> >
> > It'd probably be better to prepare early here and build
> > wpasupplicant-udeb for whatever it can build on.
>
> I don't care that much as it mainly concerns your package, but as
> kfreebsd does not currently have wireless support in d-i, the package
> won't be used for now. I don't know how much work it would be to
> enable wireless for kfreebsd in d-i, but that's a another task.
>
> I have another question:
> To connect to the debconf network I needed to additional kernel
> modules for the encryption algorithms: aes_generic.ko and
> aes-x86_64.ko. Are these the only crpyto modules required for WPA or
> are there configurations where other algorithms might be needed. Of
> course aes-x86_64 has to be replaced by the appropriate module on
> other architectures.
It's possible, I don't really know.
>
> > > > Has there been any solution for the netcfg integration already, see
> > > > <201011041811.11753@otaku42.de> [1], referring to the originally
> > > > proposed introduction of embedded source copies of wpasuppliant's
> > > > wpa_ctrl.[hc] into netcfg. Please also keep in mind that crda/
> > > > wireless-regdb is required for accessing channels 11-13/14 on modern
> > > > drivers.
> > >
> > > I've applied the existing WPA netcfg support patches developed by Glenn
> > > Saberton, and they do appear to include a (stripped down) wpa_ctrl.c.
> >
> > That stripped down crap probably was extracted from a sideline project
> > (python-wpactrl) I was working on, and is not good long term solution.
> >
> > wpa_ctrl.{c,h} from current wpasupplicant source tree have lots more
> > dependency on other stuff. Extracting and patching wpa_ctrl.{c,h} to be
> > standalone is something which should be avoided - I just do not know how
> > currently.
> >
> > Asked upstream wpa_supplicant if wpa_ctrl could be provided in a way
> > where it could be a shared library but received no response.
>
> Is there any progress on this?
Nope.
>
> > > I
> > > have no idea what the story is with crda/wireless-regdb, as I said
> > > before, I don't know anything about WPA. If you'd like to help out,
> > > though, your knowledge would be greatly valued.
> >
> > I wouldn't mind helping out, don't know how though, Have little idea
> > about D-I environment and took long enough to just reply to this request
> > to feel a little embarrassed.
> >
> > Also haven't seen the proposed change to netcfg anytime in recent past to
> > comment further. Can that be reviewed?
>
> It's in branch people/womble/wpa of
> git://git.debian.org/git/d-i/netcfg.
>
> Gaudenz
Thanks for the link.
Kel.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201107240858.08353@otaku42.de
Re: Bug#610931: Please build wpasupplicant-udeb
Hi
I'm picking up the task to integrate WPA support into
debian-installer. My goal is to have this finished by the end of
Debconf. Is anyone of you also going to attend Debconf?
> On Tuesday 25 January 2011 04:39:44 Matthew Palmer wrote:
> > >
> > > diff -urN wpasupplicant-0.6.10.orig/debian/config/udeb
> > > wpasupplicant-0.6.10/debian/config/udeb
> > > [...]
> > > +CONFIG_DRIVER_WEXT=y
> > >
> > > Given that wext is deprecated, it would imho make more sense to use
> > > CONFIG_DRIVER_NL80211=y instead, maybe even to leave wext disabled.
> > > With the notable exception of ipw2100/ ipw2200, all other linux wlan
> > > drivers weren't produced in large volumes or don't support wpa2 to
> > > begin with; for new ones (this covers all mac80211 based ones) nl80211
> > > support is mandatory and there are some initial efforts to add nl80211
> > > to ipw2x00. This also avoids the need for deprecated wireless-tools in
> > > favour of iw/ crda (which is required for ch11-14 anyways) - or being
> > > able to use libnl for all configuration in netcfg.
> >
> > I know nothing about WPA, I've just used a udeb config file that was in an
> > existing (out of date) patch to build a wpasupplicant udeb. In all honesty
> > you can set this configuration to whatever you think is best.
> nl80211 is the way forward. It would require libnl to be included in D-I.
AFAICS with my iwlwifi card both nl80211 and wext work. Is there any
practical advantage of nl80211. If possible I would like to avoid
having to include another library into d-i.
> >
> > > diff -urN wpasupplicant-0.6.10.orig/debian/control
> > > wpasupplicant-0.6.10/debian/control
> > > [...]
> > > +Architecture: linux-any
> > >
> > > wpasupplicant is needed, and compatible with-, kFreeBSD as well, at
> > > this moment kFreeBSD doesn't support wlan for unrelated reasons
> > > (ifconfig not being able to configure wlan interfaces, besides the open
> > > firmware issues, while firmwares are required for most chipsets). So
> > > ignoring hurd, it should be "any" or at least "linux-any kfreebsd-any".
> >
> > Wireless config is disabled in d-i for kfreebsd, so there's no reason to
> > build wpasupplicant-udeb for those arches. However, if you're comfortable
> > that a wpasupplicant-udeb will build correctly for those arches, it'd save
> > changes down the line if/when kfreebsd gets d-i wireless support.
> It'd probably be better to prepare early here and build wpasupplicant-udeb for
> whatever it can build on.
I don't care that much as it mainly concerns your package, but as
kfreebsd does not currently have wireless support in d-i, the package
won't be used for now. I don't know how much work it would be to
enable wireless for kfreebsd in d-i, but that's a another task.
I have another question:
To connect to the debconf network I needed to additional kernel
modules for the encryption algorithms: aes_generic.ko and
aes-x86_64.ko. Are these the only crpyto modules required for WPA or
are there configurations where other algorithms might be needed. Of
course aes-x86_64 has to be replaced by the appropriate module on
other architectures.
> > > Has there been any solution for the netcfg integration already, see
> > > <201011041811.11753@otaku42.de> [1], referring to the originally
> > > proposed introduction of embedded source copies of wpasuppliant's
> > > wpa_ctrl.[hc] into netcfg. Please also keep in mind that crda/
> > > wireless-regdb is required for accessing channels 11-13/14 on modern
> > > drivers.
> >
> > I've applied the existing WPA netcfg support patches developed by Glenn
> > Saberton, and they do appear to include a (stripped down) wpa_ctrl.c.
> That stripped down crap probably was extracted from a sideline project
> (python-wpactrl) I was working on, and is not good long term solution.
> wpa_ctrl.{c,h} from current wpasupplicant source tree have lots more
> dependency
> on other stuff. Extracting and patching wpa_ctrl.{c,h} to be standalone is
> something which should be avoided - I just do not know how currently.
> Asked upstream wpa_supplicant if wpa_ctrl could be provided in a way where it
> could be a shared library but received no response.
Is there any progress on this?
> > I
> > have no idea what the story is with crda/wireless-regdb, as I said before, I
> > don't know anything about WPA. If you'd like to help out, though, your
> > knowledge would be greatly valued.
> I wouldn't mind h
Re: wpasupplicant udeb
On Wednesday 28 May 2008 20:59:15 Frans Pop wrote:
> Note: please do not upload yet.
> One thing I'm not yet certain of is what priority the udeb should have and
> how it should be loaded. This will need some discussion.
Just for completeness, I have adapted the patch to allow possibility for
kfreebsd udeb to be possible should it ever be needed.
Thanks, Kel.
---
--- a/debian/control
+++ b/debian/control
@@ -38,3 +38,16 @@
to connect to. It also provides a method for browsing 802.11 SSID scan
results, an event history log of messages generated by wpa_supplicant,
and a method to add or edit wpa_supplicant networks.
+
+Package: wpasupplicant-udeb
+Section: debian-installer
+Architecture: any
+XC-Package-Type: udeb
+Depends: ${shlibs:Depends}
+Description: Client support for WPA and WPA2 (IEEE 802.11i)
+ WPA and WPA2 are methods for securing wireless networks, the former
+ using IEEE 802.1X, and the latter using IEEE 802.11i. This software
+ provides key negotiation with the WPA Authenticator, and controls
+ association with IEEE 802.11i networks.
+ .
+ This is a udeb of wpasupplicant for use by the Debian installer.
--- a/debian/rules
+++ b/debian/rules
@@ -9,6 +9,7 @@
WPAGUI=wpa_gui-qt4
CFLAGS = -Wall -g
+UDEB_CFLAGS = -Wall -g -Os
LDFLAGS = -Wl,--as-needed
ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
@@ -21,8 +22,10 @@
ifeq ($(DEB_HOST_ARCH_OS),kfreebsd)
CONFIG := debian/config/kfreebsd
+ CONFIG_UDEB := debian/config/kfreebsd.udeb
else
CONFIG := debian/config/linux
+ CONFIG_UDEB := debian/config/linux.udeb
endif
@@ -62,6 +65,13 @@
dh_testroot
dh_clean -k
dh_installdirs
+ dh_install
+
+ # udeb for debian installer
+ $(MAKE) -C wpa_supplicant clean; $(RM) wpa_supplicant/.config
+ cp -v $(CONFIG_UDEB) wpa_supplicant/.config
+ CFLAGS="$(UDEB_CFLAGS)" $(MAKE) -C wpa_supplicant wpa_supplicant
+ dh_install -pwpasupplicant-udeb wpa_supplicant/wpa_supplicant sbin/
# ifupdown
install --mode=755 -D debian/ifupdown/ifupdown.sh \
@@ -94,7 +104,6 @@
dh_installchangelogs wpa_supplicant/ChangeLog
dh_installdocs
dh_installexamples
- dh_install
dh_installlogrotate --package=wpasupplicant --name=wpa_action
dh_installlogrotate --package=wpasupplicant --name=wpa_supplicant
dh_installinit --package=wpasupplicant --name=wpa-ifupdown --no-start
-- start 15 0 6 .
--- /dev/null
+++ b/debian/config/kfreebsd.udeb
@@ -0,0 +1,13 @@
+# Debian Installer's wpa_supplicant build time configuration
+CONFIG_DRIVER_BSD=y
+LIBS += -lbsd
+CONFIG_BACKEND=file
+#CONFIG_NO_STDOUT_DEBUG=y
+CONFIG_DEBUG_FILE=y
+CONFIG_NO_AES_EXTRAS=y
+CONFIG_NO_CONFIG_WRITE=y
+CONFIG_NO_CONFIG_BLOBS=y
+CONFIG_MAIN=main
+CONFIG_OS=unix
+CONFIG_ELOOP=eloop
+CONFIG_L2_PACKET=freebsd
--- /dev/null
+++ b/debian/config/linux.udeb
@@ -0,0 +1,12 @@
+# Debian Installer's wpa_supplicant build time configuration
+CONFIG_DRIVER_WEXT=y
+CONFIG_BACKEND=file
+#CONFIG_NO_STDOUT_DEBUG=y
+CONFIG_DEBUG_FILE=y
+CONFIG_NO_AES_EXTRAS=y
+CONFIG_NO_CONFIG_WRITE=y
+CONFIG_NO_CONFIG_BLOBS=y
+CONFIG_MAIN=main
+CONFIG_OS=unix
+CONFIG_ELOOP=eloop
+CONFIG_L2_PACKET=linux
---
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wpasupplicant udeb
On Wednesday 28 May 2008 20:59:15 Frans Pop wrote: > On Monday 26 May 2008, Kel Modderman wrote: > > Trying to associate with 00:13:10:41:7e:1f (SSID='kelnet' freq=2412 MHz) > > Associated with 00:13:10:41:7e:1f > > WPA: Key negotiation completed with 00:13:10:41:7e:1f [PTK=TKIP GTK=TKIP] > > CTRL-EVENT-CONNECTED - Connection to 00:13:10:41:7e:1f completed (auth) > > [id=6 id_str=kelnet] > > OK. These definitely look useful to have. Yep. Especially if the pkg-wpa maintainers are responsible for answering to failure reports from wpa_supplicant in debian installer environment, this is the kind of information that will be needed for any clue. > > > The debugging may not be useful per default, but it could just be worth > > keeping so that there is an attack vector for people reporting problems > > about using a wpa enabled netcfg, so that they be able to manually invoke > > wpa_supplicant on another terminal to capture output for analysis (eg. to > > find out why association to desired access point failed). It just depends > > if this need is valid and able to offset the desire for very small binary > > size. > > It would be really great if we could keep the standard messages, but drop > the lower level ones. But I guess that would require an upstream change. > Any chance of that do you think? I doubt that. At least not in this upstream development cycle. Not sure how sane it would be to do that either, but it cannot hurt for me to ask if it would be a consideration in the future. > > IMO the size of the udeb is quite reasonable already. Reducing it further > would be nice, but is not a hard requirement for implementing WPA support > for default installations. > > Note: please do not upload yet. > One thing I'm not yet certain of is what priority the udeb should have and > how it should be loaded. This will need some discussion. No problems. Thanks for the comments. Thanks, Kel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wpasupplicant udeb
On Monday 26 May 2008, Kel Modderman wrote: > Trying to associate with 00:13:10:41:7e:1f (SSID='kelnet' freq=2412 MHz) > Associated with 00:13:10:41:7e:1f > WPA: Key negotiation completed with 00:13:10:41:7e:1f [PTK=TKIP GTK=TKIP] > CTRL-EVENT-CONNECTED - Connection to 00:13:10:41:7e:1f completed (auth) > [id=6 id_str=kelnet] OK. These definitely look useful to have. > The debugging may not be useful per default, but it could just be worth > keeping so that there is an attack vector for people reporting problems > about using a wpa enabled netcfg, so that they be able to manually invoke > wpa_supplicant on another terminal to capture output for analysis (eg. to > find out why association to desired access point failed). It just depends > if this need is valid and able to offset the desire for very small binary > size. It would be really great if we could keep the standard messages, but drop the lower level ones. But I guess that would require an upstream change. Any chance of that do you think? IMO the size of the udeb is quite reasonable already. Reducing it further would be nice, but is not a hard requirement for implementing WPA support for default installations. Note: please do not upload yet. One thing I'm not yet certain of is what priority the udeb should have and how it should be loaded. This will need some discussion. Cheers, FJP signature.asc Description: This is a digitally signed message part.
Re: wpasupplicant udeb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Frans Pop wrote: > On Sunday 25 May 2008, Stefano Canepa wrote: >> why did you comment out the madwifi driver? >> # Driver interface for madwifi driver >> -CONFIG_DRIVER_MADWIFI=y >> +#CONFIG_DRIVER_MADWIFI=y >> # Change include directories to match with the local setup >> -CFLAGS += -I../debian/madwifi-headers >> +#CFLAGS += -I../debian/madwifi-headers >> >> IIRC eeePC installer needs madwifi. > > No, it needs the replacement of madwifi, which is ath5k. madwifi is a > non-free out-of-tree driver which we cannot support in D-I anyway. > > Cheers, > FJP Beside that, madwifi actually uses wext. The old madwifi backend hasn't been recommended for a long time, and afaik is still there because of ubuntu. Cheers Glenn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIOgUuV8GyuTwyskMRArX/AJ932TotAsPzXgsQ41kvKy2P0hZcPwCfeuvQ N/MnGDPewusvuBu9sY246Js= =H/d1 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wpasupplicant udeb
On Sunday 25 May 2008, Stefano Canepa wrote: > why did you comment out the madwifi driver? > # Driver interface for madwifi driver > -CONFIG_DRIVER_MADWIFI=y > +#CONFIG_DRIVER_MADWIFI=y > # Change include directories to match with the local setup > -CFLAGS += -I../debian/madwifi-headers > +#CFLAGS += -I../debian/madwifi-headers > > IIRC eeePC installer needs madwifi. No, it needs the replacement of madwifi, which is ath5k. madwifi is a non-free out-of-tree driver which we cannot support in D-I anyway. Cheers, FJP signature.asc Description: This is a digitally signed message part.
Re: wpasupplicant udeb
Il giorno ven, 23/05/2008 alle 16.09 +0800, Glenn ha scritto: > Ok, here it is. Its based on debians svn release of wpasupplicant as it > has a patch which allows us to build without EAP. It will still build > the deb and clients at the moment, which as stated earlier, some sort of > seperate config needs to be made for the udeb. Glenn, why did you comment out the madwifi driver? # Driver interface for madwifi driver -CONFIG_DRIVER_MADWIFI=y +#CONFIG_DRIVER_MADWIFI=y # Change include directories to match with the local setup -CFLAGS += -I../debian/madwifi-headers +#CFLAGS += -I../debian/madwifi-headers IIRC eeePC installer needs madwifi. Bye Stefano -- Stefano Canepa aka sc: [EMAIL PROTECTED] - http://www.stefanocanepa.it Three great virtues of a programmer: laziness, impatience and hubris. Le tre grandi virtù di un programmatore: pigrizia, impazienza e arroganza. (Larry Wall) signature.asc Description: Questa è una parte del messaggio firmata digitalmente
Re: wpasupplicant udeb
On Monday 26 May 2008 00:32:39 Glenn Saberton wrote:
> Jérémy Bobbio wrote:
> > On Fri, May 23, 2008 at 04:09:48PM +0800, Glenn wrote:
> >> It will still build the deb and clients at the moment, which as stated
> >> earlier, some sort of seperate config needs to be made for the udeb.
> >
> > If you can provide a patch doing so for review, it would be great.
> >
> > You might want to have a look at busybox which also use a "config" file
> > for its build system and have several different configuration for its
> > binary packages.
> >
> > Cheers,
> After talking with one of the wpasupplicant maintainers, he has kindly
> agreed to help get an acceptable patch for a wpasupplicant udeb.
> CC'ing him in on this thread. Hopefully we should have a patch
> together in the next few days.
Attached is an initial patch against current state of wpasupplicant package
in version control. Glenn and I haven't nailed down the exact build
configuration of wpa_supplicant that will be used, but we'd really like some
feedback about the packaging changes at this time.
Also, do you think compiling in support for debug messages about association
is something that would be useful to have in the debian-installer environment
for occasions when manual troubleshooting is required? A fair amount of binary
size can be shaved off without it, but unsure if that is wise.
Thanks, Kel.
---
--- a/debian/control
+++ b/debian/control
@@ -38,3 +38,16 @@
to connect to. It also provides a method for browsing 802.11 SSID scan
results, an event history log of messages generated by wpa_supplicant,
and a method to add or edit wpa_supplicant networks.
+
+Package: wpasupplicant-udeb
+Section: debian-installer
+Architecture: any
+XC-Package-Type: udeb
+Depends: ${shlibs:Depends}, dhcp-client-udeb | dhcp3-client-udeb | pump-udeb,
ethernet-card-detection
+Description: Client support for WPA and WPA2 (IEEE 802.11i)
+ WPA and WPA2 are methods for securing wireless networks, the former
+ using IEEE 802.1X, and the latter using IEEE 802.11i. This software
+ provides key negotiation with the WPA Authenticator, and controls
+ association with IEEE 802.11i networks.
+ .
+ This is a udeb of wpasupplicant for use by the Debian installer.
--- /dev/null
+++ b/debian/config/udeb
@@ -0,0 +1,12 @@
+# Debian Installer's wpa_supplicant build time configuration
+CONFIG_DRIVER_WEXT=y
+CONFIG_BACKEND=file
+#CONFIG_NO_STDOUT_DEBUG=y
+CONFIG_DEBUG_FILE=y
+CONFIG_NO_AES_EXTRAS=y
+CONFIG_NO_CONFIG_WRITE=y
+CONFIG_NO_CONFIG_BLOBS=y
+CONFIG_MAIN=main
+CONFIG_OS=unix
+CONFIG_ELOOP=eloop
+CONFIG_L2_PACKET=linux
--- a/debian/rules
+++ b/debian/rules
@@ -9,6 +9,7 @@
WPAGUI=wpa_gui-qt4
CFLAGS = -Wall -g
+UDEB_CFLAGS = -Wall -g -Os
LDFLAGS = -Wl,--as-needed
ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
@@ -62,6 +63,13 @@
dh_testroot
dh_clean -k
dh_installdirs
+ dh_install
+
+ # udeb for debian installer
+ $(MAKE) -C wpa_supplicant clean; $(RM) wpa_supplicant/.config
+ cp -v debian/config/udeb wpa_supplicant/.config
+ CFLAGS="$(UDEB_CFLAGS)" $(MAKE) -C wpa_supplicant wpa_supplicant
+ dh_install -pwpasupplicant-udeb wpa_supplicant/wpa_supplicant sbin/
# ifupdown
install --mode=755 -D debian/ifupdown/ifupdown.sh \
@@ -94,7 +102,6 @@
dh_installchangelogs wpa_supplicant/ChangeLog
dh_installdocs
dh_installexamples
- dh_install
dh_installlogrotate --package=wpasupplicant --name=wpa_action
dh_installlogrotate --package=wpasupplicant --name=wpa_supplicant
dh_installinit --package=wpasupplicant --name=wpa-ifupdown --no-start
-- start 15 0 6 .
---
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wpasupplicant udeb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jérémy Bobbio wrote: > On Fri, May 23, 2008 at 04:09:48PM +0800, Glenn wrote: >> It will still build the deb and clients at the moment, which as stated >> earlier, some sort of seperate config needs to be made for the udeb. > > If you can provide a patch doing so for review, it would be great. > > You might want to have a look at busybox which also use a "config" file > for its build system and have several different configuration for its > binary packages. > > Cheers, After talking with one of the wpasupplicant maintainers, he has kindly agreed to help get an acceptable patch for a wpasupplicant udeb. CC'ing him in on this thread. Hopefully we should have a patch together in the next few days. Cheers Glenn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIOXiHV8GyuTwyskMRAkb2AJ9gqJWThe5sSnDipCPCoYrRhQe+1QCfVIJQ EDil13798f36mwRUrcc57XI= =tK38 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wpasupplicant udeb
Jérémy Bobbio wrote: > On Fri, May 23, 2008 at 04:09:48PM +0800, Glenn wrote: > >> It will still build the deb and clients at the moment, which as stated >> earlier, some sort of seperate config needs to be made for the udeb. >> > > If you can provide a patch doing so for review, it would be great. > > You might want to have a look at busybox which also use a "config" file > for its build system and have several different configuration for its > binary packages. > > Cheers, > I'll fire off an email to the wpasupplicant list before I start doing patches for the package. This patch was meant just for testing purposes, which is what I thought Frans wanted. I'll get back with any questions or concerns that may arise from this. Cheers Glenn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: wpasupplicant udeb
On Fri, May 23, 2008 at 04:09:48PM +0800, Glenn wrote: > It will still build the deb and clients at the moment, which as stated > earlier, some sort of seperate config needs to be made for the udeb. If you can provide a patch doing so for review, it would be great. You might want to have a look at busybox which also use a "config" file for its build system and have several different configuration for its binary packages. Cheers, -- Jérémy Bobbio.''`. [EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Re: wpasupplicant udeb
Ok, here it is. Its based on debians svn release of wpasupplicant as it
has a patch which allows us to build without EAP. It will still build
the deb and clients at the moment, which as stated earlier, some sort of
seperate config needs to be made for the udeb.
Please CC me.
Cheers
Glenn
diff --git a/wpasupplicant/trunk/debian/config b/wpasupplicant/trunk/debian/config
index 54faf60..1029dc6 100644
--- a/wpasupplicant/trunk/debian/config
+++ b/wpasupplicant/trunk/debian/config
@@ -11,9 +11,9 @@ CONFIG_DRIVER_HOSTAP=y
#CFLAGS += -I../../include/wireless
# Driver interface for madwifi driver
-CONFIG_DRIVER_MADWIFI=y
+#CONFIG_DRIVER_MADWIFI=y
# Change include directories to match with the local setup
-CFLAGS += -I../debian/madwifi-headers
+#CFLAGS += -I../debian/madwifi-headers
# Driver interface for Prism54 driver
# (Note: Prism54 is not yet supported, i.e., this will not work as-is and is
@@ -68,29 +68,29 @@ CONFIG_DRIVER_WEXT=y
# CONFIG_USE_NDISUIO=y
# Driver interface for development testing
-CONFIG_DRIVER_TEST=y
+#CONFIG_DRIVER_TEST=y
# Driver interface for wired Ethernet drivers
-CONFIG_DRIVER_WIRED=y
+#CONFIG_DRIVER_WIRED=y
# Enable IEEE 802.1X Supplicant (automatically included if any EAP method is
# included)
-CONFIG_IEEE8021X_EAPOL=y
+#CONFIG_IEEE8021X_EAPOL=y
# EAP-MD5
-CONFIG_EAP_MD5=y
+#CONFIG_EAP_MD5=y
# EAP-MSCHAPv2
CONFIG_EAP_MSCHAPV2=y
# EAP-TLS
-CONFIG_EAP_TLS=y
+#CONFIG_EAP_TLS=y
# EAL-PEAP
-CONFIG_EAP_PEAP=y
+#CONFIG_EAP_PEAP=y
# EAP-TTLS
-CONFIG_EAP_TTLS=y
+#CONFIG_EAP_TTLS=y
# EAP-FAST
# Note: Default OpenSSL package does not include support for all the
@@ -100,25 +100,25 @@ CONFIG_EAP_TTLS=y
#CONFIG_EAP_FAST=y
# EAP-GTC
-CONFIG_EAP_GTC=y
+#CONFIG_EAP_GTC=y
# EAP-OTP
-CONFIG_EAP_OTP=y
+#CONFIG_EAP_OTP=y
# EAP-SIM (enable CONFIG_PCSC, if EAP-SIM is used)
-CONFIG_EAP_SIM=y
+#CONFIG_EAP_SIM=y
# EAP-PSK (experimental; this is _not_ needed for WPA-PSK)
-CONFIG_EAP_PSK=y
+#CONFIG_EAP_PSK=y
# EAP-PAX
-CONFIG_EAP_PAX=y
+#CONFIG_EAP_PAX=y
# LEAP
-CONFIG_EAP_LEAP=y
+#CONFIG_EAP_LEAP=y
# EAP-AKA (enable CONFIG_PCSC, if EAP-AKA is used)
-CONFIG_EAP_AKA=y
+#CONFIG_EAP_AKA=y
# EAP-SAKE
#CONFIG_EAP_SAKE=y
@@ -132,22 +132,22 @@ CONFIG_EAP_AKA=y
#CONFIG_EAP_TNC=y
# EAP-WSC for Wi-Fi Protected Setup
-CONFIG_EAP_WSC=y
+#CONFIG_EAP_WSC=y
# EAP-IKEv2
#CONFIG_EAP_IKEV2=y
# PKCS#12 (PFX) support (used to read private key and certificate file from
# a file that usually has extension .p12 or .pfx)
-CONFIG_PKCS12=y
+#CONFIG_PKCS12=y
# Smartcard support (i.e., private key on a smartcard), e.g., with openssl
# engine.
-CONFIG_SMARTCARD=y
+#CONFIG_SMARTCARD=y
# PC/SC interface for smartcards (USIM, GSM SIM)
# Enable this if EAP-SIM or EAP-AKA is included
-CONFIG_PCSC=y
+#CONFIG_PCSC=y
# Development testing
#CONFIG_EAPOL_TEST=y
@@ -165,13 +165,13 @@ CONFIG_CTRL_IFACE=y
# When building a wpa_cli binary for distribution, please note that these
# libraries are licensed under GPL and as such, BSD license may not apply for
# the resulting binary.
-CONFIG_READLINE=y
+#CONFIG_READLINE=y
# Remove debugging code that is printing out debug message to stdout.
# This can be used to reduce the size of the wpa_supplicant considerably
# if debugging code is not needed. The size reduction can be around 35%
# (e.g., 90 kB).
-#CONFIG_NO_STDOUT_DEBUG=y
+CONFIG_NO_STDOUT_DEBUG=y
# Remove WPA support, e.g., for wired-only IEEE 802.1X supplicant, to save
# 35-50 kB in code size.
@@ -285,7 +285,7 @@ CONFIG_TLS=openssl
#PLATFORMSDKLIB="/opt/Program Files/Microsoft Platform SDK/Lib"
# Add support for DBus control interface
-CONFIG_CTRL_IFACE_DBUS=y
+#CONFIG_CTRL_IFACE_DBUS=y
# Add support for loading EAP methods dynamically as shared libraries.
# When this option is enabled, each EAP method can be either included
@@ -326,7 +326,7 @@ CONFIG_CTRL_IFACE_DBUS=y
CONFIG_IEEE80211R=y
# Add support for writing debug log to a file (/tmp/wpa_supplicant-log-#.txt)
-CONFIG_DEBUG_FILE=y
+#CONFIG_DEBUG_FILE=y
# Enable privilege separation (see README 'Privilege separation' for details)
#CONFIG_PRIVSEP=y
diff --git a/wpasupplicant/trunk/debian/control b/wpasupplicant/trunk/debian/control
index 44ca4d5..3a46f0b 100644
--- a/wpasupplicant/trunk/debian/control
+++ b/wpasupplicant/trunk/debian/control
@@ -38,3 +38,14 @@ Description: GUI for wpa_supplicant
to connect to. It also provides a method for browsing 802.11 SSID scan
results, an event history log of messages generated by wpa_supplicant,
and a method to add or edit wpa_supplicant networks.
+
+Package: wpasupplicant-udeb
+XC-Package-Type: udeb
+Provides: wpasupplicant
+Architecture: any
+Section: debian-installer
+Priority: standard
+Depends: ${shlibs:Depends}, ${misc:Depends}, dhcp-client-udeb | dhcp3-client-udeb | pump-udeb, ethernet-card-detection
+Description: WPAsupplicant daemon (experimental)
+
+
diff --git a/wpasupplicant/trunk/debian/files b/wpasup
Re: wpasupplicant udeb
On Thursday 22 May 2008 15:25:13 Glenn wrote: > I' after some advice as to how to submit a patch for > wpasuppliant-udeb. Looking at (for example) openssl, it has the udeb > stuff in the main package. With wpasupplicant, we need a separate conf > file so that we don't include unnecessary drivers, clients and EAP > code. I can supply a patch that will build the udeb for testing > purposes, but I suspect that this isn't what the d-i team wants so I > need some advice on how to move forward on this. I have managed to get > the udeb size down to 82K and the binary to 162K. Is this suitable to be > able to be included in the installer? Please CC me, as my mail server is > having connectivity issues, and this address isn't subscribed. That sounds pretty good. Please just mail the patch to the debian-boot list for review and discussion. We should discuss and finalize the patch here before it is filed against the source package. If we need to involve the wpasupplicant maintainer in that discussion, we could possibly file the bug now, but then with an explicit note that it should not be implemented and uploaded before it has been finalized. Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
wpasupplicant udeb
Hello, I' after some advice as to how to submit a patch for wpasuppliant-udeb. Looking at (for example) openssl, it has the udeb stuff in the main package. With wpasupplicant, we need a separate conf file so that we don't include unnecessary drivers, clients and EAP code. I can supply a patch that will build the udeb for testing purposes, but I suspect that this isn't what the d-i team wants so I need some advice on how to move forward on this. I have managed to get the udeb size down to 82K and the binary to 162K. Is this suitable to be able to be included in the installer? Please CC me, as my mail server is having connectivity issues, and this address isn't subscribed. Cheers Glenn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
