DHCP client (pump) catching strange IP addressForum: DSL Embedded Topic: DHCP client (pump) catching strange IP address started by: smed Posted by smed on Dec. 09 2005,21:43
Here are the details:WinXP laptop (Dell D600) running Windows XP. Uses Broadcom ethernet adaptor and Dell TrueMobile Wireless adapter. Everything was working fine for a couple of days, I was able to get on the network and browse with Dillo and Firefox and even use Rdesktop at a client's shop to admin some Windows servers. When DSL boots up, everything is normal. When I FIRST ran DSL embedded it was unable to find the correct driver for the broadcom adapter so I modprobed ne2k-pci and was able to renew the adapter and catch an IP address, allowing me to use the network no problems. Today when I boot up DSL embedded, I no longer have t modprobe for the driver...it find it on boot, and pump seems to grab an IP address with no problem. The problem is it's catching an IP address of 10.0.2.15/24 and adding a default gateway of 10.0.2.2 and a DNS server in /etc/resolv.conf of 10.0.2.3 I can not surf the web of do anything network related because that IP address scheme is not from my DHCP server. My small LAN is setup using an IP address scheme of 192.168.1.100/24 with a default gateway of 192.168.1.101. This is a pretty standard configuration and my other 5 machines are happy with this, including the WinXP host, which is catching 192.168.1.113 as it should an pointing to the appropriate gateway, 192.168.1.101 I've tried releasing and renewing several times and it catches the same IP address, 10.0.2.15 with the same gateway, 10.0.2.2 I've tried modprobe -r ne2k-pci and reloading the module and then configuring the ethernet interface manually as so: # ifconfig eth0 192.168.1.121 The adapter will take the IP address I specify so I was happy, I then configured the default gateway as follows: #ifconfig add default gw 192.168.1.101 wonderful! when I list the routing table it even finds the default gateway. However I can not ping anything...including machines on my own network...and I can't ping the default gateway. Something is radically wrong. I went a step further and took the .zip file I downloaded and extracted DSL-2.0 embedded into another folder and booted it up "fresh". It booted without incident and went on to find an IP address and default gateway, 10.0.2.14 with the gateway at 10.0.2.2 Anyone else having this problem? I've only had this running for a few days and DAY ONE was prefect....I was able to catch an IP at 3 different client locations an catch IP addresses on their networks with no problems. I was showing it off to my client's admins who were in awe. Now all of the sudden the networking seems to have shit the bed. Not sure why. I've used pump before in past lives and it's fairly reliable IMO, but I don't really think that's the problem. One final last word - a friend of mine in my LUG also downloaded DSL the same day as I did...and he too also had good luck with it the first day. He is now experiencing the same exact problem, he's getting the same exact IP address (10.0.2.15) and the same exact gateway (10.0.2.2) and DNS server (10.0.2.3) Anyone who has experienced this, I'd appreciate hearing from....I'd like to work this out...I'm sure it must be a minor bug or config issue. I'll keep playing with it and post back if I come up with any significant finds. smed Posted by roberts on Dec. 10 2005,00:27
It is completely normal because you are running a virtual machine.See also < http://damnsmalllinux.org/cgi-bin....hl=ping > Posted by smed on Dec. 10 2005,00:48
It's may be normal, but it's non-functional. I don't care how the VM does it's thing, but I can't ping anything on the Internet or inside my LAN. Traceroutes fail completely after the hop to the host machine. The nameserver that the DHCP client writes to /etc/resolv.conf doesn't resolve *anything*, and the beside being able to ping the default gateway, it doesn't seem to be routing any traffic, which is pretty much the gateway's job. There is nothing "normal" about that....the network is no more functional than if the interface didn't have an IP address and the routing table was blank. Posted by roberts on Dec. 10 2005,01:49
I am not going to argue with you... Your post is nothing new.10..0.2.15 is the standard response from Qemu virtual machine. If your windows networking is functional with YOUR specifics then Qemu's default network will pass thru using 10.0.2.x Please take your questions regarding Qemu's networking to the Qemu support site. Posted by smed on Dec. 10 2005,02:13
ok here's an update. Normal network debugging tools such as ping and traceroute do not work as expect through QEMU. I CAN indeed load web pages with the seemingly erroneous IP address and gateway assignment, but I can't resolv any names for some reason...and the odd thing is that it WAS working the first day I tried this. I've noticed now that running DSL embedded on WinXP, Win2K and Linux all seem to behave the same in regards to the way it handles network functionality. I'm surprised there aren't more posts regarding this issue. Maybe I do need to see the QEMU forums to debug this issue. And for the record....I'm not arguing, just trying to solve a problem, unless you want an argument, 'cause I can do both. Posted by cbagger01 on Dec. 10 2005,06:01
I have used DSL embedded on Windows XP SP1 and SP2http 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. Posted by smed on Dec. 10 2005,16:49
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 Posted by cbagger01 on Dec. 10 2005,21:28
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? Posted by smed on Dec. 10 2005,22:05
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. Posted by stoneguy on Dec. 11 2005,01:58
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
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. Posted by cbagger01 on Dec. 13 2005,17:18
I am pretty sure that DSL does not use the TUN/TAP interface with QEMU and instead uses the user mode networking functionality in QEMU.
Posted by pr0f3550r on Jan. 08 2006,11:46
According to < Qemu FAQ >:
Now, when I type [CTRL]+[ALT]+2, then 'info network', I get :
So, in my opinion, user mode networking is enabled and I should be able to ping 10.0.2.2 from my win boxes but I get 'request timed out' on some machines and 'destination net unreachable' on some other. Win XP firewall settings, or what? Any help? |