DSL Embedded :: DHCP client (pump) catching strange IP address

I have used DSL embedded on Windows XP SP1 and SP2

http and ftp work fine out-of-the-box for me.

That "go talk to the QEMU guys" suggestion is more than a let's end this discussion type statement.

There is some really good help available from the QEMU developers and users.

Quote (cbagger01 @ Dec. 10 2005,01:01)

I have used DSL embedded on Windows XP SP1 and SP2
http and ftp work fine out-of-the-box for me.
That "go talk to the QEMU guys" suggestion is more than a let's end this discussion type statement.
There is some really good help available from the QEMU developers and users.

Advice taken already.
I've done some more investigating and the problem I'm having on my laptop, in particular, is not network connectivity as I orginally thought. Qemu's docs indicate that normal network debugging tools (ping, traceroute) do not work as one would suspect...so that confirms my results.

From what I can tell, the gist of my problem is as so:
DNS resolution is NOT working. That's the crux of the problem. I can see where 10.0.2.3 is being assigned in /etc/resolv.conf as the DNS server to query when resolving names, but it's not working. This is happening both on my laptop at home behind my router/firewall, and on my older Win2K box at home, also on the same network. The DNS resolution problem is NOT ocurring on my Linux workstation at home, also behind the same router/firewall. Running DSL embedded on my FC3 workstation does DNS lookups just fine....no issues.
I can load web pages through Dillo and Firefox on the Windows machines here as long as I use numeric IP addresses......so it appears as if I was wrong (I'll admit it), the network is "functional", however severely disabled without name resolution.

This is NOT a DSL problem, so I can understand the redirection to the QEMU site. Still...I've reviewed the docs on their site and the kludgy implementation of the user-mode network stack, but still I can't understand how it goes about assigning the IP address scheme, and the docs really aren't that thorough so I guess I'll have to review the QEMU forums for information related to my problem.

Anyways....thanks for the advice and I'll continue to play with this until I get it right. The Embedded version of DSL is an EXCELLENT tool for new Linux users to experiement with for the purpose of familiarizing themselves with Linux, but the network integration has got to be nearly perfect if new users are going to make the most out of it. Most Windows users taking the journey into experimenting with Linux just haven't got the patience or know-how to be playing around with strange network configurations that they aren't familiar with and that will spoil the experience for them. This certainly isn't the case for me, or many of my colleagues, however as an officer in one of the most active and dynamic LUG's in the area, it's important for me to evaluate all aspects of a distro.

Again - to those admin's and others involved in the DSL project - Nice job...I've been using it as a recovery tool for the past year or so and recently discovered the embedded version. I think you're onto something here. I'm going to recommend a presentation on DSL for the upcoming meeting schedule for my LUG and will pledge to distribute CD's to hopefully make some converts.

smed
http://www.lugip.org
smed@lugip.org

Most of the QEMU information I have learned is from the forums or the archives, so it is definately a place to start.

On my computers, DNS resolution and networking work fine from within DSL embedded.

My MSWindows computers both use DHCP (IE: Obtain addresses automatically) for the Microsoft TCP/IP settings. Maybe this is a difference between me and you?

Quote (cbagger01 @ Dec. 10 2005,16:28)

No, my machines both take their IP addresses and nameserver parameters from my DHCP server. Something isn't right though and I still haven't figured it out. When I do I'll post it back to this thread just in case someone else has the same problem.

nslookup's fail completely, so the linkage between the guess (DSL) and the host (WinXP) for the nameserver must be broken somehow. I'm still not sure I understand how QEMU does this on a Windows Host so I've got to read more on it. The Qemu forums do seem the be the way to go....lots of great information there, still I haven't seen anything that stands out as similar to my situation.

I just stumbled into this strange backwater of Linux when I put DSL on a USB stick using 5-way so I could run it in WinXP.

Up til now, I'd never heard of TUN/TAP. And after a few hours of googling, it remains mostly a mystery. Most of the info out there pertains to User Mode Linux, and refers to a different file hierarchy than DSL's.

As near as I can figure out, qemu looks for a /etc/qemu-ifup script to get things rolling. But what needs to be in the script? I got as far as

Code Sample

sudo insmod tun

but it doesn't appear to have created tun0 as one thread said it would. Of course, there is no /dev/net hierarchy in DSL, so I'm wondering if that's why I couldn't find it. There's no mknod command to create the device either.

And I also don't know whether I'd have to remaster to get the script inserted (which I'm not ready to tackle), or if there's some way to include what's required in bootlocal.sh

So, I'm kind of stuck here (like everyone else) trying to connect my inner DSL to my 192.168.x.x local lan. smed, if you find out anything, give us a shout.

Next Page...
original here.