Handing off one IP address from wireless to LAN and back
Running Kubuntu Natty on an older (T42) IBM Thinkpad. Both
the wired and the wireless interfaces are set to the same
manual IP address. Most of the time the wireless mode is used
but occasionally the cable connection is needed. Until
recently everything went well, with the wireless (eth1)
connecting automatically at startup and providing service via
the wireless router to the Internet and to the two or three
other machines on the local LAN. Then I changed the password
on the wireless router and things fell apart. Now:
-- at bootup it is necessary to provide the WEP password
via a dialogue box labeled "Secret" that pops up as soon as
the desktop stabilizes; and
-- the router passes data through to and from the Internet
(DSL/PPOE) but refuses to permit connection to the LAN until
I send <ifdown> to eth0.
The password demand is made despite the "Connect
Automatically" box being checked in SystemSettings /
NetworkConnections. The WEP-PSK key window is always blank
-- it's not being saved, after I fill it in each time.
Although <ifconfig> displays data on both eth0 and eth1,
/etc/network/interfaces shows entries only for the loopback
and for eth0, the LAN interface -- nothing about the
wireless.
It appears that System Settings decided to do something
creative with the networking configurations and startup
scripts -- how can I track them down and restore them to
default? Is there some kind of cheatsheet that tells which
files are affected by SystemSettings / NetworkConnections?
Googling leads me only to advice regarding
/etc/network/interfaces, but various edits to the "auto ethX"
and "iface ethX" stanzas have not been effective. Sigh.
Backing up and re-installing around /home is not a good idea,
unless I can be really sure that my problem doesn't lie
inside /home/.kde or something similar. Your thoughts,
please.
gds, stencil
--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
12-08-2011, 09:24 AM
Nils Kassube
Handing off one IP address from wireless to LAN and back
stencil wrote:
> Running Kubuntu Natty on an older (T42) IBM Thinkpad. Both
> the wired and the wireless interfaces are set to the same
> manual IP address.
I don't know if this is the reason for your trouble, but I'd like to
mention that an IP address is meant to identify an interface, not a
machine. Using the same IP address for different interfaces is not
necessarily a good idea.
> Most of the time the wireless mode is used
> but occasionally the cable connection is needed. Until
> recently everything went well, with the wireless (eth1)
> connecting automatically at startup and providing service via
> the wireless router to the Internet and to the two or three
> other machines on the local LAN. Then I changed the password
> on the wireless router and things fell apart. Now:
>
> -- at bootup it is necessary to provide the WEP password
> via a dialogue box labeled "Secret" that pops up as soon as
> the desktop stabilizes; and
[OT] Why do people still use WEP? WPA is around for ages and to use WEP
is similar to using no encryption at all [1].
More seriously: I would move to WPA (or even better WPA2) unless you
have very old hardware on your WLAN which doesn't support it. Then make
sure that you don't have to enter the password after bootup to avoid the
pop-up asking for the secret. Not sure how to do that ...
> -- the router passes data through to and from the Internet
> (DSL/PPOE) but refuses to permit connection to the LAN until
> I send <ifdown> to eth0.
See my first remark above. I suppose that you have two entries in the
routing table and the system tries the use the non-working eth0 first.
And your ifdown eth0 clears that routing table entry.
> The password demand is made despite the "Connect
> Automatically" box being checked in SystemSettings /
> NetworkConnections. The WEP-PSK key window is always blank
> -- it's not being saved, after I fill it in each time.
I just played with the Kubuntu 11.04 livecd. SystemSettings /
NetworkConnections seems to be a bit unreliable here. When I inserted
the WLAN USB stick some time after startup, it didn't find any wireless
network. Only after I used "sudo iwlist scan" on the commandline, it
worked. Therefore I would suggest to remove the wireless entry and add a
new entry for your network. Maybe the wireless password is then saved at
the right location and you don't have to enter it every time you start
the machine.
> Although <ifconfig> displays data on both eth0 and eth1,
> /etc/network/interfaces shows entries only for the loopback
> and for eth0, the LAN interface -- nothing about the
> wireless.
/etc/network/interfaces is used for manually managed interfaces only. If
you make an entry here, that interface should be ignored by network-
manager.
> Googling leads me only to advice regarding
> /etc/network/interfaces, but various edits to the "auto ethX"
> and "iface ethX" stanzas have not been effective. Sigh.
If you want to use /etc/network/interfaces instead of network-manager,
the entry would be something like this:
I don't know the syntax for WEP, but it should be similar (google should
know the details).
Another option would be to use WICD instead of network-manager - and if
you try it, don't forget to purge network-manager. Otherwise both
network-manager and WICD fight to control the wireless interface and
nothing works.
Nils
[1] <http://h-online.com/-732607>
--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
12-08-2011, 03:54 PM
stencil
Handing off one IP address from wireless to LAN and back
On Thu, 08 Dec 2011 12:00:30 +0000, Nils Kassube
wrote in kubuntu-users Digest, Vol 83, Issue 9:
>> [ ... ] I changed the password
>> on the wireless router and things fell apart. Now:
>>
>> -- at bootup it is necessary to provide the WEP password
>> via a dialogue box labeled "Secret" that pops up as soon as
>> the desktop stabilizes; and
>
>[ ... ] make
>sure that you don't have to enter the password after bootup to avoid the
>pop-up asking for the secret. Not sure how to do that ...
>
Nor do I, which prompted the original post. I guess the key
issue is that google will not yield to me a list of those
files written into by Network Manager (or its emulators) and
those files' default configurations, nor can I find a
coherent description (scripts read, files written) of the
startup sequence for the network interfaces.
The WEP-PSA thing is a red herring; here in the rural (US)
Berkshire hills, wardriving and the like are not a concern.
The system of swapping one IP from cable to wireless worked
satisfactorily, with auto login to the router, through three
previous password changes, two of which were under the
Maverick regime.
>
>Another option would be to use WICD instead of network-manager - and if
>you try it, don't forget to purge network-manager. Otherwise both
>network-manager and WICD fight to control the wireless interface and
>nothing works.
Sounds like the thing to do. I'll give it a lick this
weekend.
gds, stencil
--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
12-08-2011, 04:20 PM
uteck
Handing off one IP address from wireless to LAN and back
I would recommend you try using wicd in place of network-mangler.
On Thu, Dec 8, 2011 at 10:54 AM, stencil <stencil.sends@verizon.net> wrote:
On Thu, 08 Dec 2011 12:00:30 +0000, Nils Kassube
wrote in kubuntu-users Digest, Vol 83, Issue 9:
>> [ ... ] I changed the password
>> on the wireless router and things fell apart. *Now:
>>
>> * -- *at bootup it is necessary to provide the WEP password
>> via a dialogue box labeled "Secret" that pops up as soon as
>> the desktop stabilizes; *and
>
>[ ... ] make
>sure that you don't have to enter the password after bootup to avoid the
>pop-up asking for the secret. Not sure how to do that ...
>
Nor do I, which prompted the original post. *I guess the key
issue is that google will not yield to me a list of those
files written into by Network Manager (or its emulators) and
those files' default configurations, nor can I find a
coherent description (scripts read, files written) of the
startup sequence for the network interfaces.
The WEP-PSA thing is a red herring; *here in the rural (US)
Berkshire hills, wardriving and the like are not a concern.
The system of swapping one IP from cable to wireless worked
satisfactorily, with auto login to the router, through three
previous password changes, two of which were under the
Maverick regime.
>
>Another option would be to use WICD instead of network-manager - and if
>you try it, don't forget to purge network-manager. Otherwise both
>network-manager and WICD fight to control the wireless interface and
>nothing works.
Sounds like the thing to do. *I'll give it a lick this
weekend.
gds, *stencil
--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
--
no .sig found
Please restart your browser.
--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
Handing off one IP address from wireless to LAN and back
