• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1] 2
1  General Category / General Discussion / Re: Dreamplug How to Connec to WAN via WAP on: January 09, 2012, 02:06:50 AM
I do not believe it. I knew it would be a simple fix once the problem was identified, 'masquerade' is to be used when the gateway (in this case eth0) gets it's address via dhcp, if it has a static ip you should use 'snat'. I changed /etc/network/interfaces to 
Code:
iface eth0 inet dhcp
and away we go.
Now to get this thing configured to serve me website.
2  General Category / General Discussion / Re: Dreamplug How to Connec to WAN via WAP on: January 08, 2012, 01:05:57 PM
The routes get set up automatically from the info supplied in /etc/network/interfaces although you can edit them with 'route'.
For now I've unplugged eth1.
3  General Category / General Discussion / Re: Dreamplug How to Connec to WAN via WAP on: January 07, 2012, 07:07:37 PM
Yes that is still there and working, as I stated above traffic sent to the LAN gets NAT'd but I am now one step closer to a solution.
The traffic arriving at the router that originates from 192.1.168.2.104 is getting there via eth1 on the plug so that explains why it's not NAT'd  Smiley That gets rid of one red herring.
4  General Category / General Discussion / Re: Dreamplug How to Connec to WAN via WAP on: January 07, 2012, 03:39:11 PM
192.168.1.0 is my LAN
192.168.2.0 is the network assigned to uap0 the wireless interface on the plug which has the address 192.168.2.1
192.168.1.92 is the address statically assigned to eth0 on the plug
192.168.2.104 is the address that is dynamically assigned to the device that is connecting to uap0.
The address is assigned by dnsmasq running on the plug. Dnsmasq also supplies dns services.
NAT is enabled by iptables on the plug so all traffic leaving the plug on eth0 will appear to originate from ip address 192.168.1.92.
This works for traffic from 192.168.2.104 destined for the LAN but anything destined for the internet arrives at the router with an originating ip of 192.168.2.104  Shocked
So anything that requires a DNS lookup somehow bypasses iptables  Shocked
Typing an ip address into a browser will still result in a dns lookup.
5  General Category / General Discussion / Dreamplug How to Connec to WAN via WAP on: January 06, 2012, 03:54:44 AM
I've got me new Dreamplug and having a a lot of fun with it but one thing is defeating me, connecting to the internet through the WAP. Here's the story briefly, bricked it on day one. Got a Debian Squeeze img from NewIt. My network is 192.168.1.0 so I changed all references to 192.168.1.* in init_setup.sh, dnsmasq.conf and udhcpd to 192.168.2.* . Great, can access the device wirelessly. I can access servers on my network, ftp and www but I can't access the WAN.
Monitoring with wireshark and me routers logging tool I can see that requests to servers on my LAN are correctly originating from 192.168.1.92 (eth0 on the plug) but requests to the WAN are coming from 192.168.2.104 (the ip of the device from uap0) which is why I can't get out or more correctly don't receive a reply.
So it seems when it needs to use DNS to get an IP it somehow does not NAT the request to the IP !!!? Help, I've been beating me head against this for days, everything I've read suggests this should be working.
6  Hardware and U-Boot firmware / U-Boot stuff / Re: Dreamplug Cant Boot From USB drive Solved on: January 01, 2012, 07:28:48 PM
It turns out the problem is with the formating. I was using Gparted but apparently it doesn't quite do the business using a low level tool like mkfs produces reliable drives (thanks Spinifex).
7  Hardware and U-Boot firmware / U-Boot stuff / Re: Dreamplug Cant Boot From USB drive on: December 31, 2011, 05:06:51 AM
OK after much experimentation this is conclusion -- uboot is sadly lacking.
Sometimes plugging in a usb stick and resetting at the marvell prompt works (with the env set to boot from a stick)
Plugging in a stick while its off and then powering up the plug never works.
Booting off the internal card then plugging in the stick then resetting (pin in the hole) then changing the env to boot from the stick and then typing reset from the marvell prompt always works
8  Hardware and U-Boot firmware / U-Boot stuff / Re: how t o access to the linux kernel despite the WIFI on: December 31, 2011, 04:37:14 AM
Get the Jtag module and connect via the uart port
9  Linux Stuff / General Linux questions / Dreamplug debian update fopen: Permission denied on: December 31, 2011, 01:28:53 AM
If you've got a Debian based Dreamplug and you're trying to update the packages and you're getting
Code:
Processing triggers for man-db ...
fopen: Permission denied
the problem is with /var/cache/man ownership. Fix it with this
Code:
chown -R man:root /var/cache/man
10  Hardware and U-Boot firmware / U-Boot stuff / Re: Dreamplug Cant Boot From USB drive on: December 30, 2011, 08:22:17 PM
Arrgghh it's doing it again. I tried another uImage and it refused to read it
Code:
Wrong Image Format for bootm command
. I then tried one of the usb drives that had worked ok earlier and they are giving the same problem WTF.
All feeback much appreciated, if you boot of a USB stick consistently I'd like to know.
11  Hardware and U-Boot firmware / U-Boot stuff / Re: Dreamplug Cant Boot From USB drive Solved on: December 30, 2011, 07:29:52 PM
Well it must be magic. I made a 3rd pendrive using the same files as the other 2 but this one is only 4GB and it worked first time. I played about a bit setting stuff up and then tried one of the 8GB drives again. It first of all said it couldn't read it then after several seconds read the uImage and booted up and has rebooted many times since.
12  Linux Stuff / General Linux questions / Re: Dreamplug lost networking on: December 30, 2011, 03:26:21 PM
Quote
eth0   inet addr:192.168.1.105  Bcast:192.168.1.255  Mask:255.255.255.0

uap0   inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0


Disable the wifi at startup, comment out the call to init_setup.sh in /etc/rc.local and reboot
I had considered that as a problem but didn't know where to switch it off or change it. Anyhoo when I started debugging this I moved to another work station and when I hooked it up I plugged the network into the wrong ethernet port  Grin so it was probably fixed many hours ago. Identifying them on the case would be helpful and also in the user guide. Thanks for your help.
13  Linux Stuff / General Linux questions / Re: Dreamplug lost networking on: December 30, 2011, 03:01:55 PM
try the other ethernet (eth1) which is at the end of the plug
Now that's interesting in the user guide the ethernet closest to the end is identified as eth1 and the other is identified as eth2 so I assumed eth1 was eth0 and eth2 was eth1. We progress thanks.
14  Hardware and U-Boot firmware / U-Boot stuff / Dreamplug Cant Boot From USB drive on: December 30, 2011, 03:34:16 AM
Hi,
Like most newbies I'm having a few problems. I've posted elsewhere about no network and to help identify where the problem is I thought I'd boot from a USB drive. There is a comprehensive article here http://code.google.com/p/dreamplug/downloads/detail?name=DreamPlug%20-%20Change%20OS%20from%20Ubuntu%20to%20Debian-20110617.pdf&can=2&q= however it fails to boot claims the file format is wrong.
The uboot env has been changed thus
Code:
Marvell>>setenv x_bootcmd_kernel fatload usb 2 0x6400000 uImage
Marvell>>setenv x_bootargs_root root=/dev/sdc2 rootdelay=10
and
Code:
fatls usb 2 /
lists the uimage file.
I've tried 2 different uImage files, same result.
Any pointers to make this work.
15  Linux Stuff / General Linux questions / Re: Dreamplug lost networking on: December 30, 2011, 03:11:02 AM
Here's route and ifconfig staus. This should be working, what am I missing.

Code:
sheevaplug-debian:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
192.168.1.0     *               255.255.255.0   U     0      0        0 uap0
default         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
sheevaplug-debian:~# ifconfig
eth0      Link encap:Ethernet  HWaddr f0:ad:4e:00:94:47 
          inet addr:192.168.1.105  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:11

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1764 (1.7 KiB)  TX bytes:1764 (1.7 KiB)

uap0      Link encap:Ethernet  HWaddr 00:24:23:3e:fb:e0 
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

sheevaplug-debian:~# uname -a
Linux sheevaplug-debian 2.6.33.6 #1 PREEMPT Tue Feb 8 03:18:41 EST 2011 armv5tel GNU/Linux
sheevaplug-debian:~#
Pages: [1] 2