Fedora Linux Support Community & Resources Center
  #1  
Old 13th July 2012, 05:49 AM
schorschi Offline
Registered User
 
Join Date: Jun 2009
Posts: 10
windows_7ie
BCM5782 NIC can not bind to TCP/IP, never acquires IP address?

Have a broadcom 5782 NIC, worked great with Windows OS, Fedora 16 and older, CentOS 6.2 and older, etc. But in Fedora 17, the BCM5782 NIC can not bind to TCP/IP, never acquires IP address? Anyone run into this issue?

---------- Post added at 09:49 PM ---------- Previous post was at 08:58 PM ----------

A bit more information, static IP assignment in ifcfg-* file for BCM5782 NIC works. Explicit disable of NetworkManager, enable of network service, no impact. Consistent error in /var/log/messages... NODHCPOFFERS received. Yet, link state it good. Disabled SELinux, and iptables and ip6tables services, no benefit. DHCP client never seems to receive response, yet know for fact DHCP server is alive and well, only Fedora 17 having issue. Did full update of Fedora 17, under static IP, then re-established DHCP configuration in ifcfg-* file for BCM5782 NIC. No change. This issue almost seems regressive, very old issue was similar.
Reply With Quote
  #2  
Old 13th July 2012, 06:43 AM
rajhat Offline
Registered User
 
Join Date: Jul 2012
Location: India
Posts: 4
linuxredhatfirefox
Re: BCM5782 NIC can not bind to TCP/IP, never acquires IP address?

I have the same problem in RHEL 6, ifconfig eth0 ip work fine for me
setup also not working. i am using dual os may be thats problem.!!!!!!!!
Reply With Quote
  #3  
Old 13th July 2012, 07:14 AM
stevea's Avatar
stevea Offline
Registered User
 
Join Date: Apr 2006
Location: Ohio, USA
Posts: 8,346
linuxfirefox
Re: BCM5782 NIC can not bind to TCP/IP, never acquires IP address?

NICs don't bind to tcp/ip - so lets not make up nonsense terminology.

"NODHCPOFFERS" - yes this means the DHCP request was sent and your router or whatever did not reply with an offer. Look into the config for your DHCP server.

DO NOT - edit the ifcfg-* files manually - EVER. one typo and you have an un-debuggable mess and they can be linke in tricky non-obvious ways.
.
Use system-config-network for the network or right-click the NM icon for NM.
__________________
None are more hopelessly enslaved than those who falsely believe they are free.
Johann Wolfgang von Goethe
Reply With Quote
Reply

Tags
acquires, address, bcm5782, bind, nic, tcp or ip

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
(98)Address already in use: make_sock: could not bind to address [::]:443 eliassal Servers & Networking 0 28th October 2010 09:31 AM
could not bind to address message HTTPD pailott Servers & Networking 11 26th October 2009 10:54 PM
APACHE will not start, can't bind to IP address timebandit Servers & Networking 10 5th January 2009 07:57 PM
Apache Can't Bind to Address? WhiteFeather Servers & Networking 3 24th May 2008 10:02 AM
FC6 -Apache unable to bind to address justdou Servers & Networking 1 19th April 2007 08:31 AM


Current GMT-time: 23:07 (Wednesday, 19-06-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat