Search Members Help

» Welcome Guest
[ Log In :: Register ]

Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic
Pages: (2) </ 1 [2] >/

[ Track this topic :: Email this topic :: Print this topic ]

reply to topic new topic new poll
Topic: Networking problems with Embedded version, Networking problems with Embedded versio< Next Oldest | Next Newest >
Gatorhex Offline





Group: Members
Posts: 7
Joined: Mar. 2007
Posted: Mar. 02 2007,01:16 QUOTE

Ok, if its using a fake NAT to get on the 192.168 network i could live with that but I don't understand why 2 DSLs can't talk to each other on the fake 10.0 side if they are both in that range

Bah, I give up with it, it's not got iptables and I'll probably need to use that to emulate my firewalls  :(
Back to top
Profile PM 
Gatorhex Offline





Group: Members
Posts: 7
Joined: Mar. 2007
Posted: Mar. 02 2007,01:25 QUOTE

Just read somewhere....

"In other words, conceptually, tun0 actually sits 'between' the host OS and the guest (whether this is actually the case or not I leave as an intellectual exercise for the reader).  So, the tun0 address and the qemu guest OS address should be different, but should both be on the same subnet, and that subnet should be utterly different to anything else on your network.  Intellectually I can appreciate the possibility that it shouldn't *have* to be on a different subnet, but in practice I met with utter and complete failure attempting to make tun0 and the guest OS NIC live on the same subnet as all the 'real' NICs.

Therefore, all traffic to the 'real world' goes from the guest, to tun0 (ie, in the guest OS set the address of the default gateway to be the tun0 address), and from tun0 out to the world via the real NIC address.  To make all this work, you need a script that puts the house in order for tun0.  

   Your real NIC, because all of the traffic is routing through it, has to have an appropriate iptables rule to masquerade traffic, and ip forwarding needs to be enabled for the host OS.  Here is a simple script that does everything necessary (ie, this is a working, complete qemu-ifup):

--------8<--------snip
#!/bin/bash
iptables --flush          #Clear out all previous rules ('/etc/init.d/iptables stop' may also work)
echo 1 >/proc/sys/net/ipv4/ip_forward     #Enable IP forwarding for the host OS
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE   #Enable masquerading on your real NIC so tun0 can get in and out
ifconfig $1 10.0.0.1   #Bring up tun0 on a different subnet from the host
--------8<--------snip" http://www.arcknowledge.com/gmane.c....65.html

OMG somone please put iptables into the DSL distro  :laugh:
Back to top
Profile PM 
roberts Offline





Group: Members
Posts: 4983
Joined: Oct. 2003
Posted: Mar. 02 2007,01:54 QUOTE

MyDSL->UNC->rcfilewall.unc
Back to top
Profile PM WEB 
^thehatsrule^ Offline





Group: Members
Posts: 3275
Joined: July 2006
Posted: Mar. 02 2007,03:58 QUOTE

I think that script is for the host o/s .... and I don't think you are using DSL as the host.


If you want an easy way out, there are several commercial VM software you can use that are packaged quite nicely.  I'd suggest trying out vmware (which will set up your host o/s for you)
Back to top
Profile PM 
8 replies since Mar. 01 2007,23:36 < Next Oldest | Next Newest >

[ Track this topic :: Email this topic :: Print this topic ]

Pages: (2) </ 1 [2] >/
reply to topic new topic new poll
Quick Reply: Networking problems with Embedded version

Do you wish to enable your signature for this post?
Do you wish to enable emoticons for this post?
Track this topic
View All Emoticons
View iB Code