SliTaz Forum
You are not logged in.
Hi everyone.
This isn't really a slitaz problem.
More like a quirk.
Every other distro & windows can get an IP address through dhcp at home.
I have a private LAN at work & I can get DHCP on my laptop through the live CD there.
Bring the laptop home & boot it up with the live CD & it acts like the cable isn't even plugged in.
But, If I assign my LAN adapter a static IP through the router & set it up as static on slitaz, no problems.
What is special about slitaz that it wouldn't like my home router?
I'm at a loss here.
any ideas?
Thanks.
Offline
In the absence of information, I assume that all other distros and Windows are on the same laptop?
I presume you have already checked to make sure dhcp is set to 'yes' and static and wifi set to 'no' in your /etc/network.conf file which should force dhcp on eth0 if you stop and restart the network.
What's the output from 'ifconfig eth0'?
Offline
Yes on all accounts.
Restarting the network results in udhcpc on eth0 followed by: "Sending Discover..." 3x
And "no lease, forking to background"
$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:16:D4:BF:4A:F9
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5241 errors:0 dropped:24 overruns:0 frame:0
TX packets:1331 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1603594 (1.5 MiB) TX bytes:433906 (423.7 KiB)
Interrupt:16
Thanks.
Offline
You do not have two ethernet ports by any chance? I presume you don't but I have one machine with two ethernet ports and if I do not set the default port correctly it results in the same message due to obvious reasons. Should have asked you to do a ifconfig -a which would have shown all the active interfaces.
I presume you have used the same cable with other distros and got the link up and running? If this is not the case may be worthwhile replacing the cable?
If your router is able to do a debug on dhcp messages, that's worth checking out.
Perhaps you may want to post a copy of your /etc/network.conf?
Offline
Yes again on other linux distro's connecting. Actually wireless works also on other distro's but i'm more interested in figuring out wired LAN since it's the same problem with slitaz on ALL my desktops.
ifconfig -a
dummy0 Link encap:Ethernet HWaddr 76:DE:D1:2E:DA:90
BROADCAST NOARP 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:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth0 Link encap:Ethernet HWaddr 00:16:D4:BF:4A:F9
inet addr:192.168.1.66 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4315 errors:0 dropped:13 overruns:0 frame:0
TX packets:262 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1539847 (1.4 MiB) TX bytes:28367 (27.7 KiB)
Interrupt:16
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 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:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wlan0 Link encap:Ethernet HWaddr 00:19:D2:60:7E:6A
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)
I don't know what dummy is but it has a hardware MAC address.
My router is about 10yrs old and only shows me what has connected to it via DHCP recently.
here is my network.conf setup for DHCP
# /etc/network.conf: SliTaz system wide networking configuration.
# Config file used by: /etc/init.d/network.sh
#
# Set default interface.
INTERFACE="eth0"
# Dynamic IP address.
# Enable/disable DHCP client at boot time.
DHCP="yes"
# Static IP address.
# Enable/disable static IP at boot time.
STATIC="no"
# Set IP address and netmask for a static IP.
IP="192.168.1.66"
NETMASK="255.255.255.0"
# Set route gateway for a static IP.
GATEWAY="192.168.1.2"
# Set DNS server for a static IP.
DNS_SERVER="192.168.1.2"
# Wifi connection.
# Enable/disable wireless connection at boot time.
WIFI="no"
# Wifi interface (iwconfig) and ESSID.
WIFI_INTERFACE=""
WIFI_ESSID=""
WIFI_MODE="managed"
WIFI_KEY=""
WIFI_KEY_TYPE=""
WPA_DRIVER=""
WIFI_CHANNEL=""
WIFI_IWCONFIG_ARGS=""
%0
Offline
Hi
Your latest ifconfig -a shows that you have been allocated an ip address! - which is 192.168.1.66...
eth0 Link encap:Ethernet HWaddr 00:16:D4:BF:4A:F9
inet addr:192.168.1.66 Bcast:192.168.1.255 Mask:255.255.255.0
Do a ping to the router to verify but if ifconfig reckons you have an ip address, that is sure proof that you have received a dhcp address from the router.
After any changes to /etc/network.conf make sure to do a "/etc/init.d/network.sh start" (as root of course) to restart the network - perhaps you did not do this earlier??
Offline
Sorry, that is my static IP address.
I'll get back on the laptop & get the output for DHCP on a fresh boot.
Offline
here is the correct output.
If I set it up as static & assign an ip to the adaptors mac address in my router I have internet.
dhcp doesn't work though.
ifconfig -a
dummy0 Link encap:Ethernet HWaddr 32:F9:B0:32:74:24
BROADCAST NOARP 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:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth0 Link encap:Ethernet HWaddr 00:16:D4:BF:4A:F9
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:112 errors:0 dropped:2 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:33584 (32.7 KiB) TX bytes:9128 (8.9 KiB)
Interrupt:16
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 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:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wlan0 Link encap:Ethernet HWaddr 00:19:D2:60:7E:6A
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)
/etc/init.d/network.sh start
Starting udhcpc client on: eth0...
udhcpc (v1.18.4) started
Sending discover...
Sending discover...
Sending discover...
No lease, forking to background
Offline
OK, now that's a different story!!
However, what is interesting is that still your eth0 shows good tx and rx counts (apart from the 2 dropped packets).
I did a LiveCD boot myself and the only significant difference I found was that in my case the interrupt is 17 and I also have the memory location given whereas yours only show interrupt 16.
I am running out of ideas but just wondering whether this might be an issue with the driver in use. You may want to do a lspci and check that the appropriate module is loaded.
Check out the section on Install Network Card/Driver here.....
http://doc.slitaz.org/en:handbook:networkconf?s[]=ethernet&s[]=driver
Hope this will help.
Offline
I'll look at the driver & my hardware but, if I had the wrong driver/ module loaded would I still be able to get a static IP address?
Offline
You are probably right, if the issue is with the driver it is likely that static ip will also fail.
If you do a 'ps -ef | grep udhcpc' it should tell you which interface is being used for dhcp and this might give you some clues....
If I were you, I would turn off dhcp on the router and run dhcp on another machine on your lan to isolate any issues with udhcpc and router's dhcp daemon. From memory, Windows programs like tftpd32 has dhcp server function as well, in case your other pcs are running Windows.
Offline
Not that it is going to help that much but you can run udhcpc in the foreground...
# udhcpc -f -i eth0
Unfortunately, it will not give extra debug information but worth a try.
# udhcpc --help will give all options in case you want to different options.
Offline
Eth0 is being used.
I recall having this problem with another distro, TinyCore.
I booted up with that & got the same thing.
It uses the same dhcp server as slitaz.
So either my router & udhcpc don't like each other or well I don't know because it should just work. Doesn't make sense how every PC I boot slitaz on can't get an IP address through DHCP on my LAN.
I'm going to make my wifi router my dhcp server on my LAN when I get a chance and see if it makes a difference.
Offline
As mentioned earlier, the easiest way to nail down the issue is to turn off dhcp on the router and run dhcpd on another machine on your LAN.
If the LAN is connected via hub I would run something like wireshark or tcpdump on another machine and check what is happening with your dhcp requests and responses. Or alternatively, download the Slitaz Packages DVD and install wireshark or tcpdump on the machine using the DVD as the repository (that way you do not have to have an Internet connection to install wireshark).
Also, there is a dhcp-client package in the repo which probably is different to udhcpc used at boot time and may be worth a try.
Would be interested to know your findings. Good luck.
Offline
I'll be damned.
Unplugged my wi-fi router from my main router & made that the dhcp server & booted right into an I.P. address once I choose eth0 as my network adapter.
I was able to browse the routers configuration through midori.
Ok so for some reason udhcpc doesn't like my router.
why?
Now I did check & the lastest firmware is from 2004 & it's on there. LOL!
Might be time to retire it.
The d-link's last firmware upgrade was 2006. not much better.
I'm going to try the other dhcp client you spoke of. If I can figure out how to make it run once I remove the default)
Looks like that is a more common client.
But ultimately I think it's time to upgrade my router. Their cheap these days.
Offline
Good to see that you have some solution to your problem.
I do not think it is a firmware issue on your wifi router - 2004 is not that old especially considering dhcp came into existence a lot earlier than that.
Now that you have given more details of your set up, it looks more likely that this is more a routing issue.
Are you routing between the two routers or bridging the two? If you have two networks then the dhcp broadcasts from your LAN will not reach the dhcp server on the other network and this may explain why it does not work. Easy to check this - plug the PC directly into the wifi router (you will not be able to access the Internet but that is beside the issue) and see whether you can get a ip address.
Anyway, the only way to determine the problem is to sniff the packets on the wire - you should be able to download and install wireshark now that you have an Internet connection.
Offline
I'm using my wifi router as just a switch & wireless access point.
My main router is on another floor.
I've hooked numerous PC's up to the wifi router & have my main PC hooked up to it & they all receive an IP through dhcp.
Plugging the laptop directly into my main router still doesn't give me an IP so it isn't anything in between on my network.
I also forgot I can put my DSL modem into router mode and use that as my dhcp server as another option.
For wireshark, if I connect staticly & then run udhcpc to see what happens will it show me what is going on when the PC looks for a DHCP server?
also,
if I recall correctly, Slitaz 3.0 used to work just fine on my network.
I'm going to boot up that CD & see what happens.
Now, if it doesn't give me an IP through dhcp then i'm going to just reset my router & clear the settings because there is a lot of old stuff in there & I may of done something that is causing it to ignore the client.
If it does work then I can use that to compare the two to see what is going on differently.
I'd prefer not to take the easy way out & figure out what is going on.
It'll take longer, but i'm learning & do see the potential of this distro & would like to stick with it.
thank you for your help.
Offline
Ok, slitaz 3 doesn't boot into X on my laptop but when I ran tazx it downloaded the video drivers without me doing anything. LOL!
I can't get to a desktop, but I have internet at the command prompt.
So what is different with networking between Slitaz 3 & 4 ?
Offline
@nitrogen_widget,
With regards to your question on wireshark, yes, it will show the dhcp requests going out and dhcp responses coming from the router, if any. Also, udhcpc has some extra options you may want to try - I would run udhcpc in the foreground so that the process can be repeated, if needed.
It may be worthwhile saving the trace so that you can compare with a Slitaz 3 trace.
Also, while you got wireshark running, you may want to try out the dhcp-client which is available on the repo. This should give you sufficient info to draw any conclusions and hopefully come up with a good solution.
With regards to difference between Slitaz 3 and 4, probably someone like mojo will be able to provide you with an answer. I am just a Slitaz user and not involved in the development cycle so sorry, cannot answer that question. As wild guess, I suspect 4 may have an more up to date udhcpc script.
Offline
If I read wireshark correctly, the broadcast to any dhcp servers went out & my router did nothing. It was like it wasn't there. I don't know why, but even with my laptop plugged directly into my router I still couldn't get an ip address.
I was going to troubleshoot this further but decided i just don't have the time to play around with dhcp clients & just made my dsl modem my dhcp server & I'm posting this now from my fresh laptop install of slitaz with working network at first boot.
Offline
@nitrogen_widget, this is very strange but at least you have a good working solution. If you do find some spare time, it may be worthwhile comparing wireshark traces when running Slitaz 4 and one of your other distros (or alternatively, running a different dhcp client) - just curious to know what is going on!
Offline
[ Generated in 0.017 seconds, 8 queries executed - Memory usage: 1.59 MiB (Peak: 1.77 MiB) ]