Re: stupid networking question
Sadly, this doesn't work on my suse (/etc/sysconfig/...) based system. depeje On Thursday 08 January 2009 12:58:09 Thomas Otterbein wrote: FYI: On my kubuntu (ubuntu with KDE installed by default) using the KDE NetworkManager I followed the advices on http://wiki.openmoko.org/wiki/USB_Networking#Debian.2C_Ubuntu_and_others but insereted auto usb0 into /etc/network/interfaces as suggested by arne. It looks now like that: auto lo iface lo inet loopback # freerunner auto usb0 allow-hotplug usb0 iface usb0 inet static address 192.168.0.200 netmask 255.255.255.192 post-up /etc/network/freerunner start pre-down /etc/network/freerunner stop After a reboot (NetworkManager did not want to play well i.e. did not adopt to the changes) I get Device usb0: unmanaged and everything works as expected: My FR get's configured by /etc/network/freerunner and my (W)LAN-connections a correctly handled by NetworkManager. I guess this solution solves the issue for Ubuntu and all it's derivates too. Probably for all KDE-Installations as it seems that the key is to make the NetworkManager ignore the usb0-Interface. Regards thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: stupid networking question
On Tue, Jan 13, 2009 at 6:01 AM, Peter Nijs pe...@familienijs.be wrote: Sadly, this doesn't work on my suse (/etc/sysconfig/...) based system. depeje On Thursday 08 January 2009 12:58:09 Thomas Otterbein wrote: FYI: On my kubuntu (ubuntu with KDE installed by default) using the KDE NetworkManager I followed the advices on http://wiki.openmoko.org/wiki/USB_Networking#Debian.2C_Ubuntu_and_others but insereted auto usb0 into /etc/network/interfaces as suggested by arne. It looks now like that: auto lo iface lo inet loopback # freerunner auto usb0 allow-hotplug usb0 iface usb0 inet static address 192.168.0.200 netmask 255.255.255.192 post-up /etc/network/freerunner start pre-down /etc/network/freerunner stop After a reboot (NetworkManager did not want to play well i.e. did not adopt to the changes) I get Device usb0: unmanaged and everything works as expected: My FR get's configured by /etc/network/freerunner and my (W)LAN-connections a correctly handled by NetworkManager. I guess this solution solves the issue for Ubuntu and all it's derivates too. Probably for all KDE-Installations as it seems that the key is to make the NetworkManager ignore the usb0-Interface. Regards thomas Greetings! I have Debian lenny on a 686 and for the record, I do use the KDE for my window manager. I doubt KDE has any effect on the kernel level networking. That said, I am open to learning. I put this stanza in my /etc/network/interfaces file, to wit: allow-hotplug usb0 iface usb0 inet static address 192.168.0.200 netmask 255.255.255.0 I did not include the auto usb0 because I don't always have my FreeRunner (gta02, Date Code: 20070731) connected via the USB cable. Now, then, when I boot the desktop box, arno-iptables-firewall complains about usb0 not being there yet. Then, when I do boot my FreeRunner and connect the USB cable, I find I have an interface with the appropriate address automatically setup for me. Here is the output of a series of commands, before and after connecting: BEFORE: f...@irad:~$ ip link show 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:11:11:36:c9:b8 brd ff:ff:ff:ff:ff:ff f...@irad:~$ ip addr show 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:11:11:36:c9:b8 brd ff:ff:ff:ff:ff:ff inet 192.168.35.11/24 brd 192.168.35.255 scope global eth0 inet6 fe80::211:11ff:fe36:c9b8/64 scope link valid_lft forever preferred_lft forever AFTER: f...@irad:~$ ip link show 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:11:11:36:c9:b8 brd ff:ff:ff:ff:ff:ff 4: usb0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether fa:b5:c2:e2:09:ea brd ff:ff:ff:ff:ff:ff f...@irad:~$ ip addr show 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:11:11:36:c9:b8 brd ff:ff:ff:ff:ff:ff inet 192.168.35.11/24 brd 192.168.35.255 scope global eth0 inet6 fe80::211:11ff:fe36:c9b8/64 scope link valid_lft forever preferred_lft forever 4: usb0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether fa:b5:c2:e2:09:ea brd ff:ff:ff:ff:ff:ff inet 192.168.0.200/24 brd 192.168.0.255 scope global usb0 inet6 fe80::f8b5:c2ff:fee2:9ea/64 scope link valid_lft forever preferred_lft forever I use arno-iptables-firewall to set up my firewall and nat routing from the usb0 interface through my regular eth0 connection to my local router and Internet connection. I am delighted that this hotplug thingy works. Cheerio! -- Fielder George Dowding, KL7FHX dba Iceworm Enterprises Debian GNU/Linux Lenny User Number 269482 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: stupid networking question
networkmanager used to ignore interfaces listed in /etc/network/interfaces (and does this still on my debian/unstable box), so putting the wiki's stanza for usb0 auto usb0 ... might be worth a try. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: stupid networking question
arne anka wrote: networkmanager used to ignore interfaces listed in /etc/network/interfaces (and does this still on my debian/unstable box), so putting the wiki's stanza for usb0 auto usb0 ... might be worth a try. That sounds like a good idea, thanks for the hint. My eee and other machines all run debian and NM does the same. I think it's geared to usage situations (like in 90% of cases) where only one network connection is required at a time, and if a wired interface comes up you probably want to use it in preference to wireless most of the time. One of my quarrels with NM is that it's difficult to figure out how to stop it autoconnecting to, say, the neighbours open wireless that you used for a couple of days before your own ADSL was installed -- View this message in context: http://n2.nabble.com/stupid-networking-question-tp2120334p2127346.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: stupid networking question
One of my quarrels with NM is that it's difficult to figure out how to stop it autoconnecting to, say, the neighbours open wireless that you used for a couple of days before your own ADSL was installed i think a right click somewhere brings up a list of preferred networks where you can delete the entries not needed anymore (i distinctly remember the list, but not how i got there -- the offending network maybe?) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: stupid networking question
arne anka wrote: i think a right click somewhere brings up a list of preferred networks where you can delete the entries not needed anymore (i distinctly remember the list, but not how i got there -- the offending network maybe?) I think that may depend on the version, but on the redhat machine I've got beside me right now, yup, there's a right click edit wireless networks option. I also found out that somewhere under ~/.gconf there's a directory for each wireless network and you can delete those. Less than intuitive though! -- View this message in context: http://n2.nabble.com/stupid-networking-question-tp2120334p2127390.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: stupid networking question
I also found out that somewhere under ~/.gconf there's a directory for each wireless network and you can delete those. ah! you're using gnome. Less than intuitive though! well, it's gnome, isn't it? anyway, that's totally ot for the list now ... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: stupid networking question
FYI: On my kubuntu (ubuntu with KDE installed by default) using the KDE NetworkManager I followed the advices on http://wiki.openmoko.org/wiki/USB_Networking#Debian.2C_Ubuntu_and_others but insereted auto usb0 into /etc/network/interfaces as suggested by arne. It looks now like that: auto lo iface lo inet loopback # freerunner auto usb0 allow-hotplug usb0 iface usb0 inet static address 192.168.0.200 netmask 255.255.255.192 post-up /etc/network/freerunner start pre-down /etc/network/freerunner stop After a reboot (NetworkManager did not want to play well i.e. did not adopt to the changes) I get Device usb0: unmanaged and everything works as expected: My FR get's configured by /etc/network/freerunner and my (W)LAN-connections a correctly handled by NetworkManager. I guess this solution solves the issue for Ubuntu and all it's derivates too. Probably for all KDE-Installations as it seems that the key is to make the NetworkManager ignore the usb0-Interface. Regards thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: stupid networking question
On Thu, 8 Jan 2009 10:58:09 pm Thomas Otterbein wrote: On my kubuntu (ubuntu with KDE installed by default) using the KDE NetworkManager I followed the advices on http://wiki.openmoko.org/wiki/USB_Networking#Debian.2C_Ubuntu_and_others Which version of Kubuntu are you running ? I seem to remember some people commenting that with Intrepid (8.10) that stopped working, though I've not attempted to use this on my Intrepid laptop yet (I just do the ifconfig by hand). cheers, Chris -- Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC This email may come with a PGP signature as a file. Do not panic. For more info see: http://en.wikipedia.org/wiki/OpenPGP signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: stupid networking question
Which version of Kubuntu are you running ? 8.10 I seem to remember some people commenting that with Intrepid (8.10) that stopped working, though I've not attempted to use this on my Intrepid laptop yet (I just do the ifconfig by hand). yes I had the same issue but the described method solved it, at least for me. However I just got tired of continously running a whole bunch of commands just to get my phone -trying to avoid the term expensive brick here ;-) - connected to the internet and ready to receive updates. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: stupid networking question
Thomas Otterbein wrote: It looks now like that: auto lo iface lo inet loopback # freerunner auto usb0 allow-hotplug usb0 iface usb0 inet static address 192.168.0.200 netmask 255.255.255.192 post-up /etc/network/freerunner start pre-down /etc/network/freerunner stop You should only use auto usb0 or allow-hotplug usb0 but not both at the same time. For me it only works with auto and not hotplug but don't ask why. ;) Ciao, Rainer ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: stupid networking question
On Thu, 8 Jan 2009 11:13:46 pm Thomas Otterbein wrote: yes I had the same issue but the described method solved it, at least for me. Excellent! When I get a round tuit I'll sort that out on the laptop. :-) However I just got tired of continously running a whole bunch of commands just to get my phone -trying to avoid the term expensive brick here ;-) - connected to the internet and ready to receive updates. I've got my main desktop set up for that already, but that's running 8.04. All the best, Chris -- Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC This email may come with a PGP signature as a file. Do not panic. For more info see: http://en.wikipedia.org/wiki/OpenPGP signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: stupid networking question
You should only use auto usb0 or allow-hotplug usb0 but not both at the same time. For me it only works with auto and not hotplug but don't ask why. ;) Yes but it seems that entering both does not do any harm. The networking configuration uses the latest statement (allow-hotplug) while stupid NetworkManager only looks for auto to release his grip on the devices. So both get what they need to work properly and everyone is happy. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: stupid networking question
It looks now like that: auto lo iface lo inet loopback # freerunner auto usb0 allow-hotplug usb0 iface usb0 inet static address 192.168.0.200 netmask 255.255.255.192 post-up /etc/network/freerunner start pre-down /etc/network/freerunner stop You should only use auto usb0 or allow-hotplug usb0 but not both at the same time. Why not? auto is the same as allow-auto and nothing says you can't have allow-toto eth0 and allow-tata eth0 and allow-titi eth0. So if you have both allow-hotplug and auto for the same interface, it just means you want to bring it up at boot and you also want to bring it up when it gets plugged in. Stefan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: stupid networking question
only sense when a usb networking capable device is plugged in -- so allow-hotplug seems the only sensible option, to me, that is. Yes, but you both leave the OpenSource-Factor out. The (K)Ubuntu NetworkManager does not accept the allow-hotplug as a sign to keep it's fingers out of the interface configuration. The author has only considered auto as a possible option (at least I guess it's that simple). So sensible, correct or useless - it's the solution to the issue The FR cannot be used under KDE with running NetworkManager which seems to be a quite common problem. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: stupid networking question
Sorry, I'd misssed this reply last night somehow. What is in /etc/network/interfaces on the eeepc, and are you using NetworkManager? If using NM, is it the default NM from Ubuntu, or Kubuntu, or something else? This sounds to me like the NM is getting confused. Also, are you using WPA or WEP on the wifi? (Shouldn't matter, but if using NM now then changing to static config is more involved with WPA/WEP enabled) The problem I see most frequently with 8.10's NM is that it gets confused about statically-configured interfaces - EG, I have a workstation on a static public IP on eth0, and when I jack in the FR on usb0, NM brings up usb0 with the same friggin public IP, and tries to route packets through the FR instead of ethernet... j On Tue, 6 Jan 2009 21:06:39 -0500, Harry L. Lee ha...@jonesnose.com wrote: 7.10 alternate On Tue, Jan 6, 2009 at 8:31 PM, Joel Newkirk freerun...@newkirk.us wrote: On Tue, 6 Jan 2009 20:09:14 -0500, Harry L. Lee ha...@jonesnose.com wrote: I have an eeepcwifi'd into the Net, running ubuntu,but when i plug the openmoko into one of its usb ports it goes into wifi reconnection. halp! -- ha...@jonesnose.com What Ubuntu version and flavor? Network Manager has issues under 8.10/Intrepid - I've only had reliable networking (with multiple interfaces) when I disabled NM and wrote manual config. j -- Joel Newkirk http://jthinks.com (blog) http://newkirk.us/om (FR stuff) -- ha...@jonesnose.com Harry L Lee (via gmail) chief cook and bottle washer http://jonesnose.com mailto:ha...@jonesnose.com 207-384-8030 (email preferred) -- Joel Newkirk http://jthinks.com (blog) http://newkirk.us/om (FR stuff) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: stupid networking question
On Tue, 6 Jan 2009 20:09:14 -0500, Harry L. Lee ha...@jonesnose.com wrote: I have an eeepcwifi'd into the Net, running ubuntu,but when i plug the openmoko into one of its usb ports it goes into wifi reconnection. halp! -- ha...@jonesnose.com What Ubuntu version and flavor? Network Manager has issues under 8.10/Intrepid - I've only had reliable networking (with multiple interfaces) when I disabled NM and wrote manual config. j -- Joel Newkirk http://jthinks.com (blog) http://newkirk.us/om (FR stuff) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
