Re: USB networking Win7

2014-01-17 Thread dmatthews.org
Hi Matthias

chiark.greenend.org.uk/~sgtatham/putty/

PuTTY is quite a decent (free as in beer) ssh client for windows

-- 
David Matthews 
m...@dmatthews.org

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking Win7

2014-01-17 Thread Michael Spacefalcon
dmatthews.org m...@dmatthews.org wrote:

 PuTTY is quite a decent (free as in beer) ssh client for windows

PuTTY is free as in speech too, i.e., it is bona fide free software -
not just free as in beer.  Of course Windows isn't, but we are talking
about PuTTY, right?

VLR,
SF

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking Win7

2014-01-17 Thread Matthias Apitz
El día Friday, January 17, 2014 a las 05:07:22PM +, Michael Spacefalcon 
escribió:

 dmatthews.org m...@dmatthews.org wrote:
 
  PuTTY is quite a decent (free as in beer) ssh client for windows
 
 PuTTY is free as in speech too, i.e., it is bona fide free software -
 not just free as in beer.  Of course Windows isn't, but we are talking
 about PuTTY, right?

I know PuTTY very well. But, I was talking about how to bring up the
USB network interface in Win7

Thanks

matthias
-- 
Matthias Apitz   |  /\ ASCII Ribbon Campaign: www.asciiribbon.org
E-mail: g...@unixarea.de |  \ / - No HTML/RTF in E-mail
WWW: http://www.unixarea.de/ |   X  - No proprietary attachments
phone: +49-170-4527211   |  / \ - Respect for open standards

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking Win7

2014-01-17 Thread rhn
On Fri, 17 Jan 2014 18:25:24 +0100
Matthias Apitz g...@unixarea.de wrote:

 El día Friday, January 17, 2014 a las 05:07:22PM +, Michael Spacefalcon 
 escribió:
 
  dmatthews.org m...@dmatthews.org wrote:
  
   PuTTY is quite a decent (free as in beer) ssh client for windows
  
  PuTTY is free as in speech too, i.e., it is bona fide free software -
  not just free as in beer.  Of course Windows isn't, but we are talking
  about PuTTY, right?
 
 I know PuTTY very well. But, I was talking about how to bring up the
 USB network interface in Win7
 
 Thanks
 
   matthias

The Freerunner works as a USB Ethernet gadget (RNDIS).
You need to install an .inf file (some kind of a description?) or else Windows 
will not work with it.

[1] is describing how to do it. I did it a long time ago myself with the 
Freerunner, but I'm not sure if I used this exact guide.

Cheers,
rhn

[1]http://wiki.openmoko.org/wiki/Neo_1973_and_Windows#USB_Ethernet_emulation

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking Win7

2014-01-17 Thread matteo sanvito
Yeah, i can confirm what rhn said, I did the same!

good luck!
matteo


2014/1/17 rhn omcomali@porcupinefactory.org

 On Fri, 17 Jan 2014 18:25:24 +0100
 Matthias Apitz g...@unixarea.de wrote:

  El día Friday, January 17, 2014 a las 05:07:22PM +, Michael
 Spacefalcon escribió:
 
   dmatthews.org m...@dmatthews.org wrote:
  
PuTTY is quite a decent (free as in beer) ssh client for windows
  
   PuTTY is free as in speech too, i.e., it is bona fide free software -
   not just free as in beer.  Of course Windows isn't, but we are talking
   about PuTTY, right?
 
  I know PuTTY very well. But, I was talking about how to bring up the
  USB network interface in Win7
 
  Thanks
 
matthias

 The Freerunner works as a USB Ethernet gadget (RNDIS).
 You need to install an .inf file (some kind of a description?) or else
 Windows will not work with it.

 [1] is describing how to do it. I did it a long time ago myself with the
 Freerunner, but I'm not sure if I used this exact guide.

 Cheers,
 rhn

 [1]
 http://wiki.openmoko.org/wiki/Neo_1973_and_Windows#USB_Ethernet_emulation

 ___
 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: USB Networking Issue

2012-05-13 Thread Matthias Apitz
El día Sunday, May 13, 2012 a las 09:57:55AM -0500, Cristian Gómez escribió:

 Hi guys, I'm using SHR (last build) on NAND and QTMoko on SD and when I
 connect my FR to my Arch Linux box, I can't get a new network interface to
 ping/ssh to. This happens on Arch, in Ubuntu the interface is created
 without problems
 
 Do you know how to fix this?

I do not know anything about Arch Linux. But, I have had the same
problem with FreeBSD. With the older SHR version (around 2010) the
interface was created fine, while with the recent (stage 046, or even
before) it was not created. The problem was that the USB vendor and
product ID is now presented by the SHR Linux kernel as 0x0525:0xa4a2
(and as well the IP addr pair changed, btw.). In FreeBSD I have had to
adjust my device daemon hook scripts to that. Maybe Arch Linux uses a
similar procedure to detect the USB device as a network device ...

HIH, espero que te ayude

matthias
-- 
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e g...@unixarea.de - w http://www.unixarea.de/
UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking Issue

2012-05-13 Thread Timo Juhani Lindfors
Cristian Gómez cristianp...@gmail.com writes:
 Do you know how to fix this?

It'd be useful to see the output of the dmesg, ip address and ip
route commands from both arch and ubuntu.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking with Ubuntu 9.04

2009-10-08 Thread Sander van Grieken
Why use a script that you need to run manually each time?

It can be done automatically just by putting the right stuff in 
/etc/network/interfaces:

auto eth2
iface eth2 inet static
  address 192.168.0.200
  netmask 255.255.255.0
  post-up iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -j MASQUERADE
  post-up echo 1  /proc/sys/net/ipv4/ip_forward
  post-up route add -host 192.168.0.202 dev eth2
  post-up dnsmasq
  pre-down echo 0  /proc/sys/net/ipv4/ip_forward
  pre-down iptables -t nat -D POSTROUTING -s 192.168.0.0/24 -j MASQUERADE
  pre-down killall dnsmasq


when you plug in the FR, eth2 will activate automatically..

grtz
Sander


On Thursday 08 October 2009 03:24:06 Cristian Gómez wrote:
 Hi Tony, thanks for giving a try to the script. I'm glad it helped you. I
 just create a sub-section on the wiki page [1] where I put the script to
 help others to get connected easily.
 
 Cheers
 
 [1] http://wiki.openmoko.org/wiki/USB_Networking#Connection_Script
 
 /***
 * Don't Worry...Be Linux
 * Cristian Gómez Alvarez
 * Ingeniero en Sistemas y Computación
 * Universidad de Caldas
 * Comunidad de Software Libre Manizales
 * IEEE/WIE Student Member
 * Linux User #463617
 * Mi Blog: http://cristianpark.sehablalinux.com/
 /
 
 
 2009/10/7 Tony Berth tonybe...@googlemail.com
 
  On Wed, Oct 7, 2009 at 10:27 AM, Matthias Huber 
 
  matthias.hu...@wollishausen.de wrote:
   Tony Berth schrieb:
 
  Bingo. Thanks A LOT!
 
  Is it possible to update the Wiki with that one. I think this will be a
  great help to the whole community
 
   if you would tell me wich of / or both tricks did it on your system ?
 
  but i had to add this two lines to my /etc/ufw/ufw.conf
 
  ufw allow from 192.168.0.202
  ufw allow to 192.168.0.202
 
 
  another trial with iptables needs to load some modules too:
 
  #!/bin/sh
 
  MOKO=192.168.0.202
 
  echo 1  /proc/sys/net/ipv4/ip_forward
   modprobe ipt_MASQUERADE
 
  iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
  iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
  iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32
 
  what works was the script Cristian Gomez included in his reply!
 
  Just for the records, the first time I run that script it does assign the
  192.168.0.200 IP to eth1 but can't ping/access 192.168.0.202! Then:
 
  - I disconnect Openmoko
  - connect it again
  - re-run the script and voila the connection is there!
 
  Thanks
 
  Tony
 
 
  ___
  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: USB networking with Ubuntu 9.04

2009-10-08 Thread Tony Berth
did try that and did work when I was using a debian 5 box but no chance with
ubuntu 9.04 :(

Thanks

Tony

On Thu, Oct 8, 2009 at 1:21 PM, Sander van Grieken san...@3v8.net wrote:

 Why use a script that you need to run manually each time?

 It can be done automatically just by putting the right stuff in
 /etc/network/interfaces:

 auto eth2
 iface eth2 inet static
   address 192.168.0.200
   netmask 255.255.255.0
   post-up iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -j MASQUERADE
  post-up echo 1  /proc/sys/net/ipv4/ip_forward
  post-up route add -host 192.168.0.202 dev eth2
  post-up dnsmasq
  pre-down echo 0  /proc/sys/net/ipv4/ip_forward
  pre-down iptables -t nat -D POSTROUTING -s 192.168.0.0/24 -j MASQUERADE
  pre-down killall dnsmasq


 when you plug in the FR, eth2 will activate automatically..

 grtz
 Sander


 On Thursday 08 October 2009 03:24:06 Cristian Gómez wrote:
  Hi Tony, thanks for giving a try to the script. I'm glad it helped you. I
  just create a sub-section on the wiki page [1] where I put the script to
  help others to get connected easily.
 
  Cheers
 
  [1] http://wiki.openmoko.org/wiki/USB_Networking#Connection_Script
 
  /***
  * Don't Worry...Be Linux
  * Cristian Gómez Alvarez
  * Ingeniero en Sistemas y Computación
  * Universidad de Caldas
  * Comunidad de Software Libre Manizales
  * IEEE/WIE Student Member
  * Linux User #463617
  * Mi Blog: http://cristianpark.sehablalinux.com/
  /
 
 
  2009/10/7 Tony Berth tonybe...@googlemail.com
 
   On Wed, Oct 7, 2009 at 10:27 AM, Matthias Huber 
  
   matthias.hu...@wollishausen.de wrote:
Tony Berth schrieb:
  
   Bingo. Thanks A LOT!
  
   Is it possible to update the Wiki with that one. I think this will be
 a
   great help to the whole community
  
if you would tell me wich of / or both tricks did it on your system ?
  
   but i had to add this two lines to my /etc/ufw/ufw.conf
  
   ufw allow from 192.168.0.202
   ufw allow to 192.168.0.202
  
  
   another trial with iptables needs to load some modules too:
  
   #!/bin/sh
  
   MOKO=192.168.0.202
  
   echo 1  /proc/sys/net/ipv4/ip_forward
modprobe ipt_MASQUERADE
  
   iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
   iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
   iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32
  
   what works was the script Cristian Gomez included in his reply!
  
   Just for the records, the first time I run that script it does assign
 the
   192.168.0.200 IP to eth1 but can't ping/access 192.168.0.202! Then:
  
   - I disconnect Openmoko
   - connect it again
   - re-run the script and voila the connection is there!
  
   Thanks
  
   Tony
  
  
   ___
   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

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking with Ubuntu 9.04

2009-10-08 Thread Eric Olson
I copied Sander's exact lines into /etc/network/interfaces (I changed 
eth2 to usb0 -- I don't know if that matters) on my ubuntu 9.04 laptop 
and it's working for me.  I have plugged and unplugged the cable a 
couple times and no longer have to run my manual script each time.

Thanks!
Eric

Tony Berth wrote:
 did try that and did work when I was using a debian 5 box but no chance with
 ubuntu 9.04 :(
 
 Thanks
 
 Tony
 
 On Thu, Oct 8, 2009 at 1:21 PM, Sander van Grieken san...@3v8.net wrote:
 
 Why use a script that you need to run manually each time?

 It can be done automatically just by putting the right stuff in
 /etc/network/interfaces:

 auto eth2
 iface eth2 inet static
   address 192.168.0.200
   netmask 255.255.255.0
   post-up iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -j MASQUERADE
  post-up echo 1  /proc/sys/net/ipv4/ip_forward
  post-up route add -host 192.168.0.202 dev eth2
  post-up dnsmasq
  pre-down echo 0  /proc/sys/net/ipv4/ip_forward
  pre-down iptables -t nat -D POSTROUTING -s 192.168.0.0/24 -j MASQUERADE
  pre-down killall dnsmasq


 when you plug in the FR, eth2 will activate automatically..

 grtz
 Sander


 On Thursday 08 October 2009 03:24:06 Cristian Gómez wrote:
 Hi Tony, thanks for giving a try to the script. I'm glad it helped you. I
 just create a sub-section on the wiki page [1] where I put the script to
 help others to get connected easily.

 Cheers

 [1] http://wiki.openmoko.org/wiki/USB_Networking#Connection_Script

 /***
 * Don't Worry...Be Linux
 * Cristian Gómez Alvarez
 * Ingeniero en Sistemas y Computación
 * Universidad de Caldas
 * Comunidad de Software Libre Manizales
 * IEEE/WIE Student Member
 * Linux User #463617
 * Mi Blog: http://cristianpark.sehablalinux.com/
 /


 2009/10/7 Tony Berth tonybe...@googlemail.com

 On Wed, Oct 7, 2009 at 10:27 AM, Matthias Huber 

 matthias.hu...@wollishausen.de wrote:
  Tony Berth schrieb:

 Bingo. Thanks A LOT!

 Is it possible to update the Wiki with that one. I think this will be
 a
 great help to the whole community

  if you would tell me wich of / or both tricks did it on your system ?

 but i had to add this two lines to my /etc/ufw/ufw.conf

 ufw allow from 192.168.0.202
 ufw allow to 192.168.0.202


 another trial with iptables needs to load some modules too:

 #!/bin/sh

 MOKO=192.168.0.202

 echo 1  /proc/sys/net/ipv4/ip_forward
  modprobe ipt_MASQUERADE

 iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
 iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
 iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32
 what works was the script Cristian Gomez included in his reply!

 Just for the records, the first time I run that script it does assign
 the
 192.168.0.200 IP to eth1 but can't ping/access 192.168.0.202! Then:

 - I disconnect Openmoko
 - connect it again
 - re-run the script and voila the connection is there!

 Thanks

 Tony


 ___
 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

 
 
 
 
 ___
 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: USB networking with Ubuntu 9.04

2009-10-07 Thread Tony Berth
Bingo. Thanks A LOT!

Is it possible to update the Wiki with that one. I think this will be a
great help to the whole community

Cheers

Tony

2009/10/7 Cristian Gómez cristianp...@gmail.com

 Hi, What I do to connect the FreeRunner to the PC is running this script
 [1] that I've made with the things listed on the wiki. To run it just type
 sudo sh usb_networking.sh.

 I used it on Arch Linux and Ubuntu and I think it works on every distro as
 well. Any changes, suggestions are welcome. Currently it's on spanish.

 Note: The script is configured for SHR so it uses the eth1 interface not
 the usb0

 [1] http://www.mediafire.com/download.php?zm0gtz2tyjq

 /***
 * Don't Worry...Be Linux
 * Cristian Gómez Alvarez
 * Ingeniero en Sistemas y Computación
 * Universidad de Caldas
 * Comunidad de Software Libre Manizales
 * IEEE/WIE Student Member
 * Linux User #463617
 * Mi Blog: http://cristianpark.sehablalinux.com/
 /


 2009/10/6 Matthias Huber matthias.hu...@wollishausen.de

  Tony Berth schrieb:

 On Tue, Oct 6, 2009 at 10:00 PM, Frederik Sdun 
 frederik.s...@googlemail.com wrote:

 * Tony Berth tonybe...@googlemail.com [06.10.2009 18:06]:
  followed as described in:
 
 http://wiki.openmoko.org/wiki/USB_Networking
 
 -
 
Ubuntu 9.04 - the Jaunty Jackalope -- udev
 
 One can see /etc/udev/rules.d that a device plugged in on USB will
 be
 called eth1. Go to system-Administration-Network and add the
 parameters
 for eth1  static ip, address 192.168.0.200 mask 255.255.255.192 add
 your
 default gateway. Thats is all.
 
 Tested with Qi bootloader aka official MAC address of the Freerunner
 : on
 Android Koolu beta 7
 
 Carig Philippines --frank 14:11, 17 June 2009 (UTC)
 
 --
 
 and eth1 gets assigned the proper IP address. I can connect to Neo
 but
 from there I don't have any connection to the 'outside'. Please
 notice
 that resolv.conf has the correct Opendns IPs!
 
 Actually I should face the same problem as described in:
 
 http://lists.openmoko.org/nabble.html#nabble-td3119750
 
 but the postings there weren't of any help :(
 
 Thanks
 
 Tony
  I used the config you can find in [0] and it works.


 [0]
 http://wiki.openmoko.org/wiki/USB_Networking#Debian.2C_Ubuntu_and_others
  ___


 but this one 'ties' it in usb0 although it connects as eth1! How can this
 work?

 I also used the following entries in /etc/network/interfaces:

 #freerunner3
 allow-hotplug eth1
 iface eth1 inet static
 address 192.168.0.200
 netmask 255.255.255.0
 network 192.168.0.0
 up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 
 up echo 1  /proc/sys/net/ipv4/ip_forward 
 up iptables -P FORWARD ACCEPT 
 down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 

 and didn't work! Openmoko wasn't able to get an IP address at all!

 get ip adress ? dont understand this.

 but i had to add this two lines to my /etc/ufw/ufw.conf

 ufw allow from 192.168.0.202
 ufw allow to 192.168.0.202


 another trial with iptables needs to load some modules too:

 #!/bin/sh

 MOKO=192.168.0.202

 echo 1  /proc/sys/net/ipv4/ip_forward
 modprobe ipt_MASQUERADE

 iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
 iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
 iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32


 --
 Mit freundlichen Grüssen
 Matthias Huber
 Kohlstattstr. 14
 86459 Wollishausen
 Tel: 08238-7998
 LPI000181125


 ___
 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


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking with Ubuntu 9.04

2009-10-07 Thread Matthias Huber

Tony Berth schrieb:

Bingo. Thanks A LOT!

Is it possible to update the Wiki with that one. I think this will be 
a great help to the whole community



if you would tell me wich of / or both tricks did it on your system ?



but i had to add this two lines to my /etc/ufw/ufw.conf

ufw allow from 192.168.0.202
ufw allow to 192.168.0.202


another trial with iptables needs to load some modules too:

#!/bin/sh

MOKO=192.168.0.202


echo 1  /proc/sys/net/ipv4/ip_forward
modprobe ipt_MASQUERADE

iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32




--
Mit freundlichen Grüssen
Matthias Huber 
Kohlstattstr. 14

86459 Wollishausen
Tel: 08238-7998
LPI000181125

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking with Ubuntu 9.04

2009-10-07 Thread Tony Berth
On Wed, Oct 7, 2009 at 10:27 AM, Matthias Huber 
matthias.hu...@wollishausen.de wrote:

  Tony Berth schrieb:

 Bingo. Thanks A LOT!

 Is it possible to update the Wiki with that one. I think this will be a
 great help to the whole community

  if you would tell me wich of / or both tricks did it on your system ?


 but i had to add this two lines to my /etc/ufw/ufw.conf

 ufw allow from 192.168.0.202
 ufw allow to 192.168.0.202


 another trial with iptables needs to load some modules too:

 #!/bin/sh

 MOKO=192.168.0.202

 echo 1  /proc/sys/net/ipv4/ip_forward
  modprobe ipt_MASQUERADE

 iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
 iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
 iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32


what works was the script Cristian Gomez included in his reply!

Just for the records, the first time I run that script it does assign the
192.168.0.200 IP to eth1 but can't ping/access 192.168.0.202! Then:

- I disconnect Openmoko
- connect it again
- re-run the script and voila the connection is there!

Thanks

Tony
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking with Ubuntu 9.04

2009-10-07 Thread Cristian Gómez
Hi Tony, thanks for giving a try to the script. I'm glad it helped you. I
just create a sub-section on the wiki page [1] where I put the script to
help others to get connected easily.

Cheers

[1] http://wiki.openmoko.org/wiki/USB_Networking#Connection_Script

/***
* Don't Worry...Be Linux
* Cristian Gómez Alvarez
* Ingeniero en Sistemas y Computación
* Universidad de Caldas
* Comunidad de Software Libre Manizales
* IEEE/WIE Student Member
* Linux User #463617
* Mi Blog: http://cristianpark.sehablalinux.com/
/


2009/10/7 Tony Berth tonybe...@googlemail.com



 On Wed, Oct 7, 2009 at 10:27 AM, Matthias Huber 
 matthias.hu...@wollishausen.de wrote:

  Tony Berth schrieb:

 Bingo. Thanks A LOT!

 Is it possible to update the Wiki with that one. I think this will be a
 great help to the whole community

  if you would tell me wich of / or both tricks did it on your system ?


 but i had to add this two lines to my /etc/ufw/ufw.conf

 ufw allow from 192.168.0.202
 ufw allow to 192.168.0.202


 another trial with iptables needs to load some modules too:

 #!/bin/sh

 MOKO=192.168.0.202

 echo 1  /proc/sys/net/ipv4/ip_forward
  modprobe ipt_MASQUERADE

 iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
 iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
 iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32


 what works was the script Cristian Gomez included in his reply!

 Just for the records, the first time I run that script it does assign the
 192.168.0.200 IP to eth1 but can't ping/access 192.168.0.202! Then:

 - I disconnect Openmoko
 - connect it again
 - re-run the script and voila the connection is there!

 Thanks

 Tony


 ___
 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: USB networking with Ubuntu 9.04

2009-10-06 Thread Frederik Sdun
* Tony Berth tonybe...@googlemail.com [06.10.2009 18:06]:
followed as described in:
 
http://wiki.openmoko.org/wiki/USB_Networking
 
-
 
   Ubuntu 9.04 - the Jaunty Jackalope -- udev
 
One can see /etc/udev/rules.d that a device plugged in on USB will be
called eth1. Go to system-Administration-Network and add the parameters
for eth1  static ip, address 192.168.0.200 mask 255.255.255.192 add your
default gateway. Thats is all.
 
Tested with Qi bootloader aka official MAC address of the Freerunner : on
Android Koolu beta 7
 
Carig Philippines --frank 14:11, 17 June 2009 (UTC)
 
--
 
and eth1 gets assigned the proper IP address. I can connect to Neo but
from there I don't have any connection to the 'outside'. Please notice
that resolv.conf has the correct Opendns IPs!
 
Actually I should face the same problem as described in:
 
http://lists.openmoko.org/nabble.html#nabble-td3119750
 
but the postings there weren't of any help :(
 
Thanks
 
Tony
I used the config you can find in [0] and it works.


[0] http://wiki.openmoko.org/wiki/USB_Networking#Debian.2C_Ubuntu_and_others
 ___
 Openmoko community mailing list
 community@lists.openmoko.org
 http://lists.openmoko.org/mailman/listinfo/community


-- 
IRC: playya @ Freenode, Gimpnet
xmpp: pla...@draugr.de


signature.asc
Description: Digital signature
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking with Ubuntu 9.04

2009-10-06 Thread Tony Berth
On Tue, Oct 6, 2009 at 10:00 PM, Frederik Sdun frederik.s...@googlemail.com
 wrote:

 * Tony Berth tonybe...@googlemail.com [06.10.2009 18:06]:
 followed as described in:
 
 http://wiki.openmoko.org/wiki/USB_Networking
 
 -
 
Ubuntu 9.04 - the Jaunty Jackalope -- udev
 
 One can see /etc/udev/rules.d that a device plugged in on USB will be
 called eth1. Go to system-Administration-Network and add the
 parameters
 for eth1  static ip, address 192.168.0.200 mask 255.255.255.192 add
 your
 default gateway. Thats is all.
 
 Tested with Qi bootloader aka official MAC address of the Freerunner :
 on
 Android Koolu beta 7
 
 Carig Philippines --frank 14:11, 17 June 2009 (UTC)
 
 --
 
 and eth1 gets assigned the proper IP address. I can connect to Neo but
 from there I don't have any connection to the 'outside'. Please notice
 that resolv.conf has the correct Opendns IPs!
 
 Actually I should face the same problem as described in:
 
 http://lists.openmoko.org/nabble.html#nabble-td3119750
 
 but the postings there weren't of any help :(
 
 Thanks
 
 Tony
 I used the config you can find in [0] and it works.


 [0]
 http://wiki.openmoko.org/wiki/USB_Networking#Debian.2C_Ubuntu_and_others
  ___


but this one 'ties' it in usb0 although it connects as eth1! How can this
work?

I also used the following entries in /etc/network/interfaces:

#freerunner3
allow-hotplug eth1
iface eth1 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 
up echo 1  /proc/sys/net/ipv4/ip_forward 
up iptables -P FORWARD ACCEPT 
down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 

and didn't work! Openmoko wasn't able to get an IP address at all!

Thanks

Tony
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking with Ubuntu 9.04

2009-10-06 Thread Matthias Huber

Tony Berth schrieb:
On Tue, Oct 6, 2009 at 10:00 PM, Frederik Sdun 
frederik.s...@googlemail.com mailto:frederik.s...@googlemail.com 
wrote:


* Tony Berth tonybe...@googlemail.com
mailto:tonybe...@googlemail.com [06.10.2009 18:06]:
followed as described in:

http://wiki.openmoko.org/wiki/USB_Networking

-

   Ubuntu 9.04 - the Jaunty Jackalope -- udev

One can see /etc/udev/rules.d that a device plugged in on USB
will be
called eth1. Go to system-Administration-Network and add
the parameters
for eth1  static ip, address 192.168.0.200 mask
255.255.255.192 add your
default gateway. Thats is all.

Tested with Qi bootloader aka official MAC address of the
Freerunner : on
Android Koolu beta 7

Carig Philippines --frank 14:11, 17 June 2009 (UTC)

--

and eth1 gets assigned the proper IP address. I can connect
to Neo but
from there I don't have any connection to the 'outside'.
Please notice
that resolv.conf has the correct Opendns IPs!

Actually I should face the same problem as described in:

http://lists.openmoko.org/nabble.html#nabble-td3119750

but the postings there weren't of any help :(

Thanks

Tony
I used the config you can find in [0] and it works.


[0]
http://wiki.openmoko.org/wiki/USB_Networking#Debian.2C_Ubuntu_and_others
 ___


but this one 'ties' it in usb0 although it connects as eth1! How can 
this work?


I also used the following entries in /etc/network/interfaces:

#freerunner3
allow-hotplug eth1
iface eth1 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 
http://192.168.0.0/24 

up echo 1  /proc/sys/net/ipv4/ip_forward 
up iptables -P FORWARD ACCEPT 
down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 
http://192.168.0.0/24 


and didn't work! Openmoko wasn't able to get an IP address at all!

get ip adress ? dont understand this.

but i had to add this two lines to my /etc/ufw/ufw.conf

ufw allow from 192.168.0.202
ufw allow to 192.168.0.202


another trial with iptables needs to load some modules too:

#!/bin/sh

MOKO=192.168.0.202

echo 1  /proc/sys/net/ipv4/ip_forward
modprobe ipt_MASQUERADE

iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32


--
Mit freundlichen Grüssen
Matthias Huber 
Kohlstattstr. 14

86459 Wollishausen
Tel: 08238-7998
LPI000181125

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking with Ubuntu 9.04

2009-10-06 Thread Cristian Gómez
Hi, What I do to connect the FreeRunner to the PC is running this script [1]
that I've made with the things listed on the wiki. To run it just type sudo
sh usb_networking.sh.

I used it on Arch Linux and Ubuntu and I think it works on every distro as
well. Any changes, suggestions are welcome. Currently it's on spanish.

Note: The script is configured for SHR so it uses the eth1 interface not the
usb0

[1] http://www.mediafire.com/download.php?zm0gtz2tyjq

/***
* Don't Worry...Be Linux
* Cristian Gómez Alvarez
* Ingeniero en Sistemas y Computación
* Universidad de Caldas
* Comunidad de Software Libre Manizales
* IEEE/WIE Student Member
* Linux User #463617
* Mi Blog: http://cristianpark.sehablalinux.com/
/


2009/10/6 Matthias Huber matthias.hu...@wollishausen.de

  Tony Berth schrieb:

 On Tue, Oct 6, 2009 at 10:00 PM, Frederik Sdun 
 frederik.s...@googlemail.com wrote:

 * Tony Berth tonybe...@googlemail.com [06.10.2009 18:06]:
  followed as described in:
 
 http://wiki.openmoko.org/wiki/USB_Networking
 
 -
 
Ubuntu 9.04 - the Jaunty Jackalope -- udev
 
 One can see /etc/udev/rules.d that a device plugged in on USB will be
 called eth1. Go to system-Administration-Network and add the
 parameters
 for eth1  static ip, address 192.168.0.200 mask 255.255.255.192 add
 your
 default gateway. Thats is all.
 
 Tested with Qi bootloader aka official MAC address of the Freerunner
 : on
 Android Koolu beta 7
 
 Carig Philippines --frank 14:11, 17 June 2009 (UTC)
 
 --
 
 and eth1 gets assigned the proper IP address. I can connect to Neo
 but
 from there I don't have any connection to the 'outside'. Please
 notice
 that resolv.conf has the correct Opendns IPs!
 
 Actually I should face the same problem as described in:
 
 http://lists.openmoko.org/nabble.html#nabble-td3119750
 
 but the postings there weren't of any help :(
 
 Thanks
 
 Tony
  I used the config you can find in [0] and it works.


 [0]
 http://wiki.openmoko.org/wiki/USB_Networking#Debian.2C_Ubuntu_and_others
  ___


 but this one 'ties' it in usb0 although it connects as eth1! How can this
 work?

 I also used the following entries in /etc/network/interfaces:

 #freerunner3
 allow-hotplug eth1
 iface eth1 inet static
 address 192.168.0.200
 netmask 255.255.255.0
 network 192.168.0.0
 up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 
 up echo 1  /proc/sys/net/ipv4/ip_forward 
 up iptables -P FORWARD ACCEPT 
 down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 

 and didn't work! Openmoko wasn't able to get an IP address at all!

 get ip adress ? dont understand this.

 but i had to add this two lines to my /etc/ufw/ufw.conf

 ufw allow from 192.168.0.202
 ufw allow to 192.168.0.202


 another trial with iptables needs to load some modules too:

 #!/bin/sh

 MOKO=192.168.0.202

 echo 1  /proc/sys/net/ipv4/ip_forward
 modprobe ipt_MASQUERADE

 iptables -I FORWARD -j ACCEPT -d ${MOKO}/32
 iptables -I FORWARD -j ACCEPT -s ${MOKO}/32
 iptables -I POSTROUTING -t nat -j MASQUERADE -s ${MOKO}/32


 --
 Mit freundlichen Grüssen
 Matthias Huber
 Kohlstattstr. 14
 86459 Wollishausen
 Tel: 08238-7998
 LPI000181125


 ___
 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: USB Networking disabled

2009-09-10 Thread arne anka
 I just posted a message on the smartphone mailing-list about a similar
 problem I have.

according to your description on smartphone-users, yours is totally  
different an issue (and i answered with a way to fix that).
you simply fell in the well known qi/udev trap, while the op according to  
his description does not get any cdc ether device at all.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking disabled

2009-09-10 Thread arne anka
- is cdc-ether built-in or a module?
- how do you make sure it is not recognized? syslog?
- das the log say anything at all about usb?
- what exactly are you seeing when pluggin in the fr on the host side?

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking disabled

2009-09-10 Thread Neil M. Stewart
I now have it working. I changed the USB networking related features
including cdc-ether as built-in, as opposed to modules, which was the
original configuration.

On Thu, Sep 10, 2009 at 4:31 AM, arne anka openm...@ginguppin.de wrote:
 - is cdc-ether built-in or a module?
 - how do you make sure it is not recognized? syslog?
 - das the log say anything at all about usb?
 - what exactly are you seeing when pluggin in the fr on the host side?

 ___
 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: USB Networking disabled

2009-09-09 Thread Stefan Monnier
 I recently compile the latest andy-tracking branch of the kernel
 (GTA02_mystable-a3587e4ed77974ad), however the usb networking feature
 is no longer operational.
 Prior to installing the new kernel, my Linux system would recognize
 the Neo Freerunner as a CDC Ethernet device, now it no longer
 recognizes the device once it is attached.
 I used the gta02_moredrivers_defconfig in the build process. Does
 anyone know what might be causing this issue?
 Thanks in advance for you help.

I just posted a message on the smartphone mailing-list about a similar
problem I have.  In my case the USB netowkring fails when I boot with
Qi, but works when I boot with U-Boot.


Stefan


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking disabled

2009-09-09 Thread Rask Ingemann Lambertsen
On Wed, Sep 09, 2009 at 03:33:50PM -0400, Stefan Monnier wrote:

 I just posted a message on the smartphone mailing-list about a similar
 problem I have.  In my case the USB netowkring fails when I boot with
 Qi, but works when I boot with U-Boot.

   IIRC, Qi adds kernel parameters in an attempt to set the Ethernet address
used by the Freerunner's CDC Ethernet device. If you have the 'lsusb'
command on the system you're connecting to the Freerunner, what does it say?

-- 
Rask Ingemann Lambertsen
Danish law requires addresses in e-mail to be logged and stored for a year

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking MAC regression (aka the usb0 - eth0 change)

2009-05-24 Thread Nicolas Cavallari
 Johny Tenfinger wrote :
 On Sat, May 23, 2009 at 17:05, Nicolas Cavallari batch...@free.fr wrote:
 This worked fine during the usb0 phase. But since the distro started using 
 the official
 MAC address, This wouldn't work anymore.
 Which distro? In SHR-unstable it should be fixed for long time, but in
 others, where kernel is using arguments passed by Qi (dunno if Om2009
 is using Qi or SHR way for settings MAC address...) it isn't, because
 of bug in Qi.
 On Sat, May 23, 2009 at 19:33, Nicolas Cavallari batch...@free.fr wrote:
 It's the latest SHR Testing. 
 but my Qi installation may not be up to date...

Screw that, Qi was up to date.

Johny Tenfinger wrote :
 
 Try latest SHR-unstable. It should be really better than -testing, and
 it should have it fixed (not depending to bootloader).

From what i saw, unstable does just increment the host mac adress if the 
device and the host mac are
the same, just like Paul Fertser's Qi patch on the kernel@ mailling list.

I don't want to try SHR-unstable right now (i use my FR as my main phone), but 
hacking the
g_ether.sh script to do the same thing also fix the problem.


I also created a ticket on trac, as suggested :
https://docs.openmoko.org/trac/ticket/2290

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking MAC regression (aka the usb0 - eth0 change)

2009-05-24 Thread Johny Tenfinger
On Sun, May 24, 2009 at 16:34, Nicolas Cavallari batch...@free.fr wrote:
 I don't want to try SHR-unstable right now (i use my FR as my main phone), 
 but hacking the
 g_ether.sh script to do the same thing also fix the problem.

Well, for me SHR-unstable is more usable as daily phone than
SHR-testing, but that's only my opinion and off-topic :)

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking MAC regression (aka the usb0 - eth0 change)

2009-05-23 Thread Johny Tenfinger
On Sat, May 23, 2009 at 17:05, Nicolas Cavallari batch...@free.fr wrote:
 This worked fine during the usb0 phase. But since the distro started using 
 the official
 MAC address, This wouldn't work anymore.

Which distro? In SHR-unstable it should be fixed for long time, but in
others, where kernel is using arguments passed by Qi (dunno if Om2009
is using Qi or SHR way for settings MAC address...) it isn't, because
of bug in Qi.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking MAC regression (aka the usb0 - eth0 change)

2009-05-23 Thread Nicolas Cavallari
Johny Tenfinger a écrit :
 On Sat, May 23, 2009 at 17:05, Nicolas Cavallari batch...@free.fr wrote:
 This worked fine during the usb0 phase. But since the distro started using 
 the official
 MAC address, This wouldn't work anymore.
 
 Which distro? In SHR-unstable it should be fixed for long time, but in
 others, where kernel is using arguments passed by Qi (dunno if Om2009
 is using Qi or SHR way for settings MAC address...) it isn't, because
 of bug in Qi.

It's the latest SHR Testing. but my Qi installation may not be up to date...

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking MAC regression (aka the usb0 - eth0 change)

2009-05-23 Thread Johny Tenfinger
On Sat, May 23, 2009 at 19:33, Nicolas Cavallari batch...@free.fr wrote:
 Johny Tenfinger a écrit :
 On Sat, May 23, 2009 at 17:05, Nicolas Cavallari batch...@free.fr wrote:
 This worked fine during the usb0 phase. But since the distro started using 
 the official
 MAC address, This wouldn't work anymore.

 Which distro? In SHR-unstable it should be fixed for long time, but in
 others, where kernel is using arguments passed by Qi (dunno if Om2009
 is using Qi or SHR way for settings MAC address...) it isn't, because
 of bug in Qi.

 It's the latest SHR Testing. but my Qi installation may not be up to date...

Try latest SHR-unstable. It should be really better than -testing, and
it should have it fixed (not depending to bootloader).

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking MAC regression (aka the usb0 - eth0 change)

2009-05-23 Thread Paul Fertser
Hi,

Nicolas Cavallari batch...@free.fr writes:
 For a while, I used to use USB networking to connect my FR to the interwebs.
[snip]
 The bridge fails because it consider the host mac address to be a local mac 
 (brctl showmacs) and
 so ignore any host with the same mac. Changing the host mac address (with 
 ifconfig ethXXX hw ether)
 solves the problem, but it clearly not a acceptable solution.

Thanks for reporting. I've just sent a patch to the kernel ML that
should fix the issue.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking now creates eth1 on host

2009-05-15 Thread Paul Fertser
reznor schumi_8_2...@gmx.de writes:
 You just have to know what's going on and then it's easy. That information
 should have been distributed a few months ago and that way that everyone
 gets it who uses Qi. At the fyp forums nobody seemed to know.

You see? Fyp community is disconnected because they use forums, QOD.

Here [1] the change was described in all details along with
justifications. Also the wiki page was updated accordingly.

And to be honest i just can't understand why it created so much
confusion because it's plain obvious from reading host's dmesg right
after inserting FR, really.

[1] http://lists.openmoko.org/pipermail/devel/2009-April/005384.html

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking now creates eth1 on host (was: Re: [neovento 5] applications!)

2009-05-14 Thread reznor


Paul Fertser wrote:
 
 Why do you suggest this instead of using the correct method?!
 
Why didn't you suggest the correct method before, though you knew the
correct method all the time???


Paul Fertser wrote:
 
 The guy obviously got eth1 on host. Every time. He should have used it
 instead of finding older incorrectly working versions of bootloaders.
 
 The reason is simple: since Qi was fixed to properly provide
 factory-configured MAC address for the usb networking interface, it's
 detected on the host as it should, every time udev sees that device
 it'll assign the same static interface to it (in the simplest case
 it'll be eth1), that's the main improvement actually! 
Ok, Ill try that.


Paul Fertser wrote:
 
 I wonder why you neovento guys don't read kernel mailing list, devel
 mailing list where this was elaborated in details, why you never come
 to IRC to discuss low-level issues etc.
Lack of motivation and time. This is only some hobby, we spend as much time
in it as we consider being appropriate. You guys can just ignore the
neovento guys. So what's the problem?
As long there won't be any usable distributions for my freerunner, I'll make
my own. Easy, right?
-- 
View this message in context: 
http://n2.nabble.com/-neovento-5--applications%21-tp2881940p2889485.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: USB networking now creates eth1 on host

2009-05-14 Thread Paul Fertser
reznor schumi_8_2...@gmx.de writes:
 Paul Fertser wrote:
 
 Why do you suggest this instead of using the correct method?!
 
 Why didn't you suggest the correct method before, though you knew the
 correct method all the time???

Sorry, i was a bit busy and the thread called neovento apps wasn't
of the most interest to me so i've read it a bit later, just
that. Moreover, the problem is obvious from the host's dmesg.

 I wonder why you neovento guys don't read kernel mailing list, devel
 mailing list where this was elaborated in details, why you never come
 to IRC to discuss low-level issues etc.
 Lack of motivation and time. This is only some hobby, we spend as much time
 in it as we consider being appropriate. You guys can just ignore the
 neovento guys. So what's the problem?
 As long there won't be any usable distributions for my freerunner, I'll make
 my own. Easy, right?

Heh, my remark wasn't meant to be offensive, take it easy ;)

The problem is that i feel neovento guys are separating from the
developers community by not using our mailing lists and IRC. I've
heard you're using some web-forum (is it really true?) i can't imagine
you'll get any help from the other devs using such a crappy method.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking now creates eth1 on host (was: Re: [neovento 5] applications!)

2009-05-14 Thread arne anka
 Why do you suggest this instead of using the correct method?!

 Why didn't you suggest the correct method before, though you knew the
 correct method all the time???

it was suggested -- at least once and i repeated it after seeing that  
apparently no one cared to read that.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking now creates eth1 on host

2009-05-14 Thread reznor


Paul Fertser wrote:
 
 Heh, my remark wasn't meant to be offensive, take it easy ;)
 
 The problem is that i feel neovento guys are separating from the
 developers community by not using our mailing lists and IRC. I've
 heard you're using some web-forum (is it really true?) i can't imagine
 you'll get any help from the other devs using such a crappy method.
 
neovento is not such a professional distribution like all the others like
SHR, Android, OM and so on. Additionally it is quite new. I started it just
about four months ago as a one man fun thing. That it actually turned into
something useful for some people is nice. I think you have a completely
wrong idea of the whole thing.

We have one thread on the fyp forum, that's right. It's just for some
communication within that community. I actually don't know what's crappy on
that and why we need so much help from the devs? When there were issues I
just mailed into the debianonfreerunner mailinglist and got response.

Excuse me, but for not wanting to be offensive you are writing some really
arrogant crap.




-- 
View this message in context: 
http://n2.nabble.com/-neovento-5--applications%21-tp2881940p2889594.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


Every web-forum sucks by definition, isn't it obvious? (was: Re: USB networking now creates eth1 on host)

2009-05-14 Thread Paul Fertser
reznor schumi_8_2...@gmx.de writes:
 Excuse me, but for not wanting to be offensive you are writing some really
 arrogant crap.

:D

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking now creates eth1 on host

2009-05-14 Thread reznor

Works with Qi. 
You just have to know what's going on and then it's easy. That information
should have been distributed a few months ago and that way that everyone
gets it who uses Qi. At the fyp forums nobody seemed to know.

-- 
View this message in context: 
http://n2.nabble.com/-neovento-5--applications%21-tp2881940p2903754.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: USB networking now creates eth1 on host

2009-05-14 Thread Nelson Castillo
On Thu, May 14, 2009 at 5:35 PM, reznor schumi_8_2...@gmx.de wrote:

 Works with Qi.
 You just have to know what's going on and then it's easy. That information
 should have been distributed a few months ago and that way that everyone
 gets it who uses Qi. At the fyp forums nobody seemed to know.

Hello.

Check this:

http://lists.openmoko.org/pipermail/devel/2009-April/005384.html

Nelson.-

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB networking now creates eth1 on host

2009-05-14 Thread reznor

22. April, that's only 3-4 weeks ago, a bit late. Some people just stopped
using Qi because of that months ago and lost interest also, just like me.
But finally the message arrives. -.-



Nelson Castillo-2 wrote:
 
 On Thu, May 14, 2009 at 5:35 PM, reznor schumi_8_2...@gmx.de wrote:

 Works with Qi.
 You just have to know what's going on and then it's easy. That
 information
 should have been distributed a few months ago and that way that everyone
 gets it who uses Qi. At the fyp forums nobody seemed to know.
 
 Hello.
 
 Check this:
 
 http://lists.openmoko.org/pipermail/devel/2009-April/005384.html
 
 Nelson.-
 
 ___
 Openmoko community mailing list
 community@lists.openmoko.org
 http://lists.openmoko.org/mailman/listinfo/community
 
 

-- 
View this message in context: 
http://n2.nabble.com/-neovento-5--applications%21-tp2881940p2904213.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: USB Networking

2008-11-07 Thread Stefan Monnier
 With Ubuntu 8.04 and 8.10 I've had 100% success on four or five different
 systems with:

 auto usb0
 iface usb0 inet static
 address 192.168.0.201
 netmask 255.255.255.252
 post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.202
 post-up iptables -I PREROUTING -i usb0 -p udp --dport 53 -j DNAT --to
 192.168.0.254
 post-up echo 1  /proc/sys/net/ipv4/ip_forward
 post-up iptables -P FORWARD ACCEPT
 pre-down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.202
 pre-down iptables -D PREROUTING -i usb0 -p udp --dport 53 -j DNAT --to
 192.168.0.254


 in /etc/network/interfaces, and the fix noted on the wiki at
 http://wiki.openmoko.org/wiki/Usb_networking#Ubuntu_Issues

If you use allow-hotplug instead of auto, it should work without
needing any fix.


Stefan


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-06 Thread Tony Berth
Indeed that was the problem. 'allow-hotplug' instead of 'auto' is the
solution! PLEASE correct the WIKI asap!

Thanks for your prompt support

Cheers

Tony

On Wed, Nov 5, 2008 at 10:13 PM, joezeewails [EMAIL PROTECTED] wrote:

 Stefan Monnier wrote:
 
  That's probably not right.  You probably want to try allow-hotplug
  ubs0 instead.  auto means to do it at boot time and it may just fail
  if (for some reason) the usb0 interface is not yet created.
 
 
  Stefan
 
 I could confirm this.
 It doesn't work with auto usb0 with allow-hotplug usb0 it works just
 fine.
 Every time I plug the Freerunner in my debian etch it brings the
 interface up.
 I use the version from the wiki with a extra freerunner script.

 My entry in /etc/network/interfaces:

 #freerunner
 allow-hotplug usb0
 iface usb0 inet static
 address 192.168.0.200
 netmask 255.255.255.0
 post-up /etc/network/freerunner start
 pre-down /etc/network/freerunner stop



 Someone should correct the wiki, should I?


 Cheers,
 Joe


 ___
 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: USB Networking

2008-11-06 Thread Pander
Any ideas regarding (semi)automatic configuration via
https://bugs.launchpad.net/ubuntu/+bug/289548 are also welcome.

On Thu, November 6, 2008 09:28, Tony Berth wrote:
 Indeed that was the problem. 'allow-hotplug' instead of 'auto' is the
 solution! PLEASE correct the WIKI asap!

 Thanks for your prompt support

 Cheers

 Tony

 On Wed, Nov 5, 2008 at 10:13 PM, joezeewails [EMAIL PROTECTED] wrote:

 Stefan Monnier wrote:
 
  That's probably not right.  You probably want to try allow-hotplug
  ubs0 instead.  auto means to do it at boot time and it may just
 fail
  if (for some reason) the usb0 interface is not yet created.
 
 
  Stefan
 
 I could confirm this.
 It doesn't work with auto usb0 with allow-hotplug usb0 it works just
 fine.
 Every time I plug the Freerunner in my debian etch it brings the
 interface up.
 I use the version from the wiki with a extra freerunner script.

 My entry in /etc/network/interfaces:

 #freerunner
 allow-hotplug usb0
 iface usb0 inet static
 address 192.168.0.200
 netmask 255.255.255.0
 post-up /etc/network/freerunner start
 pre-down /etc/network/freerunner stop



 Someone should correct the wiki, should I?


 Cheers,
 Joe


 ___
 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




___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-06 Thread Max Giesbert
@Tone Berth: The wiki is a community thing. You should update it yourself.

Tony Berth schrieb:
 Indeed that was the problem. 'allow-hotplug' instead of 'auto' is the
 solution! PLEASE correct the WIKI asap!
 
 Thanks for your prompt support
 
 Cheers
 
 Tony
 
 On Wed, Nov 5, 2008 at 10:13 PM, joezeewails [EMAIL PROTECTED]
 mailto:[EMAIL PROTECTED] wrote:
 
 Stefan Monnier wrote:
 
  That's probably not right.  You probably want to try allow-hotplug
  ubs0 instead.  auto means to do it at boot time and it may just
 fail
  if (for some reason) the usb0 interface is not yet created.
 
 
  Stefan
 
 I could confirm this.
 It doesn't work with auto usb0 with allow-hotplug usb0 it works just
 fine.
 Every time I plug the Freerunner in my debian etch it brings the
 interface up.
 I use the version from the wiki with a extra freerunner script.
 
 My entry in /etc/network/interfaces:
 
 #freerunner
 allow-hotplug usb0
 iface usb0 inet static
 address 192.168.0.200 http://192.168.0.200
 netmask 255.255.255.0 http://255.255.255.0
 post-up /etc/network/freerunner start
 pre-down /etc/network/freerunner stop
 
 
 
 Someone should correct the wiki, should I?
 
 
 Cheers,
 Joe
 
 
 ___
 Openmoko community mailing list
 community@lists.openmoko.org mailto: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

-- 
exactt technology
Dipl. Inf. (FH) Max Giesbert

Schießstättstr. 16  T: +49 17 75 07 53 44
D-80339 München F: +49 89 1 22 21 97 02

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-06 Thread Denis Johnson
On Thu, Nov 6, 2008 at 9:06 PM, Tony Berth [EMAIL PROTECTED] wrote:
 the wiki posted solution was tested by myself on a the currebt debian and
 did work! Are you using the same environment?

I believe so, I'm using Ubuntu 8.10 but have had this problem since 8.04.

 On Thu, Nov 6, 2008 at 10:46 AM, Denis Johnson [EMAIL PROTECTED]
 wrote:

 I have had this setting for months it does not work for me.

 Whenever I want to connect my FR, I must first plug it in into the usb
 and then run the following script which someone once posted here or on
 the #openmoko irc. Until I run ths script I cannot ping and hence ssh
 into the FR. Unfortunately I don't know enough to integrate and
 automate what the script does into my interfaces file. If someone can
 shed some more light, it would be appreciated:

 --
 #!/bin/sh
 # Enables Hostside USB-Networking for neo
 ifconfig usb0 down
 ifconfig usb0 192.168.0.200 netmask 255.255.255.0 up
 iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
 echo 1  /proc/sys/net/ipv4/ip_forward
 iptables -P FORWARD ACCEPT
 route add -host 192.168.0.202 gw 192.168.0.200
 route -n | grep -e Destination -e usb0
 --

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-06 Thread Tony Berth
done!

Thanks

On Thu, Nov 6, 2008 at 11:01 AM, Max Giesbert [EMAIL PROTECTED] wrote:

 @Tone Berth: The wiki is a community thing. You should update it yourself.

 Tony Berth schrieb:
  Indeed that was the problem. 'allow-hotplug' instead of 'auto' is the
  solution! PLEASE correct the WIKI asap!
 
  Thanks for your prompt support
 
  Cheers
 
  Tony
 
  On Wed, Nov 5, 2008 at 10:13 PM, joezeewails [EMAIL PROTECTED]
  mailto:[EMAIL PROTECTED] wrote:
 
  Stefan Monnier wrote:
  
   That's probably not right.  You probably want to try allow-hotplug
   ubs0 instead.  auto means to do it at boot time and it may just
  fail
   if (for some reason) the usb0 interface is not yet created.
  
  
   Stefan
  
  I could confirm this.
  It doesn't work with auto usb0 with allow-hotplug usb0 it works
 just
  fine.
  Every time I plug the Freerunner in my debian etch it brings the
  interface up.
  I use the version from the wiki with a extra freerunner script.
 
  My entry in /etc/network/interfaces:
 
  #freerunner
  allow-hotplug usb0
  iface usb0 inet static
  address 192.168.0.200 http://192.168.0.200
  netmask 255.255.255.0 http://255.255.255.0
  post-up /etc/network/freerunner start
  pre-down /etc/network/freerunner stop
 
 
 
  Someone should correct the wiki, should I?
 
 
  Cheers,
  Joe
 
 
  ___
  Openmoko community mailing list
  community@lists.openmoko.org mailto: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

 --
 exactt technology
 Dipl. Inf. (FH) Max Giesbert

 Schießstättstr. 16  T: +49 17 75 07 53 44
 D-80339 München F: +49 89 1 22 21 97 02

 ___
 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: USB Networking

2008-11-06 Thread Tony Berth
the wiki posted solution was tested by myself on a the currebt debian and
did work! Are you using the same environment?

Cheers

Tony

On Thu, Nov 6, 2008 at 10:46 AM, Denis Johnson [EMAIL PROTECTED]wrote:

 I have had this setting for months it does not work for me.

 Whenever I want to connect my FR, I must first plug it in into the usb
 and then run the following script which someone once posted here or on
 the #openmoko irc. Until I run ths script I cannot ping and hence ssh
 into the FR. Unfortunately I don't know enough to integrate and
 automate what the script does into my interfaces file. If someone can
 shed some more light, it would be appreciated:

 --
 #!/bin/sh
 # Enables Hostside USB-Networking for neo
 ifconfig usb0 down
 ifconfig usb0 192.168.0.200 netmask 255.255.255.0 up
 iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
 echo 1  /proc/sys/net/ipv4/ip_forward
 iptables -P FORWARD ACCEPT
 route add -host 192.168.0.202 gw 192.168.0.200
 route -n | grep -e Destination -e usb0
 --

 cheers Denis

 On Thu, Nov 6, 2008 at 7:13 AM, joezeewails [EMAIL PROTECTED] wrote:
 
  Stefan Monnier wrote:
  
   That's probably not right.  You probably want to try allow-hotplug
   ubs0 instead.  auto means to do it at boot time and it may just fail
   if (for some reason) the usb0 interface is not yet created.
  
  
   Stefan
  
  I could confirm this.
  It doesn't work with auto usb0 with allow-hotplug usb0 it works just
  fine.
  Every time I plug the Freerunner in my debian etch it brings the
  interface up.
  I use the version from the wiki with a extra freerunner script.
 
  My entry in /etc/network/interfaces:
 
  #freerunner
  allow-hotplug usb0
  iface usb0 inet static
  address 192.168.0.200
  netmask 255.255.255.0
  post-up /etc/network/freerunner start
  pre-down /etc/network/freerunner stop
 
 
 
  Someone should correct the wiki, should I?
 
 
  Cheers,
  Joe
 
 
  ___
  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

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


RE: USB Networking

2008-11-06 Thread Matthias Camenzind
I had also some problems with the Usb networking with ubuntu 8.04. But i could 
solve it with this: ifconfig usb0 192.168.0.200 netmask 255.255.255.0 
I had to enter it every time after i connected FR with my Computer or I 
rebooted the FR. But it worked fine. I found this solution in the Getting 
Started Guide for Neo 1973.
Today network is automatically set up after connecting but today I don't know 
exactly what I did.

-Original Message-
From: Denis Johnson [EMAIL PROTECTED]
Sent: 11/6/2008 1:06:23 PM
To: List for Openmoko community discussion community@lists.openmoko.org
Subject: Re: USB Networking


On Thu, Nov 6, 2008 at 9:06 PM, Tony Berth [EMAIL PROTECTED] wrote:
 the wiki posted solution was tested by myself on a the currebt debian and
 did work! Are you using the same environment?

I believe so, I'm using Ubuntu 8.10 but have had this problem since 8.04.

 On Thu, Nov 6, 2008 at 10:46 AM, Denis Johnson [EMAIL PROTECTED]
 wrote:

 I have had this setting for months it does not work for me.

 Whenever I want to connect my FR, I must first plug it in into the usb
 and then run the following script which someone once posted here or on
 the #openmoko irc. Until I run ths script I cannot ping and hence ssh
 into the FR. Unfortunately I don't know enough to integrate and
 automate what the script does into my interfaces file. If someone can
 shed some more light, it would be appreciated:

 --
 #!/bin/sh
 # Enables Hostside USB-Networking for neo
 ifconfig usb0 down
 ifconfig usb0 192.168.0.200 netmask 255.255.255.0 up
 iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
 echo 1  /proc/sys/net/ipv4/ip_forward
 iptables -P FORWARD ACCEPT
 route add -host 192.168.0.202 gw 192.168.0.200
 route -n | grep -e Destination -e usb0
 --

___
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: USB Networking

2008-11-06 Thread Joel Newkirk
On Thu, 6 Nov 2008 17:54:09 +, Matthias Camenzind 
[EMAIL PROTECTED] wrote:
 I had also some problems with the Usb networking with ubuntu 8.04. But i
 could solve it with this: ifconfig usb0 192.168.0.200 netmask
255.255.255.0
 I had to enter it every time after i connected FR with my Computer or I
 rebooted the FR. But it worked fine. I found this solution in the Getting
 Started Guide for Neo 1973.
 Today network is automatically set up after connecting but today I don't
 know exactly what I did.
 
 -Original Message-
 From: Denis Johnson [EMAIL PROTECTED]
 Sent: 11/6/2008 1:06:23 PM
 To: List for Openmoko community discussion community@lists.openmoko.org
 Subject: Re: USB Networking
 
 
 On Thu, Nov 6, 2008 at 9:06 PM, Tony Berth [EMAIL PROTECTED]
 wrote:
 the wiki posted solution was tested by myself on a the currebt debian
 and
 did work! Are you using the same environment?
 
 I believe so, I'm using Ubuntu 8.10 but have had this problem since 8.04.

With Ubuntu 8.04 and 8.10 I've had 100% success on four or five different
systems with:

auto usb0
iface usb0 inet static
address 192.168.0.201
netmask 255.255.255.252
post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.202
post-up iptables -I PREROUTING -i usb0 -p udp --dport 53 -j DNAT --to
192.168.0.254
post-up echo 1  /proc/sys/net/ipv4/ip_forward
post-up iptables -P FORWARD ACCEPT
pre-down iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.202
pre-down iptables -D PREROUTING -i usb0 -p udp --dport 53 -j DNAT --to
192.168.0.254


in /etc/network/interfaces, and the fix noted on the wiki at
http://wiki.openmoko.org/wiki/Usb_networking#Ubuntu_Issues

NOTES: I use 192.168.0.201 on host and 192.168.0.202 on FR, with netmask of
/30 or 255.255.255.252 - to match 'standard' {dumb as I feel it is}
FreeRunner network setup, use 192.168.0.200 on host with 255.255.255.0 as
netmask.  Also, 192.168.0.254 is my local DNS server, hence the DNAT rule
forwarding DNS requests there (which I don't actually need anymore since I
use local dnscache on the FR).  In fact, none of the post-up and pre-down
parts affect me anymore as I utilize a static permanent ruleset to
accomplish this, so I leave them all commented out.

(and yes, 'auto' DOES work, provided the fix linked above is employed, and
works without it some times)

j



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-05 Thread Stefan Monnier
 Tony == Tony Berth [EMAIL PROTECTED]
 Edit /etc/network/interfaces and add:
 auto usb0

That's probably not right.  You probably want to try allow-hotplug
ubs0 instead.  auto means to do it at boot time and it may just fail
if (for some reason) the usb0 interface is not yet created.


Stefan




___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-05 Thread joezeewails
Stefan Monnier wrote:

 That's probably not right.  You probably want to try allow-hotplug
 ubs0 instead.  auto means to do it at boot time and it may just fail
 if (for some reason) the usb0 interface is not yet created.


 Stefan
   
I could confirm this.
It doesn't work with auto usb0 with allow-hotplug usb0 it works just
fine.
Every time I plug the Freerunner in my debian etch it brings the
interface up.
I use the version from the wiki with a extra freerunner script.

My entry in /etc/network/interfaces:

#freerunner
allow-hotplug usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
post-up /etc/network/freerunner start
pre-down /etc/network/freerunner stop



Someone should correct the wiki, should I?


Cheers,
Joe


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking

2008-11-05 Thread abatrour

Also double check to make sure your LAN ip address isn't in the 192.168.0.*
range.
I've wasted too much time making that mistake.
-- 
View this message in context: 
http://n2.nabble.com/USB-Networking-tp1461467p1463175.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: USB Networking

2008-11-05 Thread Joel Newkirk
On Wed, 5 Nov 2008 18:42:33 -0800 (PST), abatrour [EMAIL PROTECTED]
wrote:
 
 Also double check to make sure your LAN ip address isn't in the
 192.168.0.*
 range.
 I've wasted too much time making that mistake.
 --
 View this message in context:
 http://n2.nabble.com/USB-Networking-tp1461467p1463175.html
 Sent from the Openmoko Community mailing list archive at Nabble.com.

Which is why my desktops (home and work) are set to use 192.168.0.201/30,
and the FreeRunner is set to 192.168.0.202/30. (on first SSH after flash I
change the FR settings for subnet, gateway and DNS)  Better would be to go
entirely 'elsewhere' within private IP address blocks, like 10.20.30.1/24
or something, but since the default IP on a FreeRunner after flashing is
always 192.168.0.202/24, I gave ground and kept it there, just narrowed the
subnet to /30 (two usable IPs, 192.168.0.201-202) so that only
102.168.0.200-203 are unworkable on my LAN.

j



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking vs. iptables

2008-09-19 Thread Christian Weßel
Hello,

first I correct the DNS address at the both DNATs at the server side:
[EMAIL PROTECTED] backup]# iptables -L -t nat --line-numbers -n -v
Chain PREROUTING (policy ACCEPT 2829 packets, 171K bytes)
num   pkts bytes target prot opt in out source
destination 
10 0 DNAT   tcp  --  *  *   192.168.0.202
192.168.0.200   tcp dpt:53 to:212.6.108.140 
2   20  1248 DNAT   udp  --  *  *   192.168.0.202
192.168.0.200   udp dpt:53 to:212.6.108.140 

Chain POSTROUTING (policy ACCEPT 9133 packets, 641K bytes)
num   pkts bytes target prot opt in out source
destination 
1   59  6086 MASQUERADE  all  --  *  *   192.168.0.0/24
0.0.0.0/0   

But I recognize no pos. At the FR I have still the same results:
[EMAIL PROTECTED]:~# cat /etc/resolv.conf 
nameserver 192.168.0.200
[EMAIL PROTECTED]:~# nslookup www.google.com
Server:192.168.0.200
Address 1: 192.168.0.200

nslookup: can't resolve 'www.google.com'

I checked the filter table, I see no mistake. The most are standard
rules by RH/FC. The input and the forward chains are affect no traffic,
except the listed IPs:22 in private chain 'RH-Firewall-1-INPUT'.

on server:
[EMAIL PROTECTED] backup]# iptables -L -t nat --line-numbers -n -v
Chain PREROUTING (policy ACCEPT 2812 packets, 170K bytes)
num   pkts bytes target prot opt in out source
destination 
10 0 DNAT   tcp  --  *  *   192.168.0.202
192.168.0.200   tcp dpt:53 to:212.6.108.140 
2   20  1248 DNAT   udp  --  *  *   192.168.0.202
192.168.0.200   udp dpt:53 to:212.6.108.140 

Chain POSTROUTING (policy ACCEPT 9082 packets, 638K bytes)
num   pkts bytes target prot opt in out source
destination 
1   59  6086 MASQUERADE  all  --  *  *   192.168.0.0/24
0.0.0.0/0   

Chain OUTPUT (policy ACCEPT 9097 packets, 640K bytes)
num   pkts bytes target prot opt in out source
destination 
[EMAIL PROTECTED] backup]# iptables -L --line-numbers -n -v
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
num   pkts bytes target prot opt in out source
destination 
1 592K  375M RH-Firewall-1-INPUT  all  --  *  *   0.0.0.0/0
0.0.0.0/0   

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
num   pkts bytes target prot opt in out source
destination 
1  701 45828 RH-Firewall-1-INPUT  all  --  *  *   0.0.0.0/0
0.0.0.0/0   

Chain OUTPUT (policy ACCEPT 613K packets, 261M bytes)
num   pkts bytes target prot opt in out source
destination 

Chain RH-Firewall-1-INPUT (2 references)
num   pkts bytes target prot opt in out source
destination 
1   18  1488 DROP   tcp  --  *  *   200.148.247.20
0.0.0.0/0   tcp dpt:22 
2   23  1256 DROP   tcp  --  *  *   85.114.135.61
0.0.0.0/0   tcp dpt:22 
3   19  1420 DROP   tcp  --  *  *   82.117.193.162
0.0.0.0/0   tcp dpt:22 
4   16  1292 DROP   tcp  --  *  *   218.240.15.45
0.0.0.0/0   tcp dpt:22 
5   19  1552 DROP   tcp  --  *  *   219.143.219.129
0.0.0.0/0   tcp dpt:22 
6   21  1668 DROP   tcp  --  *  *   211.20.200.24
0.0.0.0/0   tcp dpt:22 
7   23  1836 DROP   tcp  --  *  *   64.152.73.79
0.0.0.0/0   tcp dpt:22 
8   19  1500 DROP   tcp  --  *  *   203.112.151.49
0.0.0.0/0   tcp dpt:22 
92   120 DROP   tcp  --  *  *   91.121.162.172
0.0.0.0/0   tcp dpt:22 
10  22  1732 DROP   tcp  --  *  *   211.157.110.226
0.0.0.0/0   tcp dpt:22 
11  17  1356 DROP   tcp  --  *  *   219.94.180.143
0.0.0.0/0   tcp dpt:22 
12  16  1296 DROP   tcp  --  *  *   200.196.51.29
0.0.0.0/0   tcp dpt:22 
13  20  1536 DROP   tcp  --  *  *   222.221.12.13
0.0.0.0/0   tcp dpt:22 
14  20  2800 DROP   tcp  --  *  *   194.165.132.66
0.0.0.0/0   tcp dpt:22 
15  21  1668 DROP   tcp  --  *  *   58.253.67.58
0.0.0.0/0   tcp dpt:22 
16  17  3048 DROP   tcp  --  *  *   91.112.122.242
0.0.0.0/0   tcp dpt:22 
17  19  1840 DROP   tcp  --  *  *   125.206.243.126
0.0.0.0/0   tcp dpt:22 
18   0 0 DROP   tcp  --  *  *   72.29.77.144
0.0.0.0/0   tcp dpt:22 
19  20  1636 DROP   tcp  --  *  *   59.42.177.139
0.0.0.0/0   tcp dpt:22 
20  18  1316 DROP   tcp  --  *  *   212.14.37.2
0.0.0.0/0   tcp dpt:22 
21246K  210M ACCEPT all  --  lo *   0.0.0.0/0
0.0.0.0/0   
22 898 78034 ACCEPT icmp --  *  *   0.0.0.0/0
0.0.0.0/0   icmp type 255 
23   0 0 ACCEPT esp  --  *  *   

Re: USB Networking vs. iptables

2008-09-19 Thread Christian Weßel
Am Freitag, den 19.09.2008, 07:35 -0400 schrieb Joel Newkirk:
 Try iptables -I RH-Firewall-1-INPUT -s 192.168.0.202 -j ACCEPT, or the
 same rule inserted at the top of INPUT and FORWARD chains.

I will try.

 RH-Firewall-1-INPUT blocks SSH from various specific IPs,  then accepts
 only very limited specific connections, including ICMP,http,https,ssh,CUPS
 and ipsec but NOT including DNS...  

That's right, but at the end if no rules of the chain affected, the
police of the chain will affect. And the default police is ACCEPT. So, I
guess that means that DNS is not blocked.

 Lack of a rule accepting DNS in INPUT
 keeps you from doing DNS lookups at 192.168.0.201, lack of a rule accepting
 DNS in FORWARD keeps you from doing DNS lookups at any other host.

I will try to add DNS to the private chain.
-- 

mfg/br, christian

Flurstraße 14
29640 Schneverdingen
Germany

E-Mail: [EMAIL PROTECTED]
Telefon: +49 5193 97 14 95
Mobile:  +49 171 357 59 57
http://wesselch.homelinux.org


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking vs. iptables

2008-09-19 Thread Christian Weßel
iptables -I RH-Firewall-1-INPUT -s 192.168.0.202 -j ACCEPT

That's it. Now I am able to install Debian by following wiki guide
http://wiki.debian.org/DebianOnFreeRunner

Thanx a lot.

Am Freitag, den 19.09.2008, 07:35 -0400 schrieb Joel Newkirk:
 Try iptables -I RH-Firewall-1-INPUT -s 192.168.0.202 -j ACCEPT, or the
 same rule inserted at the top of INPUT and FORWARD chains.
-- 

mfg/br, christian weßel

Flurstraße 14
29640 Schneverdingen
Germany

E-Mail: [EMAIL PROTECTED]
Telefon: +49 5193 97 14 95
Mobile:  +49 171 357 59 57
http://wesselch.homelinux.org


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking vs. iptables

2008-09-19 Thread Joel Newkirk
On Fri, 19 Sep 2008 16:21:13 +, Christian Weßel [EMAIL PROTECTED]
wrote:
 iptables -I RH-Firewall-1-INPUT -s 192.168.0.202 -j ACCEPT
 
 That's it. Now I am able to install Debian by following wiki guide
 http://wiki.debian.org/DebianOnFreeRunner
 
 Thanx a lot.
 
 Am Freitag, den 19.09.2008, 07:35 -0400 schrieb Joel Newkirk:
 Try iptables -I RH-Firewall-1-INPUT -s 192.168.0.202 -j ACCEPT, or the
 same rule inserted at the top of INPUT and FORWARD chains.


You're most welcome.  The one problem with your reasoning regarding the
default policy of ACCEPT is that the last rule in the RH-Firewall-1-INPUT
chain is a 'drop all' rule...  Every RedHat/Fedora/CentOS box I've ever set
up nearly the first thing I do is delete the default firewall and construct
my own - I don't like the way they structure theirs.  IMHO best practice
(and clearest logic) is to enable a DROP policy on INPUT and FORWARD
chains, and add explicit ACCEPT rules for desired traffic. 

j



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking vs. iptables

2008-09-18 Thread Dennis Ferron
Instead of this:

tables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200
--dport domain -j DNAT --to-destination 192.168.0.1
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200
--dport domain -j DNAT --to-destination 192.168.0.1

Did you do/would you try this (on your server):

tables -t nat -A PREROUTING -p tcp -s 192.168.0.202 -d 192.168.0.200
--dport domain -j DNAT --to-destination 192.168.1.254
iptables -t nat -A PREROUTING -p udp -s 192.168.0.202 -d 192.168.0.200
--dport domain -j DNAT --to-destination 192.168.1.254

This assumes your router is set up as a DNS server.  Then in resolv.conf,
use your router at 192.168.1.254 as the DNS server, not any of those other
values.  That is (I think) similar to how I have mine configured at home.
 If you still have problems, I'll post my exact /etc conf files for you when
I get home.

On Thu, Sep 18, 2008 at 12:22 PM, Christian Weßel [EMAIL PROTECTED] wrote:

 Hello mokos,

 I just have a DNS problem, I try to configure my FC6 following the guide
 http://wiki.openmoko.org/wiki/USB_Networking#Proxying_with_iptables
 because I have a simple static environment for my FR.

 FR.usb.ip = 192.168.0.202
 server.usb.ip = 192.168.0.200
 server.eth.ip = 192.168.1.10
 router.eth.ip = 192.168.1.254
 DNS.ip = 212.6.108.140

 on server:
 [EMAIL PROTECTED] ~]# cat /etc/resolv.conf
 search home
 nameserver 212.6.108.140
 nameserver 212.6.108.141

 [EMAIL PROTECTED] ~]# iptables -L -t nat --line-numbers -n
 Chain PREROUTING (policy ACCEPT)
 num  target prot opt source   destination
 1DNAT   tcp  --  192.168.0.202192.168.0.200   tcp
 dpt:53 to:212.6.181.140
 2DNAT   udp  --  192.168.0.202192.168.0.200   udp
 dpt:53 to:212.6.181.140

 Chain POSTROUTING (policy ACCEPT)
 num  target prot opt source   destination
 1MASQUERADE  all  --  192.168.0.0/24   0.0.0.0/0

 Chain OUTPUT (policy ACCEPT)
 num  target prot opt source   destination

 on FR:
 [EMAIL PROTECTED]:~# cat /etc/resolv.conf
 nameserver 192.168.0.200

 [EMAIL PROTECTED]:~# ping 74.125.19.147 -c 1
 PING 74.125.19.147 (74.125.19.147): 56 data bytes
 64 bytes from 74.125.19.147: seq=0 ttl=236 time=182.480 ms

 --- 74.125.19.147 ping statistics ---
 1 packets transmitted, 1 packets received, 0% packet loss
 round-trip min/avg/max = 182.480/182.480/182.480 ms

 [EMAIL PROTECTED]:~# nslookup www.google.com
 Server:192.168.0.200
 Address 1: 192.168.0.200

 nslookup: can't resolve 'www.google.com'

 For me the masqueration seems to be fine, just something with DNAT is
 wrong.
 If I change the FR.resolv.conf to 'nameserver 212.6.181.140' it also not
 working.

 But what's wrong?

 BTW: I got no SElinux security alerts, neither in secure nor in
 messages.
 --

 mfg/br, christian

 Flurstraße 14
 29640 Schneverdingen
 Germany

 E-Mail: [EMAIL PROTECTED]
 Telefon: +49 5193 97 14 95
 Mobile:  +49 171 357 59 57
 http://wesselch.homelinux.org

 ___
 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: USB Networking vs. iptables

2008-09-18 Thread Joel Newkirk
I notice that you list the DNS server as 212.6.108.140
(resolver0.ewetel.de), but have the DNAT rules pointing at 212.6.181.140
(an unnamed IP that seems to be owned by 'claranet')...  Checking from the
'outside' (IE I'm not on your ISP's network, and I presume you are within
the ewetel.de network) 212.6.108.140 is a DNS server which won't let me do
recursive lookups, which is normal, but 212.6.181.140 seems unoccupied at
this time, or 100% firewalled.

If that doesn't resolve it, what's in your FORWARD and INPUT chains?  Can
you post the output of iptables -vnL?  (the -'v' for verbose means the
output will include counts of packets/bytes that matched each rule - useful
for debugging sometimes when unexpected zeros appear)  iptables -vnL
shows all the filter chains, INPUT/OUTPUT/FORWARD. (plus any custom chains)
 INPUT would affect packets from the Freerunner to the FC6 box (IE, when
resolv.conf points at 192.168.0.200) while FORWARD would affect packets
when you have the outside DNS server in resolv.conf.

j


On Thu, 18 Sep 2008 17:22:29 +, Christian Weßel [EMAIL PROTECTED]
wrote:
 Hello mokos,
 
 I just have a DNS problem, I try to configure my FC6 following the guide
 http://wiki.openmoko.org/wiki/USB_Networking#Proxying_with_iptables
 because I have a simple static environment for my FR.
 
 FR.usb.ip = 192.168.0.202
 server.usb.ip = 192.168.0.200
 server.eth.ip = 192.168.1.10
 router.eth.ip = 192.168.1.254
 DNS.ip = 212.6.108.140
 
 on server:
 [EMAIL PROTECTED] ~]# cat /etc/resolv.conf 
 search home
 nameserver 212.6.108.140
 nameserver 212.6.108.141
 
 [EMAIL PROTECTED] ~]# iptables -L -t nat --line-numbers -n
 Chain PREROUTING (policy ACCEPT)
 num  target prot opt source   destination 
 1DNAT   tcp  --  192.168.0.202192.168.0.200   tcp
 dpt:53 to:212.6.181.140 
 2DNAT   udp  --  192.168.0.202192.168.0.200   udp
 dpt:53 to:212.6.181.140 
 
 Chain POSTROUTING (policy ACCEPT)
 num  target prot opt source   destination 
 1MASQUERADE  all  --  192.168.0.0/24   0.0.0.0/0   
 
 Chain OUTPUT (policy ACCEPT)
 num  target prot opt source   destination
 
 on FR:
 [EMAIL PROTECTED]:~# cat /etc/resolv.conf 
 nameserver 192.168.0.200
 
 [EMAIL PROTECTED]:~# ping 74.125.19.147 -c 1
 PING 74.125.19.147 (74.125.19.147): 56 data bytes
 64 bytes from 74.125.19.147: seq=0 ttl=236 time=182.480 ms
 
 --- 74.125.19.147 ping statistics ---
 1 packets transmitted, 1 packets received, 0% packet loss
 round-trip min/avg/max = 182.480/182.480/182.480 ms
 
 [EMAIL PROTECTED]:~# nslookup www.google.com
 Server:192.168.0.200
 Address 1: 192.168.0.200
 
 nslookup: can't resolve 'www.google.com'
 
 For me the masqueration seems to be fine, just something with DNAT is
 wrong.
 If I change the FR.resolv.conf to 'nameserver 212.6.181.140' it also not
 working.
 
 But what's wrong?
 
 BTW: I got no SElinux security alerts, neither in secure nor in
 messages.



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: usb networking no longer works (solved)

2008-08-06 Thread Dimitri

Sorry, I hadn't realized that the phone had shut itself off.

I'm feeling rather dumb, right about now. Sorry :)

D


Dimitri wrote:
 
 I've flashed the latest 2008.8 images, and the script I was previously
 using to connect to the phone via usb no longer works.
 
 What I used to run (with 2007.2 images) was the following script as sudo
 in Ubuntu:
 --
 #!/bin/bash
 
 iptables -F
 ifconfig usb0 192.168.0.200 netmask 255.255.255.0
 route add 192.168.0.202 usb0
 iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
 iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
 iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
 bash -c echo '1  /proc/sys/net/ipv4/ip_forward'
 --
 
 But now, it fails with errors. I ran it, line by line, the first line that
 fails is
 
 ifconfig usb0 192.168.0.200 netmask 255.255.255.0
 
 with the error:
 --
 SIOCSIFADDR: No such device
 usb0: ERROR while getting interface flags: No such device
 SIOCSIFNETMASK: No such device
 --
 
 What's going on?
 Dimitri
 

-- 
View this message in context: 
http://n2.nabble.com/usb-networking-no-longer-works-tp675218p675227.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: usb networking no longer works

2008-08-06 Thread Kalle Happonen
Hi,
I had the same problem. IIRC it was resolved by flashing a new uboot to 
the device.

cheers,
Kalle

Dimitri wrote:
 I've flashed the latest 2008.8 images, and the script I was previously using
 to connect to the phone via usb no longer works.

 What I used to run (with 2007.2 images) was the following script as sudo in
 Ubuntu:
 --
 #!/bin/bash

 iptables -F
 ifconfig usb0 192.168.0.200 netmask 255.255.255.0
 route add 192.168.0.202 usb0
 iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT
 iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT
 iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24
 bash -c echo '1  /proc/sys/net/ipv4/ip_forward'
 --

 But now, it fails with errors. I ran it, line by line, the first line that
 fails is

 ifconfig usb0 192.168.0.200 netmask 255.255.255.0

 with the error:
 --
 SIOCSIFADDR: No such device
 usb0: ERROR while getting interface flags: No such device
 SIOCSIFNETMASK: No such device
 --

 What's going on?
 Dimitri
   


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: usb networking no longer works (solved)

2008-08-06 Thread Andy Green
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Somebody in the thread at some point said:
| Sorry, I hadn't realized that the phone had shut itself off.
|
| I'm feeling rather dumb, right about now. Sorry :)

No problem, thanks for clearing it up.

- -Andy
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkiZRWgACgkQOjLpvpq7dMrDOwCfVEpCA9Nm0Z3q+71MlhCZOZ+D
pRcAn3w9zgAh6edweX/Pn3iGj4ewopqs
=uZDS
-END PGP SIGNATURE-

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: USB Networking - Freerunner Mac OS X 10.5.4

2008-07-12 Thread Russell Sears
The neo's IP address is 192.168.0.202; the Mac's IP should be 
192.168.0.200, so you're trying to ssh to the laptop, not the phone.

I have no idea why you're getting the cannot allocate memory errors. 
The ubutu error messages make more sense, so I'd try troubleshooting it 
from there first.

-Rusty

C R McClenaghan wrote:
 I'm having trouble getting USB networking to work on my new Neo  
 Freerunner. Under Mac OS X 10.5.4 I'm getting:
 
 ssh: connect to host 192.168.0.200 port 22: Cannot allocate memory
 
 and
 
 PING 192.168.0.200 (192.168.0.200): 56 data bytes
 ping: sendto: Cannot allocate memory
 
 If I use an Ubuntu 8.04 virtual machine on the Mac, the ping succeeds,  
 but the ssh is denied with:
 
 ssh: connect to host 192.168.0.200 port 22: Connection refused
 
 I have looked at the Mac OS X wiki pages and tried an alternative  
 driver, but that seemed to have no effect. From the shell I'm unable  
 to run lsmod or modprobe, so I'm not sure which of the two drivers is  
 running. I'm about to try the other driver mentioned on the wiki for  
 the Zaraus, but I'm not hopeful.
 
 I can access the USB console for both UBoots - Nor and Nand, so the  
 cable itself seems good.
 
 Has anyone insight or suggestions on what I might try?
 
 Thanks,
 
 Chris
 
 ___
 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: USB Networking - Freerunner Mac OS X 10.5.4

2008-07-12 Thread C R McClenaghan
Rusty,

Thanks - I had just reread the wiki and noticed my error. Too much  
excitement on receiving the unit and not enough coffee this morning ;-)

Thanks for the help - I am able to ssh to the Freerunner!

Onward and upward.

Chris

On Jul 12, 2008, at 11:10 AM, Russell Sears wrote:

 The neo's IP address is 192.168.0.202; the Mac's IP should be
 192.168.0.200, so you're trying to ssh to the laptop, not the phone.

 I have no idea why you're getting the cannot allocate memory errors.
 The ubutu error messages make more sense, so I'd try troubleshooting  
 it
 from there first.

 -Rusty

 C R McClenaghan wrote:
 I'm having trouble getting USB networking to work on my new Neo
 Freerunner. Under Mac OS X 10.5.4 I'm getting:

 ssh: connect to host 192.168.0.200 port 22: Cannot allocate memory

 and

 PING 192.168.0.200 (192.168.0.200): 56 data bytes
 ping: sendto: Cannot allocate memory

 If I use an Ubuntu 8.04 virtual machine on the Mac, the ping  
 succeeds,
 but the ssh is denied with:

 ssh: connect to host 192.168.0.200 port 22: Connection refused

 I have looked at the Mac OS X wiki pages and tried an alternative
 driver, but that seemed to have no effect. From the shell I'm unable
 to run lsmod or modprobe, so I'm not sure which of the two drivers is
 running. I'm about to try the other driver mentioned on the wiki for
 the Zaraus, but I'm not hopeful.

 I can access the USB console for both UBoots - Nor and Nand, so the
 cable itself seems good.

 Has anyone insight or suggestions on what I might try?

 Thanks,

 Chris

 ___
 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


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community