5:07 p.m.
Hi All;
I can plug a hard wire into my laptop and boot up, it comes up connected.
I can boot up with no connection and then tell it to connect to the
wireless it works fine, but if later I click disconnect for the wireless
and plug the hard wire (cat 6) cable in it says it's "connecting" but
spins until I finally reboot.
Can anyone help me debug this?
Thanks in advance
8:20 a.m.
On 24.03.2014 08:52, Ahmad Samir wrote:
On 22 March 2014 04:40, CS_DBA <cs_dba(a)consistentstate.com>
wrote:
>
> On 03/21/2014 05:43 PM, Ed Greshko wrote:
>
>> On 03/22/14 07:39, CS_DBA wrote:
>>
>>> On 03/21/2014 05:33 PM, Ed Greshko wrote:
>>>
>>>> On 03/22/14 06:07, CS_DBA wrote:
>>>>
>>>>> I can plug a hard wire into my laptop and boot up, it comes up
>>>>> connected.
>>>>>
>>>>> I can boot up with no connection and then tell it to connect to the
>>>>> wireless it works fine, but if later I click disconnect for the
wireless
>>>>> and plug the hard wire (cat 6) cable in it says it's
"connecting" but
>>>>> spins until I finally reboot.
>>>>>
>>>> Have you tried unplugging the cable, waiting a bit, and plugging it in
>>>> again?
>>>>
>>>> Seems to work fine, but when I try and move from wireless to em1
"on
>>> the fly" I see the issue
>>>
>> I don't quite understand.... Are you saying.....
>>
>> You boot up with no connection and then tell it to connect to the
>> wireless it works fine. You then disconnect from wireless, plug in the
>> cable, status becomes "connecting" but never connects. Then, you uplug
the
>> cable, wait a bit, plug it back in....and all is well.
>>
>> Is that what you are doing/seeing? You don't need to reboot...but you do
>> need to plug-in, plug-out, plug-in?
>>
>>
> Here's what I see
>
> 1) If I boot up with no cable plugged in it auto connects to the wireless
> immediately
>
> 2) If I boot up with the cable (cat 5/6) plugged in it immediately
> connects to em1
>
> 3) If I boot with the cable plugged in, then unplug the cable it connects
> to the wireless quickly
>
> 4) If I boot up with the cable plugged in, disconnect the cable, then
> re-connect it it re-connects to em1 fine
>
>
[...]
> 5) however if I boot up with no cable, let it connect to the wireless,
> then plug in the cable it attempts to connect to em1 but never completes
>
>
I don't have wireless, but I see a similar issue, if I boot the machine
with the ethernet cable disconnected, then connect it after boot, the
system says/thinks the connection is up but it doesn't work, can't even
ping the router.
Some workarounds:
- Disconnecting the cable, waiting a few seconds then replugging it makes
it work
- Bringing the connection down manually, then up seems to work too either
using:
# ifdown em1 && sleep 5 && ifup em1
or:
# ip link set em1 down && sleep 5 && ip link set em1 up
(em1 is the connection name on my box).
restarting the NetworkManager service doesn't seem to have an effect. With
or without DHCP doesn't matter too. This is with Intel I217-V ethernet chip
and the e1000 kernel module.
nmcli connection/device up/down/(dis)connect id/ifname
man 1 nmcli
Perhaps file a bug report, you and cs_dba?
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=Ne...
poma
2:52 a.m.
On 22 March 2014 04:40, CS_DBA <cs_dba(a)consistentstate.com> wrote:
On 03/21/2014 05:43 PM, Ed Greshko wrote:
> On 03/22/14 07:39, CS_DBA wrote:
>
>> On 03/21/2014 05:33 PM, Ed Greshko wrote:
>>
>>> On 03/22/14 06:07, CS_DBA wrote:
>>>
>>>> I can plug a hard wire into my laptop and boot up, it comes up
>>>> connected.
>>>>
>>>> I can boot up with no connection and then tell it to connect to the
>>>> wireless it works fine, but if later I click disconnect for the wireless
>>>> and plug the hard wire (cat 6) cable in it says it's
"connecting" but
>>>> spins until I finally reboot.
>>>>
>>> Have you tried unplugging the cable, waiting a bit, and plugging it in
>>> again?
>>>
>>> Seems to work fine, but when I try and move from wireless to em1 "on
>> the fly" I see the issue
>>
> I don't quite understand.... Are you saying.....
>
> You boot up with no connection and then tell it to connect to the
> wireless it works fine. You then disconnect from wireless, plug in the
> cable, status becomes "connecting" but never connects. Then, you uplug
the
> cable, wait a bit, plug it back in....and all is well.
>
> Is that what you are doing/seeing? You don't need to reboot...but you do
> need to plug-in, plug-out, plug-in?
>
>
Here's what I see
1) If I boot up with no cable plugged in it auto connects to the wireless
immediately
2) If I boot up with the cable (cat 5/6) plugged in it immediately
connects to em1
3) If I boot with the cable plugged in, then unplug the cable it connects
to the wireless quickly
4) If I boot up with the cable plugged in, disconnect the cable, then
re-connect it it re-connects to em1 fine
[...]
5) however if I boot up with no cable, let it connect to the
wireless,
then plug in the cable it attempts to connect to em1 but never completes
I don't have wireless, but I see a similar issue, if I boot the machine
with the ethernet cable disconnected, then connect it after boot, the
system says/thinks the connection is up but it doesn't work, can't even
ping the router.
Some workarounds:
- Disconnecting the cable, waiting a few seconds then replugging it makes
it work
- Bringing the connection down manually, then up seems to work too either
using:
# ifdown em1 && sleep 5 && ifup em1
or:
# ip link set em1 down && sleep 5 && ip link set em1 up
(em1 is the connection name on my box).
restarting the NetworkManager service doesn't seem to have an effect. With
or without DHCP doesn't matter too. This is with Intel I217-V ethernet chip
and the e1000 kernel module.
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
--
Ahmad Samir
11:17 a.m.
On 22.03.2014 03:40, CS_DBA wrote:
Here's what I see
1) If I boot up with no cable plugged in it auto connects to the
wireless immediately
2) If I boot up with the cable (cat 5/6) plugged in it immediately
connects to em1
3) If I boot with the cable plugged in, then unplug the cable it
connects to the wireless quickly
4) If I boot up with the cable plugged in, disconnect the cable, then
re-connect it it re-connects to em1 fine
5) however if I boot up with no cable, let it connect to the wireless,
then plug in the cable it attempts to connect to em1 but never completes
$ repoquery -i NetworkManager-config-server
or perhaps systemd-networkd(Wired)/NetworkManager(Wireless) combination.
poma
9:35 a.m.
On 03/22/14 18:43, Ed Greshko wrote:
On 03/22/14 20:37, Tim wrote:
> CS_DBA wrote:
>>> 5) however if I boot up with no cable, let it connect to the
>>> wireless, then plug in the cable it attempts to connect to em1
>>> but never completes
> Ed Greshko sent
>> Right.... But, if after doing #5 you unplug the cable, wait a
>> bit (30 seconds or more), and then re-plug does the second
>> attempt succeed? If not, output of ifconfig please.
> If it took anything more than 5 seconds to sort that out, I'd be
> concerned, or very peeved at crap design. These days we have
> computers with GHz processors, not kHz.
>
Yes, of course. But humans have a very bad habit of under estimating
time. I tend to err on the long side. But that isn't germane to the
problem at hand.
have you ever tried county by 'monkey'?
1 monkey, 2 monkey, 3 monkey, ,,, ?
or
1 mississippi, 2 mississippi, 3 mississippi, ,,, ?
look at a watch or clock while you do it. a little practice and
you will be close on up to several minutes.
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
7:37 a.m.
CS_DBA wrote:
> 5) however if I boot up with no cable, let it connect to the
> wireless, then plug in the cable it attempts to connect to em1 but
> never completes
Ed Greshko sent
Right.... But, if after doing #5 you unplug the cable, wait a bit
(30
seconds or more), and then re-plug does the second attempt succeed?
If not, output of ifconfig please.
If it took anything more than 5 seconds to sort that out, I'd be
concerned, or very peeved at crap design. These days we have computers
with GHz processors, not kHz.
--
[tim@localhost ~]$ uname -rsvp
Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64
All mail to my mailbox is automatically deleted, there is no point
trying to privately email me, I will only read messages posted to the
public lists.
George Orwell's '1984' was supposed to be a warning against tyranny, not
a set of instructions for supposedly democratic governments.
7:43 a.m.
On 03/22/14 20:37, Tim wrote:
CS_DBA wrote:
>> 5) however if I boot up with no cable, let it connect to the
>> wireless, then plug in the cable it attempts to connect to em1 but
>> never completes
Ed Greshko sent
> Right.... But, if after doing #5 you unplug the cable, wait a bit (30
> seconds or more), and then re-plug does the second attempt succeed?
> If not, output of ifconfig please.
If it took anything more than 5 seconds to sort that out, I'd be
concerned, or very peeved at crap design. These days we have computers
with GHz processors, not kHz.
Yes, of course. But humans have a very bad habit of under estimating time. I tend to err
on the long side. But that isn't germane to the problem at hand.
--
Getting tired of non-Fedora discussions and self-serving posts
6:09 a.m.
On 03/21/14 22:40, CS_DBA wrote:
On 03/21/2014 05:43 PM, Ed Greshko wrote:
Here's what I see
1) If I boot up with no cable plugged in it auto connects to the
wireless immediately
2) If I boot up with the cable (cat 5/6) plugged in it immediately
connects to em1
3) If I boot with the cable plugged in, then unplug the cable it
connects to the wireless quickly
4) If I boot up with the cable plugged in, disconnect the cable, then
re-connect it it re-connects to em1 fine
5) however if I boot up with no cable, let it connect to the wireless,
then plug in the cable it attempts to connect to em1 but never completes
I'm not a fan of NetworkManager, but it is what it is, with that said, I
tried a similar thing, going from WiFi to wired on Centos 6 with the
same problem, however rather than reboot, I restarted NM and got it
working. When I was done I pulled the wire and got it to re-connect
with WiFi with no issues.
Pete
--
Unencumbered by the thought process.
-- Click and Clack the Tappet brothers
9:40 p.m.
On 03/21/2014 05:43 PM, Ed Greshko wrote:
On 03/22/14 07:39, CS_DBA wrote:
> On 03/21/2014 05:33 PM, Ed Greshko wrote:
>> On 03/22/14 06:07, CS_DBA wrote:
>>> I can plug a hard wire into my laptop and boot up, it comes up connected.
>>>
>>> I can boot up with no connection and then tell it to connect to the wireless
it works fine, but if later I click disconnect for the wireless and plug the hard wire
(cat 6) cable in it says it's "connecting" but spins until I finally
reboot.
>> Have you tried unplugging the cable, waiting a bit, and plugging it in again?
>>
> Seems to work fine, but when I try and move from wireless to em1 "on the
fly" I see the issue
I don't quite understand.... Are you saying.....
You boot up with no connection and then tell it to connect to the wireless it works fine.
You then disconnect from wireless, plug in the cable, status becomes
"connecting" but never connects. Then, you uplug the cable, wait a bit, plug it
back in....and all is well.
Is that what you are doing/seeing? You don't need to reboot...but you do need to
plug-in, plug-out, plug-in?
Here's what I see
1) If I boot up with no cable plugged in it auto connects to the
wireless immediately
2) If I boot up with the cable (cat 5/6) plugged in it immediately
connects to em1
3) If I boot with the cable plugged in, then unplug the cable it
connects to the wireless quickly
4) If I boot up with the cable plugged in, disconnect the cable, then
re-connect it it re-connects to em1 fine
5) however if I boot up with no cable, let it connect to the wireless,
then plug in the cable it attempts to connect to em1 but never completes
6:39 p.m.
On 03/21/2014 05:33 PM, Ed Greshko wrote:
On 03/22/14 06:07, CS_DBA wrote:
> I can plug a hard wire into my laptop and boot up, it comes up connected.
>
> I can boot up with no connection and then tell it to connect to the wireless it works
fine, but if later I click disconnect for the wireless and plug the hard wire (cat 6)
cable in it says it's "connecting" but spins until I finally reboot.
Have you tried unplugging the cable, waiting a bit, and plugging it in again?
Seems to work fine, but when I try and move from wireless to em1 "on the
fly" I see the issue
6:43 p.m.
On 03/22/14 07:39, CS_DBA wrote:
On 03/21/2014 05:33 PM, Ed Greshko wrote:
> On 03/22/14 06:07, CS_DBA wrote:
>> I can plug a hard wire into my laptop and boot up, it comes up connected.
>>
>> I can boot up with no connection and then tell it to connect to the wireless it
works fine, but if later I click disconnect for the wireless and plug the hard wire (cat
6) cable in it says it's "connecting" but spins until I finally reboot.
> Have you tried unplugging the cable, waiting a bit, and plugging it in again?
>
Seems to work fine, but when I try and move from wireless to em1 "on the fly" I
see the issue
I don't quite understand.... Are you saying.....
You boot up with no connection and then tell it to connect to the wireless it works fine.
You then disconnect from wireless, plug in the cable, status becomes
"connecting" but never connects. Then, you uplug the cable, wait a bit, plug it
back in....and all is well.
Is that what you are doing/seeing? You don't need to reboot...but you do need to
plug-in, plug-out, plug-in?
--
Getting tired of non-Fedora discussions and self-serving posts
6:33 p.m.
On 03/22/14 06:07, CS_DBA wrote:
I can plug a hard wire into my laptop and boot up, it comes up
connected.
I can boot up with no connection and then tell it to connect to the wireless it works
fine, but if later I click disconnect for the wireless and plug the hard wire (cat 6)
cable in it says it's "connecting" but spins until I finally reboot.
Have you tried unplugging the cable, waiting a bit, and plugging it in again?
--
Getting tired of non-Fedora discussions and self-serving posts
9:50 p.m.
On 03/22/14 10:40, CS_DBA wrote:
Here's what I see
1) If I boot up with no cable plugged in it auto connects to the wireless immediately
2) If I boot up with the cable (cat 5/6) plugged in it immediately connects to em1
3) If I boot with the cable plugged in, then unplug the cable it connects to the wireless
quickly
4) If I boot up with the cable plugged in, disconnect the cable, then re-connect it it
re-connects to em1 fine
5) however if I boot up with no cable, let it connect to the wireless, then plug in the
cable it attempts to connect to em1 but never completes
Right.... But, if after doing #5 you unplug the cable, wait a bit (30 seconds or more),
and then re-plug does the second attempt succeed? If not, output of ifconfig please.
--
Getting tired of non-Fedora discussions and self-serving posts
3686
days inactive
3689
days old
12 comments
7 participants
participants (7)
-
Ahmad Samir -
CS DBA -
Ed Greshko -
g -
Pete Geenhuizen -
poma -
Tim