Webconverger connecting to network only on one computer
Olek T.
Alas, for many reasons I can't use DHCP with Webconverger terminals
(ethernet), so I had to manually type IP in the self-built ISO. I used
this tutorial:
It works great, I follow it step-by step and all I change is two
things:
1) my 'config/includes.chroot/etc/network/interfaces' file looks like
this:
auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet static
address 192.168.150.90
netmask 255.255.255.0
nwtwork 192.168.150.0
2) in 'auto/config' I change homepage to the one I need (Intranet)
And that's all. Then I build the Webconverger, burn it on a CD and it
works... but only on the machine that it was built on. When I try the
Live CD on another computer (which is identical), it just can't
connect to network. When I install Debian and build Webconverger on
that second computer, the Webconverger works fine, but again - only on
this computer, not on any other. What's the cause? The only difference
between the computers may be MAC address of ethernet card. Should I
install Debian on my every terminal and then build the Live CD from
the scratch on it espacially for that computer? That makes no sense :-
(
Also, I can't check 'ifconfig' in terminal window, as it's not
included in the Live CD with Webconverger (I don't know why).
Do you have any idea, what's going on?
Kai Hendry
> http://groups.google.com/group/webc-users/browse_thread/thread/3b06d59af77e6d13/d6c04ad8b097e2f4?lnk=gst&q=step#d6c04ad8b097e2f4
You should be using this tutorial: http://webconverger.org/develop
I don't see what that group post has that
http://webconverger.org/develop doesn't. I want authoritative
information in the wiki and people to ideally reference that instead.
I'm happy to grant write permissions to the wiki if users ask.
> address 192.168.150.90
> works... but only on the machine that it was built on. When I try the
> Live CD on another computer (which is identical), it just can't
> connect to network. When I install Debian and build Webconverger on
> Do you have any idea, what's going on?
IIUC you are using the same IP with two computers? Or have I mis-understood you?
Using the same IP obviously shouldn't work. :)
Kind regards,
Olek T.
> You should be using this tutorial:http://webconverger.org/develop
>
> I don't see what that group post has thathttp://webconverger.org/developdoesn't.
I used http://webconverger.org/develop, but this step-by-step is more
detailed...
> IIUC you are using the same IP with two computers? Or have I mis-understood you?
Yes, you understood correctly. I try the CD with hard-coded IP on two
computers, but not simultanously (I'm not stupid). First I tried on
the one that I built the Live CD on (worked), then turned it off and
tried on another - identical (not worked).
What I also noticed - when Live CD works, in /tmp is 'MACID' file with
the NIC's MAC, on the computer that cannot connect to network there is
also MACID file, but empty. I don't know if this has anything to do
with the problem, but really - MAC number is the only difference
between the computers. I'm stuck.
Kai Hendry
> What I also noticed - when Live CD works, in /tmp is 'MACID' file with
> the NIC's MAC, on the computer that cannot connect to network there is
> also MACID file, but empty. I don't know if this has anything to do
> with the problem, but really - MAC number is the only difference
> between the computers. I'm stuck.
Both machines are absolutely identical?
I have noticed a problem where some machines come up on eth1 instead
of the expected eth0 on new 3.x kernels. At least that throws me.
Try `/sbin/ifconfig` in debug mode to look a little more. `ip addr`
should also work, which I'm told is the "new way" to do things. :)
Olek T.
Yes. We bought nearly 30 of them - all the same model. So yeah, pretty
much identical.
>
> I have noticed a problem where some machines come up on eth1 instead
> of the expected eth0 on new 3.x kernels. At least that throws me.
I tried with eth1 - it didn't want to work at all.
> Try `/sbin/ifconfig` in debug mode to look a little more. `ip addr`
> should also work, which I'm told is the "new way" to do things. :)
I tried to run those commands before, but for some reason they are not
included on built CD. I have no idea why.
As for the 'main' problem - now I'm 100% sure: when I manually input
static IP, during building process this IP is somehow assigned to MAC
address of computer that it is built on. That's why the CD works only
on this very computer. It looks like I'll have to install Debian on my
30 computers, then on each one individually build Live CD with
Webconverger. Sounds silly and will take helluva time, but I guess
it's the only way to make it work at the moment. To be honest I'm
pretty happy that I managed to successfully build Webconverger in the
first place :-)
I work in library and we need terminals that will be able to visit our
intranet book catalog only, so Webconverger is exactly what we need.
Kai Hendry
>> Try `/sbin/ifconfig` in debug mode to look a little more. `ip addr`
>> should also work, which I'm told is the "new way" to do things. :)
> I tried to run those commands before, but for some reason they are not
> included on built CD. I have no idea why.
The fact you are missing these network tools in your build sends alarm
bells for me. You should certainly have them.
Xenchou
I am no Linux expert (use it about once or twice a year from odd
things), so take this for what it is worth....
What may be happening is that the eth0 is 'reserved' by a MAC address,
and when you transfer to a second computer the system renames the
local eth0 (which no longer matched the MAC it knows) to eth1. If you
start a Kiosk without the 'noroot', start a terminal, and check the
syslog:
webc@webconverger:~$sudo grep eth /var/log/syslog
You will see a couple lines, but one should end with something like
this:
udev[448]: renamed network interface eth0 to eth1
If you see the same message, then you probably have this file:
webc@webconverger:~$sudo cat /etc/udev/rules.d/70-persistent-net.rules
You will notice in this file it reserves eh0 to a specific MAC
address, the same as the one from the system you built the Kiosk on.
On regular builds from Kai this file does not exist. You have one
because on your system that you built the ISO on did, and Kai does
not. Check your own system for the same file, and compare the output
to that from the CD.
During the live-build process your local files are used to build the
CD. To avoid this issue, you can remove your local copy (and I
recommend any other files in rules.d) until the build is finished.
This should keep your eth0 as eth0, and avoid brining over local
settings (mounts as well) to the Kiosk system.
A second option, now that you know what the system is renaming it to
(eth1 most likely) then you can update your interfaces files to apply
the same IP to eth1. Just use the same file, but replace the eth0's
with eth1's.
This is something I noticed happening on a system I just recently did,
and while I haven't tested this fully yet (not at the location) it
seems to work in the little lab I have here at home.
Also, for ifconfig, try :
webc@webconverger:~$sudo ifconfig
Stewart
On Dec 16 2011, 5:53 am, "Olek T." <a.trembowie...@gmail.com> wrote:
> Hi,
>
> Alas, for many reasons I can't use DHCP with Webconverger terminals
> (ethernet), so I had to manually type IP in the self-built ISO. I used
> this tutorial:
>
Kai Hendry
> webc@webconverger:~$sudo cat /etc/udev/rules.d/70-persistent-net.rules
Nice catch Stewart. :-)
http://www.flickr.com/photos/hendry/6665918219
This explains a lot! I guess I should try override this file with an
empty file next.
Kind regards,
Matthijs Kooijman
> > webc@webconverger:~$sudo cat /etc/udev/rules.d/70-persistent-net.rules
I ran into this problem as well last week, hadn't gotten around to
reporting it yet.
> This explains a lot! I guess I should try override this file with an
> empty file next.
I fixed it by dropping the attached mini-script in config/hooks.
Gr.
Matthijs
Olek T.
so much!!! Finally this strange problem is resolved :-)
Matthijs Kooijman
yesterday, Daniel pointed out that live-build already contains a hook to
fix this issue. However, it turns out hook processing was half-broken in
the latest live-build versions, so it didn't work.
I've since sorted out the hook processing stuff and made it work again.
I expect Daniel to merge it before the next release, so expect this
issue to be resolved when using (still unreleased) live-build 3.0~a42-1.
Gr.
Matthijs
Kai Hendry
On 11 January 2012 05:13, Matthijs Kooijman <matt...@stdin.nl> wrote:
> issue to be resolved when using (still unreleased) live-build 3.0~a42-1.
I'm running an old build of Debian live now and with the hook run
explicitly in the config
http://anonscm.debian.org/gitweb/?p=debian-live/config-webc.git;a=commitdiff;h=9794417f0c81e2aa2bc16f98be22ae0254908e23
The latest daily builds look fine. http://build.webconverger.org/ I
would greatly appreciate any feedback if there are any problems with
the dailies before a release. :)
So I plan to release Webconverger 11 by the end of the week. Just
making some final tweaks to
https://github.com/kaihendry/iceweasel-webconverger and of course
preparing release notes to coincide.
After 11 is out the door I will upgrade the build host to the latest
unstable Debian Live.
Many thanks,
Matthijs Kooijman
---
webconverger/config/archives/artax-backports.list | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/webconverger/config/archives/artax-backports.list b/webconverger/config/archives/artax-backports.list
index e6535dc..d05037a 100644
--- a/webconverger/config/archives/artax-backports.list
+++ b/webconverger/config/archives/artax-backports.list
@@ -1 +1 @@
-deb http://archive.progress-linux.org/progress/ artax-backports main non-free
+deb http://archive.progress-linux.org/progress/ artax-backports main contrib non-free
--
1.7.7.3
Kai Hendry
Not quite git email savvy, so applied by hand. :)
Matthijs Kooijman
> Not quite git email savvy, so applied by hand. :)
Heh, I've only really used the sending part so far, that's easy ;-p
(I think that you can just paste a full e-mail message, including all
headers into "git am" and it should Just Work, though).
Gr.
Matthijs