You are not logged in.
I was just wondering if anybody else was having an issue with the new version of dhcpcd 5.0.6-1? I upgraded and it's not working for me. Everything appeared all right but no Internet. When I tried to restart the network connection it would pop back a message saying it was throttling MTU to 576 but then nothing. I downgraded back to the previous version and now it is working again. I'm running dnsmasq and arno-iptables-firewall (both as per the Wiki instructions). Anybody got a clue?
Thanks
Last edited by harryNID (2009-07-24 22:16:15)
In solving a problem of this sort, the grand thing is to be able to reason backward. That is a very useful accomplishment, and a very easy one, but people do not practice it much. In the everyday affairs of life it is more useful to reason forward, and so the other comes to be neglected. There are fifty who can reason synthetically for one who can reason analytically. --Sherlock Holmes
Offline
The same here. Have a fresh install system with dhcpcd 5.0.6-1 and my card power off just after dhcdcd throttle MTU to 576, desconfiguring (i think) my card. Result: no internet! Even ping at loopback address doesn't work.
Downgraded to dhcpcd 5.0.4-1 and everything seems perfect, no throttling.
Offline
Thanks for the info "kronig". At least I know I'm not the only one. I wanted to see if others were having the same issue before filing a bug report. I'm thinking this is an upstream problem though so we'll see.
This happened to me with the version before last and I figured out it was Firehol causing it. I switched to Arno's and everything worked again there. This time no matter what I did I couldn't get it to respond.
In solving a problem of this sort, the grand thing is to be able to reason backward. That is a very useful accomplishment, and a very easy one, but people do not practice it much. In the everyday affairs of life it is more useful to reason forward, and so the other comes to be neglected. There are fifty who can reason synthetically for one who can reason analytically. --Sherlock Holmes
Offline
Thanks for the heads-up!
I struggled with this yesterday and have been kicking myself for not thinking of the downgrade solution.
I can confirm downgrading to 5.0.4-1 solved it for me too.
Peace
E5o
Offline
Same issue by me too.
Dhclient solved the problem for me.
Offline
If you think the MTU as required by your DHCP server is wrong, you can either fix the DHCP server or stop requesting the MTU in /etc/dhcpcd.conf
dhcpcd-5.0.5 defaulted to requesting the MTU as we should assume the DHCP server is correctly configured for it.
Offline
That did it!
Thanks "rsmarples"
It's working fine now.
I just had to comment out:
option interface_mtu
in /etc/dhcpcd.conf
Thanks Again!
Last edited by harryNID (2009-07-24 22:15:47)
In solving a problem of this sort, the grand thing is to be able to reason backward. That is a very useful accomplishment, and a very easy one, but people do not practice it much. In the everyday affairs of life it is more useful to reason forward, and so the other comes to be neglected. There are fifty who can reason synthetically for one who can reason analytically. --Sherlock Holmes
Offline
Bliss!
Thanks rsmarples!
I can confirm
#option interface_mtu
did solve it for me too.
Great
E5o
Last edited by E5o (2009-07-29 09:29:04)
Offline
It will be usefull for so much users, because so much complains arrives about the new dhcpcd version, maybe it's worth to add to the wiki, if it really can solve the problem.
Offline
Does not solve it for me. What else can I try?
We met up with the aliens and guess what? They have no word for fluffy!
Offline