RE: p4p1 changed to p2p1; works oddly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: users-bounces@xxxxxxxxxxxxxxxxxxxxxxx 
> [mailto:users-bounces@xxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Michael D. Berger
> Sent: Wednesday, November 09, 2011 20:15
> To: Fedora Users
> Subject: p4p1 changed to p2p1; works oddly
> 
> In my last thread I reported that my network stopped working.
> Looking around, and comparing things with a CentOS 5 box, I 
> discovered that:
> 
>     net:p4p1 was not there
>     net:p2p1 was there
> 
> I did not do anything intentional to eliminate p4p1.  But I 
> was fiddling with libipq, so I cannot guarantee innocence.
> 
> So I did a "cp ifcfg-p4p1 ifcfg-p2p1", did a little editing, 
> and now p2p1 as a working network interface.  Note that I 
> have only one network card.
> 
> It works, but not properly:
>    it won't start on boot;
>    it starts slowly and sometimes print odd stuff.
> 
> Below is activity immediately after boot to level 3, and 
> login as root.  Note that the line containing the number 
> "98.919229" looks like something I might have typed, but it 
> is not.  It just appeared.  The "link up" and "link down" 
> lines appeared at roughly one second intervals.
> 
> It would be nice if I could get it to work correctly.
> 
> Thanks for your thoughts.
> 
> Mike,
> 
>    [root@mbrc40 ~]# !ping
>    ping 192.168.9.1
>    connect: Network is unreachable
>    [root@mbrc40 ~]# ifup p2p1
>    [   95.867559] r8169 0000:04:00.0: p2p1: link down
>    [   95.869349] r8169 0000:04:00.0: p2p1: link down
>    [root@mbrc40 ~]# [   98.919229] r8169 0000:04:00.0: p2p1: link up
>    [  100.036870] r8169 0000:04:00.0: p2p1: link down
>    [  104.012908] r8169 0000:04:00.0: p2p1: link up
>    [  105.130557] r8169 0000:04:00.0: p2p1: link down
>    [  109.126512] r8169 0000:04:00.0: p2p1: link up
>    [  110.245207] r8169 0000:04:00.0: p2p1: link down
>    [  114.283083] r8169 0000:04:00.0: p2p1: link up
>    [  115.401772] r8169 0000:04:00.0: p2p1: link down
>    [  119.355809] r8169 0000:04:00.0: p2p1: link up
>    [  120.474498] r8169 0000:04:00.0: p2p1: link down
>    [  123.171879] r8169 0000:04:00.0: p2p1: link up
> 
>    [root@mbrc40 ~]# !ping
>    ping 192.168.9.1
>    PING 192.168.9.1 (192.168.9.1) 56(84) bytes of data.
>    64 bytes from 192.168.9.1: icmp_req=1 ttl=255 time=1.29 ms
>    64 bytes from 192.168.9.1: icmp_req=2 ttl=255 
> 
[...]

I add that systemd logging is still broken.  I think that
I need to get p4p1 back.

  [root@mbrc40 myDaemon]# make enable
  /bin/systemctl enable myDaemon.service
  ln -s '/etc/systemd/system/myDaemon.service'
'/etc/systemd/system/multi-user.target.wants/myDaemon.service'
  Failed to issue method call: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the network
connection was broken.
make: *** [enable] Error 1

--
Michael D. Berger
m.d.berger@xxxxxxxx
http://www.rosemike.net/
  
 

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines


[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux