Boot-Options and WIreless

[HappyFragga]

Hy

I am trying the actuall Version 11.2 on a Zotac ZBOX-ID41.
DHCP via Ethernet works fine, customized Webadress is loade in
Iceweasel, like it should.
Problem 1: The boot-parameters 'webcchrome=noaddress' seems to be
ignored. Iceweasel opens as Fullscreen like it should via
'webcchrome=fullscreen' but there i can still the Adress-bar and the
Search-bar.

Problem 2: I am unable to get Wireless Lan working correctly. The Wlan-
Connection doesnt even get startet. We manually edited 'etc/networking/
interfaces' by adding "wlan0" to the line 'auto lo'
After a "sudo /etc/init.d/networking restart" we finally saw equests
from the WLAN-Mac-ID

But there were still some Errors like:

> wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
> run-parts: /etc/network/if-up.d/ping No such file or directory
> wpa_supplicant: cannot read contents of /etc/wpa_supplicant/wpa_supplicant.conf
> run-parts: /etc/network/if-up.d/wpa_supplicant exited with return code 1

The Error meaning ping is probably unimportent, the other errors on
the other Hand could be some part of the Problem.

Any Ideas how i could fix the Problem and get wireless working?

Thanks for your effort

Sincerely

Chris

[Kai Hendry]

On 20 February 2012 22:38, HappyFragga <happy....@gmail.com> wrote:
> I am trying the actuall Version 11.2 on a Zotac ZBOX-ID41.
> DHCP via Ethernet works fine, customized Webadress is loade in
> Iceweasel, like it should.
> Problem 1: The boot-parameters 'webcchrome=noaddress' seems to be
> ignored. Iceweasel opens as Fullscreen like it should via
> 'webcchrome=fullscreen' but there i can still the Adress-bar and the
> Search-bar.

https://github.com/Webconverger/iceweasel-webconverger (and their
individual XPIs) are in good shape, but these boot option shortcuts
aren't. :/

I will try fix them for next release.

> Any Ideas how i could fix the Problem and get wireless working?

What type of network is it? WEP or WPA?

[HappyFragga]

On Feb 20, 5:36 pm, Kai Hendry <hen...@webconverger.com> wrote:

> What type of network is it? WEP or WPA?

It is a WPA-Protected Wireless Network

[Matteo Fracassetti]

We had the same problems with version 11.0 on the Asus EeeBox and on
Zotac ID12 yet: Using the free/trial versione we were unable to set
the webcchrome and to get the wireless network working.


Since we had neither the time nor the knowledge to do all the test
case, we purchased a custom image and now we have the webcchrome
working properly but still can not operate the wireless network: In
our case, we have wireless networks with WEP protection (tested with
hidden or broadcast essid with the same results).

Instead, if we boot the distro in debug mode, add "wlan0" to "/etc/
network/interfaces => Allow hotplug" and configuring the wlan0 with
iwconfig, we can get the DHCP lease so probably we are doing something
wrong with the boot options but I can not understand what.

Sorry for my bad English ...

[Kai Hendry]

On 20 February 2012 22:38, HappyFragga <happy....@gmail.com> wrote:

> I am trying the actuall Version 11.2 on a Zotac ZBOX-ID41.
> DHCP via Ethernet works fine, customized Webadress is loade in
> Iceweasel, like it should.
> Problem 1: The boot-parameters 'webcchrome=noaddress' seems to be
> ignored. Iceweasel opens as Fullscreen like it should via
> 'webcchrome=fullscreen' but there i can still the Adress-bar and the
> Search-bar.

Not able to reproduce this problem with 'webcchrome=noaddress' on the
latest builds: http://build.webconverger.org/latest.iso

There is a general problem with
https://github.com/Webconverger/Debian-Live-config/blob/master/webconverger/config/includes.chroot/home/webc/iwchromeconfig.sh
that it doesn't match the awesome-ness in
https://github.com/Webconverger/iceweasel-webconverger/tree/master/src

I need to figure out a way of handling this or just getting rid of
this hack altogether.

WRT to Wireless. There is a problem and I'm debugging it. :( Do you
notice a looping CRDA issue on my system. Do you see it too?

Kind regards,

[Kai Hendry]

Thanks Matteo for writing in,

On 21 February 2012 08:45, Matteo Fracassetti

<matteo.fr...@gmail.com> wrote:
>  Instead, if we boot the distro in debug mode, add "wlan0" to "/etc/
> network/interfaces => Allow hotplug" and configuring the wlan0 with
> iwconfig, we can get the DHCP lease so probably we are doing something
> wrong with the boot options but I can not understand what.

Spent a few hours today going through the WPA stuff and it all seems
to work with build.webconverger.org/latest.iso

If you are are going to debug and fiddle with /etc/network/interfaces,
have a look at http://lists.debian.org/debian-user/2010/02/msg01851.html

For added stability I do recommend you go wired for deployments.

Kind regards,

[Matteo Fracassetti]

Hi, Kai.

On 21 Feb, 07:55, Kai Hendry <hen...@webconverger.com> wrote:
> Thanks Matteo for writing in,

> Spent a few hours today going through the WPA stuff and it all seems
> to work with build.webconverger.org/latest.iso

I think to have found where the problem is: We are using WEP protected
networks, not WPA.
I modified the /etc/network/interfaces inside the squashfs filesystem
to comment out these two lines:

# The wireless network interface
iface wlan0 inet dhcp
pre-up iptables-restore < /etc/iptables.conf
# wpa-driver wext
# wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

I believe that your init script webconverger properly configure the
interface wlan0 but if it need to use WEP instead of WPA, leave these
lines overwrite the settings coming from cmdline.
I think that move this directly in the init script (in wpa security
configuration) removing them from /etc/network/interfaces can solve
the issue.
Now with wep wlan our iso works fine, I'm going to test it with WPA.

>
> For added stability I do recommend you go wired for deployments.
>
> Kind regards,

Sure, but I can not exclude that somewhere I might need to have a full-
working wireless installation.

[Matteo Fracassetti]

P.S:

WEP key "must" be inserted as HEX format like:
wlan=DR.GIORGINI-WLAN-OSPITI,4722e5061706572696e6f3733,

Using ASCII version like:
wlan=DR.GIORGINI-WLAN-OSPITI,Dr.Paperino73,
don't work for us.

[Matteo Fracassetti]

I've modified the wlan0 section in /etc/network/interfaces like this:

# The wireless network interface
iface wlan0 inet dhcp
pre-up iptables-restore < /etc/iptables.conf

and your init script /etc/init.d/webconverger like this:

[...]
cat >> /etc/wpa_supplicant/wpa_supplicant.conf <<END
network={
ssid="$essid"
psk="$key"
}
END
cat >> /etc/network/interfaces<<END
wpa-driver wext
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
END

else
#echo No KEY set
iwconfig $iface key off
fi
[...]

This appear to work fine also with WEP or WPA protected wireless
network but I'll complete our test tomorrow.

[Kai Hendry]

Thanks again Matteo for writing in here with your valuable feedback,

On 21 February 2012 22:49, Matteo Fracassetti

<matteo.fr...@gmail.com> wrote:
> Using ASCII version like:
> wlan=DR.GIORGINI-WLAN-OSPITI,Dr.Paperino73,
> don't work for us.

https://github.com/Webconverger/Debian-Live-config/blob/master/webconverger/config/includes.chroot/etc/init.d/webconverger#L123

Could you please try:

wlan=DR.GIORGINI-WLAN-OSPITI,s:Dr.Paperino73

Maybe that will work....
http://manpages.debian.net/cgi-bin/man.cgi?query=iwconfig
"You can also enter the key as an ASCII string by using the s: prefix"

[ANDREW VENGLAR]

On Feb 20, 6:51 pm, Kai Hendry <hen...@webconverger.com> wrote:
> WRT to Wireless. There is a problem and I'm debugging it. :( Do you
> notice a looping CRDA issue on my system. Do you see it too?
>
> Kind regards,
>

>  11.5_webconverger.jpg
> 119KViewDownload

I am having trouble bringing up wireless, too. My cmdline is:
initrd=/live/initrd.img boot=live config homepage=######
hostname=kiosk wlan=PSD-MAC, nopersistent quickreboot nomodeset splash
username=webc vga=current quiet noroot lcales=UTF-8 BOOT_IMAGE=/live/
vmlinuz

With my setup the network it's supposed to connect to is hidden and is
unsecured. When I boot the system up /sbin/iwconfig shows that I have
wlan0 and the b43 module is loaded. Dmesg doesn't show any problems
loading the module so I assume it's loading correctly including the
firmware. This is on a custom build I made from a slightly older
version of webconverger (~first week of January). I am seeing this
behavior on other systems with different manufacturers of wireless
cards so I think it's the way the scripts are bringing up the wireless
interface that aren't working correctly.

[Kai Hendry]

On 24 February 2012 09:12, ANDREW VENGLAR <veng...@edtools.psd401.net> wrote:
> cards so I think it's the way the scripts are bringing up the wireless
> interface that aren't working correctly.

I tested a open unsecured AP case with a daily and it worked fine on a
Thinkpad X201.

I plan to re-factor the code out of
https://github.com/Webconverger/Debian-Live-config/blob/master/webconverger/config/includes.chroot/etc/init.d/webconverger

Though for now the scripts actually do work for me and my wireless hardware.

I encourage you to setup the network yourself in debug mode and try
figure out if there was an extra step the script didn't do for you.

Kind regards,

[Kai Hendry]

On 25 February 2012 10:39, Kai Hendry <hen...@webconverger.com> wrote:
> I tested a open unsecured AP case with a daily and it worked fine on a
> Thinkpad X201.

I take that back, it seems to DROP CARRIER after a few minutes once
coming up. Argh. :/

sudo iwconfig wlan0 essid $YOUR_UNSECURED_HIDDEN_ESSID # seems to get
it re-associated.

I think I need to re-look if wpa_supplicant is a better for this job.

[Matteo Fracassetti]

I'm having some trouble too.
I've done a lot of test in this days and I had a lot of problem to
bring up wireless network.
In debug mode, this cmd:

echo $(/bin/busybox httpd -d "${x//wlan=}")

always give back an empty value so configuration script can't work.
Manually configure wlan0 with the same AP and network setting always
works fine. So, it appears as a problem parsing boot options but I'm
very noob so take it carefully...

[Kai Hendry]

I don't think the problem is in parsing the wlan= line.

I'll be working on a new wireless API tomorrow, that should solve the
problem with open non-wpasupplicant managed connections.

[Matteo Fracassetti]

I think to have solved our problem with wireless network using
webconverger 11.0 with a modified script.
Still having problem with webconverger 11.2: Using wireless I can't
get network access. Ethernet works fine.

Bye.

[Kai Hendry]

Hi Matteo,

In the last couple of days we've come up with a new re-factored method
for setting up wireless.

Could you please test it on your configuration by using the dailies
and the "New method" section on http://webconverger.org/wireless/

Any problems, please file them on
https://github.com/Webconverger/Debian-Live-config/issues so we can
easily track them.

Thank you for your patience,

[Guttorm Flatabø]

On Wed, Feb 29, 2012 at 9:55 AM, Kai Hendry <hen...@webconverger.com> wrote:

In the last couple of days we've come up with a new re-factored method
for setting up wireless.

Could you please test it on your configuration by using the dailies
and the "New method" section on http://webconverger.org/wireless/

One problem that I foresee with the new method (only from reading the new instructions) is that you seemingly have to know whether your network is using WEP or WPA, and if the code in in HEX or ASCII. Most users will not know.

--
Guttorm

[Kai Hendry]

Good comment. Tbh I still need to understand how ASCII converts to HEX
for WEP configurations. All the more frustrating since people
shouldn't be using this garbage. :/