Re: USB Networking vs. iptables
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: Problems with SD boot of FSO, OM 2008.8, add /dev/mmcblk0... to distros?
I think a number of people are having the same problem stemming from the sd card driver not reading some cards. The mmcblk0p1, p2, etc. device files actually will be autocreated whenever Linux thinks there are partitions there, but the problem is that sometimes when it tries to read the partition table of the card it fails to get any data, so it doesn't think any partitions exist. Thanks for posting the mknod syntax because I was wondering how you do that manually, but you can also do this to make the p1, p2, p3 device files show up automatically: fdisk /dev/mmcblk0 visually verify that partition table exists use w to make fdisk write the (unchanged) partition table back out What happens is after the w command, fdisk calls ioctl to resync the partition table, and you magically get the dev files back. (Don't save with w if fdisk thinks the partition table is empty though!) In fact, would you try this and tell us if it works? I'd like to verify we're all having the same problem and not different problems. If the first time you call fdisk you get no table, try calling fdisk multiple times. Here's an actual session capture. fdisk is returning different results every time I call it: [EMAIL PROTECTED]:~# fdisk -l /dev/mmcblk0 [EMAIL PROTECTED]:~# fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 7948 MB, 7948206080 bytes 4 heads, 16 sectors/track, 242560 cylinders Units = cylinders of 64 * 512 = 32768 bytes Disk /dev/mmcblk0 doesn't contain a valid partition table [EMAIL PROTECTED]:~# fdisk -l /dev/mmcblk0 Disk /dev/mmcblk0: 7948 MB, 7948206080 bytes 4 heads, 16 sectors/track, 242560 cylinders Units = cylinders of 64 * 512 = 32768 bytes Device Boot Start End Blocks Id System /dev/mmcblk0p1 1 2457832 83 Linux /dev/mmcblk0p2 246 242560 7754080 83 Linux On Fri, Sep 19, 2008 at 8:53 AM, Erland Lewin <[EMAIL PROTECTED]> wrote: > I got a new SDHC card, and tried installing FSO and OM2008.8 to boot off > it. > I had problems, which I believe I tracked down to the fact that there are > no /dev/mmcblk0, /dev/mmcblk0p1, etc devices in the file systems > distributed. > > U-boot starts the kernel OK, but when the kernel tries to mount the root > filesystem, it fails because the device node /dev/mmcblk0p1 for example > above can't be found. Creating these manually with: > > (in the /dev directory of the card) > mknod mmcbkl0 b 179 0 > mknod mmcblk0p1 b 179 1 > mknod mmcblk0p2 b 179 2 > mknod mmcblk0p3 b 179 3 > > Seems to have fixed the problem. > > Note that I booted with the kernel on the same partition as the root file > system. > > I would recommend that these device nodes be created in the distributed > root file systems. > > /Erland > > > ___ > 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
