Heron and wifi - Ubuntu

This is a discussion on Heron and wifi - Ubuntu ; Have been trying out Hardy Heron (8.04) beta (plus all the updates) to gain experience ready for when it's a stable release. I'm hoping that this one will finally give me the functionality to ditch MS for good. But wifi ...

+ Reply to Thread
Results 1 to 10 of 10

Thread: Heron and wifi

  1. Heron and wifi

    Have been trying out Hardy Heron (8.04) beta (plus all the updates) to gain
    experience ready for when it's a stable release. I'm hoping that this one
    will finally give me the functionality to ditch MS for good.
    But wifi still seems to be the area where I am having trouble.

    In summary:
    I used the restricted drivers (Sytem>Admin>Hardware Drivers) to load bcm43xx
    for my Broadcom BCM 4306 wifi PCI card; (it worked well in Gutsy this way.)
    Couldn't establish a wifi connection to the router (ethernet is fine) but
    then I stumbled across advice that bcm43xxwas deprecated and I should use
    b43-fwcutter instead. One article, which others said had worked, told me to
    add a command line (which stupidly I have forgotten and lost the web page!!)
    but nada.

    Network Manager shows I have a wireless connection.
    Can't ping the router
    wifi radar says I am "connected " to my SSID but says no IP address
    allocated. I am using DHCP.
    Can't ping the router.
    Router is up for every other PC here.
    lspci shows a Broadcom 4306 LAN controller (version3)...
    Confused that ifconfig shows I have more than one wifi ??

    Here it is:
    ------------------------------------------------------------------------------------------------
    eth0 Link encap:Ethernet HWaddr 00:08:54:46:10:7d
    inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
    inet6 addr: fe80::208:54ff:fe46:107d/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:118 errors:0 dropped:0 overruns:0 frame:0
    TX packets:218 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:18617 (18.1 KB) TX bytes:35550 (34.7 KB)
    Interrupt:5 Base address:0xc800

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:1464 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1464 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:73200 (71.4 KB) TX bytes:73200 (71.4 KB)

    wlan0 Link encap:Ethernet HWaddr 00:0f:66:74:9a:a5
    UP 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)

    wlan0:avahi Link encap:Ethernet HWaddr 00:0f:66:74:9a:a5
    inet addr:169.254.7.217 Bcast:169.254.255.255 Mask:255.255.0.0
    UP BROADCAST MULTICAST MTU:1500 Metric:1

    wmaster0 Link encap:UNSPEC HWaddr
    00-0F-66-74-9A-A5-00-00-00-00-00-00-00-00-00-00
    UP BROADCAST RUNNING 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)
    -------------------------------------------------------------------------------
    And iwconfig gives:

    ---------------------------------------------
    lo no wireless extensions.

    eth0 no wireless extensions.

    wmaster0 no wireless extensions.

    wlan0 IEEE 802.11g ESSID:"sally000"
    Mode:Managed Frequency:2.462 GHz Access Point: 00:18:4D:49:2C:0E
    Tx-Power=27 dBm
    Retry min limit:7 RTS thrff Fragment thr=2346 B
    Encryption keyff
    Link Quality:0 Signal level:0 Noise level:0
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0

    ----------------------------------------------

    Also since installing b43-fwcutter I can't get into
    Sys>Admin>Hardware-drivers by the GUI and I don't know how else to do this
    using terminal. It generates a "jockey-gtk closed unexpectedly" crash
    report.

    I know it's still a beta but anyone able to offer any helpful advise? There
    seems so much "info" out there using google on wifi that it's all rather
    confusing. If bcm43xx is not to be used then surprised it's still in the
    repos. Or is it still necessary for some older cards?
    Cheers






  2. Re: Heron and wifi

    David wrote:

    > Network Manager shows I have a wireless connection.
    > Can't ping the router
    > wifi radar says I am "connected " to my SSID but says no IP address
    > allocated. I am using DHCP.
    > Can't ping the router.
    > Router is up for every other PC here.
    > lspci shows a Broadcom 4306 LAN controller (version3)...
    > Confused that ifconfig shows I have more than one wifi ??
    >
    > Here it is:
    > ------------------------------------------------------------------------------------------------
    > eth0 Link encap:Ethernet HWaddr 00:08:54:46:10:7d
    > inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
    > inet6 addr: fe80::208:54ff:fe46:107d/64 Scope:Link
    > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    > RX packets:118 errors:0 dropped:0 overruns:0 frame:0
    > TX packets:218 errors:0 dropped:0 overruns:0 carrier:0
    > collisions:0 txqueuelen:1000
    > RX bytes:18617 (18.1 KB) TX bytes:35550 (34.7 KB)
    > Interrupt:5 Base address:0xc800
    >
    > lo Link encap:Local Loopback
    > inet addr:127.0.0.1 Mask:255.0.0.0
    > inet6 addr: ::1/128 Scope:Host
    > UP LOOPBACK RUNNING MTU:16436 Metric:1
    > RX packets:1464 errors:0 dropped:0 overruns:0 frame:0
    > TX packets:1464 errors:0 dropped:0 overruns:0 carrier:0
    > collisions:0 txqueuelen:0
    > RX bytes:73200 (71.4 KB) TX bytes:73200 (71.4 KB)
    >
    > wlan0 Link encap:Ethernet HWaddr 00:0f:66:74:9a:a5
    > UP 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)
    >



    The interface configurations for the above look good, but I suspect the
    following one is a source of your trouble. Notice the 169 IP range? That
    indicates a failure of a DHCP server to provide a valid IP.

    This appears to be a virtual interface (avahi) running on the wlan0
    interface. Virtual interfaces are used so you can have routes to
    different networks than the main interface. But the 169 IP (and
    associated broadcast address) is a failure flag, and not valid. The mask
    is likely also incorrect depending on your network. Try the
    255.255.255.0 for the mask.


    > wlan0:avahi Link encap:Ethernet HWaddr 00:0f:66:74:9a:a5
    > inet addr:169.254.7.217 Bcast:169.254.255.255 Mask:255.255.0.0
    > UP BROADCAST MULTICAST MTU:1500 Metric:1



    I won't comment on the wireless stuff because I have so little
    experience with WiFi. I also have no experience with Network Manager, so
    no help there.

    Check that 169 "red flag" and see if it is the problem. Do you really
    need that virtual interface, or could it be a typo that was saved in
    /etc/network/interfaces ?

    Since you know about running sudo ifconfig -a you can read man
    interfaces and man ifconfig and figure out how to make changes. Or just
    use a text editor to remove the wlan0:avahi stanza from
    /etc/network/interfaces (or better, comment it out and see if it was
    really needed). If you previously set up networking for another
    location, it could be for your network at work.

    --
    John

    No Microsoft, Apple, Intel, Trend Micro, nor Ford products were used in the preparation or transmission of this message.

    The EULA sounds like it was written by a team of lawyers who want to tell me what I can't do. The GPL sounds like it was written by a human being, who wants me to know what I can do.

  3. Re: Heron and wifi


    : The interface configurations for the above look good, but I suspect the
    : following one is a source of your trouble. Notice the 169 IP range? That
    : indicates a failure of a DHCP server to provide a valid IP.

    Are you sure about this? It depends on the implementation of Avahi.



  4. Re: Heron and wifi


    : ------------------------------------------------------------------------------------------------
    : eth0 Link encap:Ethernet HWaddr 00:08:54:46:10:7d
    : inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
    : inet6 addr: fe80::208:54ff:fe46:107d/64 Scope:Link
    : UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    : RX packets:118 errors:0 dropped:0 overruns:0 frame:0
    : TX packets:218 errors:0 dropped:0 overruns:0 carrier:0
    : collisions:0 txqueuelen:1000
    : RX bytes:18617 (18.1 KB) TX bytes:35550 (34.7 KB)
    : Interrupt:5 Base address:0xc800
    :
    : lo Link encap:Local Loopback
    : inet addr:127.0.0.1 Mask:255.0.0.0
    : inet6 addr: ::1/128 Scope:Host
    : UP LOOPBACK RUNNING MTU:16436 Metric:1
    : RX packets:1464 errors:0 dropped:0 overruns:0 frame:0
    : TX packets:1464 errors:0 dropped:0 overruns:0 carrier:0
    : collisions:0 txqueuelen:0
    : RX bytes:73200 (71.4 KB) TX bytes:73200 (71.4 KB)
    :
    : wlan0 Link encap:Ethernet HWaddr 00:0f:66:74:9a:a5
    : UP 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)
    :
    : wlan0:avahi Link encap:Ethernet HWaddr 00:0f:66:74:9a:a5
    : inet addr:169.254.7.217 Bcast:169.254.255.255 Mask:255.255.0.0
    : UP BROADCAST MULTICAST MTU:1500 Metric:1
    :
    : wmaster0 Link encap:UNSPEC HWaddr
    : 00-0F-66-74-9A-A5-00-00-00-00-00-00-00-00-00-00
    : UP BROADCAST RUNNING 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)
    : -------------------------------------------------------------------------------
    : And iwconfig gives:
    :
    : ---------------------------------------------
    : lo no wireless extensions.
    :
    : eth0 no wireless extensions.
    :
    : wmaster0 no wireless extensions.
    :
    : wlan0 IEEE 802.11g ESSID:"sally000"
    : Mode:Managed Frequency:2.462 GHz Access Point:
    00:18:4D:49:2C:0E
    : Tx-Power=27 dBm
    : Retry min limit:7 RTS thrff Fragment thr=2346 B
    : Encryption keyff
    : Link Quality:0 Signal level:0 Noise level:0
    : Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    : Tx excessive retries:0 Invalid misc:0 Missed beacon:0
    :
    : ----------------------------------------------
    :


    This is all normal and by design.
    Sadly, I can't find any further details on this.



  5. Re: Heron and wifi

    Cork Soaker wrote:
    > : The interface configurations for the above look good, but I suspect the
    > : following one is a source of your trouble. Notice the 169 IP range? That
    > : indicates a failure of a DHCP server to provide a valid IP.
    >
    > Are you sure about this? It depends on the implementation of Avahi.



    Nope. Sure about death and taxes only. ;-)

    Didn't I more or less say it was just an educated guess?

    This guess is based upon seeing the 169s before, and they always brought
    failures to my networks, and for those who reported the same 169 IP
    range in various help groups.

    I have no idea what Avahi is except what I just Googled. I don't use
    WiFi nor DHCP. The three together sounds like a good chance for trouble.

    About two weeks ago I mentioned this 169 problem to someone. Maybe it
    was in the Debian group. To many groups -- too little memory. ;-)

    Anyway, here are some references:

    http://en.wikipedia.org/wiki/Link-local_address

    Or 966,000 hits: http://www.google.com/search?q=ip+169

    Google found two for +Avahi +169:

    http://ubuntuforums.org/showthread.php?t=472159

    http://ubuntuforums.org/archive/index.php/t-522728.html


    --
    John

    No Microsoft, Apple, Intel, Trend Micro, nor Ford products were used in the preparation or transmission of this message.

    The EULA sounds like it was written by a team of lawyers who want to tell me what I can't do. The GPL sounds like it was written by a human being, who wants me to know what I can do.

  6. Re: Heron and wifi

    I have a kid's laptop (old Fujitsu Lifebook) with a very similar
    broadcom chipset, that did not work properly with Hardy in the way you
    described.

    My solution was to just go back to Gutsy. Gutsy works great with it --
    zero problems. I will try hardy again on that laptop in a few months
    when the dust settles.

    I

    On 2008-04-12, David wrote:
    > Have been trying out Hardy Heron (8.04) beta (plus all the updates) to gain
    > experience ready for when it's a stable release. I'm hoping that this one
    > will finally give me the functionality to ditch MS for good.
    > But wifi still seems to be the area where I am having trouble.
    >
    > In summary:
    > I used the restricted drivers (Sytem>Admin>Hardware Drivers) to load bcm43xx
    > for my Broadcom BCM 4306 wifi PCI card; (it worked well in Gutsy this way.)
    > Couldn't establish a wifi connection to the router (ethernet is fine) but
    > then I stumbled across advice that bcm43xxwas deprecated and I should use
    > b43-fwcutter instead. One article, which others said had worked, told me to
    > add a command line (which stupidly I have forgotten and lost the web page!!)
    > but nada.
    >
    > Network Manager shows I have a wireless connection.
    > Can't ping the router
    > wifi radar says I am "connected " to my SSID but says no IP address
    > allocated. I am using DHCP.
    > Can't ping the router.
    > Router is up for every other PC here.
    > lspci shows a Broadcom 4306 LAN controller (version3)...
    > Confused that ifconfig shows I have more than one wifi ??
    >
    > Here it is:
    > eth0 Link encap:Ethernet HWaddr 00:08:54:46:10:7d
    > inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
    > inet6 addr: fe80::208:54ff:fe46:107d/64 Scope:Link
    > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    > RX packets:118 errors:0 dropped:0 overruns:0 frame:0
    > TX packets:218 errors:0 dropped:0 overruns:0 carrier:0
    > collisions:0 txqueuelen:1000
    > RX bytes:18617 (18.1 KB) TX bytes:35550 (34.7 KB)
    > Interrupt:5 Base address:0xc800
    >
    > lo Link encap:Local Loopback
    > inet addr:127.0.0.1 Mask:255.0.0.0
    > inet6 addr: ::1/128 Scope:Host
    > UP LOOPBACK RUNNING MTU:16436 Metric:1
    > RX packets:1464 errors:0 dropped:0 overruns:0 frame:0
    > TX packets:1464 errors:0 dropped:0 overruns:0 carrier:0
    > collisions:0 txqueuelen:0
    > RX bytes:73200 (71.4 KB) TX bytes:73200 (71.4 KB)
    >
    > wlan0 Link encap:Ethernet HWaddr 00:0f:66:74:9a:a5
    > UP 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)
    >
    > wlan0:avahi Link encap:Ethernet HWaddr 00:0f:66:74:9a:a5
    > inet addr:169.254.7.217 Bcast:169.254.255.255 Mask:255.255.0.0
    > UP BROADCAST MULTICAST MTU:1500 Metric:1
    >
    > wmaster0 Link encap:UNSPEC HWaddr
    > 00-0F-66-74-9A-A5-00-00-00-00-00-00-00-00-00-00
    > UP BROADCAST RUNNING 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)
    > And iwconfig gives:
    >
    > lo no wireless extensions.
    >
    > eth0 no wireless extensions.
    >
    > wmaster0 no wireless extensions.
    >
    > wlan0 IEEE 802.11g ESSID:"sally000"
    > Mode:Managed Frequency:2.462 GHz Access Point: 00:18:4D:49:2C:0E
    > Tx-Power=27 dBm
    > Retry min limit:7 RTS thrff Fragment thr=2346 B
    > Encryption keyff
    > Link Quality:0 Signal level:0 Noise level:0
    > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    > Tx excessive retries:0 Invalid misc:0 Missed beacon:0
    >
    >
    > Also since installing b43-fwcutter I can't get into
    > Sys>Admin>Hardware-drivers by the GUI and I don't know how else to do this
    > using terminal. It generates a "jockey-gtk closed unexpectedly" crash
    > report.
    >
    > I know it's still a beta but anyone able to offer any helpful advise? There
    > seems so much "info" out there using google on wifi that it's all rather
    > confusing. If bcm43xx is not to be used then surprised it's still in the
    > repos. Or is it still necessary for some older cards?
    > Cheers
    >
    >
    >
    >
    >


  7. Re: Heron and wifi

    I'm aware of LL :-)

    I can't find a specific definition for Avahi, but it certainly wouldn't be
    routable, hence why LL wouldn't be too bad.

    Anyway, it's the wlan0 device that needs an IP address anyway, so you can
    ignore wlan0:avahi.

    Zeroconf, to me, seems like a whole load of problems waiting to happen.



  8. Re: Heron and wifi

    On Sat, 12 Apr 2008 09:31:29 +0100, David wrote:

    > Have been trying out Hardy Heron (8.04) beta (plus all the updates) to gain
    > experience ready for when it's a stable release. I'm hoping that this one
    > will finally give me the functionality to ditch MS for good.
    > But wifi still seems to be the area where I am having trouble.


    I read everything.

    Can you configure wlan0 for static IP?



  9. Re: Heron and wifi

    David wrote:
    > Have been trying out Hardy Heron (8.04) beta (plus all the updates) to gain
    > experience ready for when it's a stable release. I'm hoping that this one
    > will finally give me the functionality to ditch MS for good.
    > But wifi still seems to be the area where I am having trouble.
    >
    > In summary:
    > I used the restricted drivers (Sytem>Admin>Hardware Drivers) to load bcm43xx
    > for my Broadcom BCM 4306 wifi PCI card; (it worked well in Gutsy this way.)
    > Couldn't establish a wifi connection to the router (ethernet is fine) but
    > then I stumbled across advice that bcm43xxwas deprecated and I should use
    > b43-fwcutter instead. One article, which others said had worked, told me to
    > add a command line (which stupidly I have forgotten and lost the web page!!)
    > but nada.
    >
    > Network Manager shows I have a wireless connection.
    > Can't ping the router
    > wifi radar says I am "connected " to my SSID but says no IP address
    > allocated. I am using DHCP.
    > Can't ping the router.
    > Router is up for every other PC here.
    > lspci shows a Broadcom 4306 LAN controller (version3)...
    > Confused that ifconfig shows I have more than one wifi ??
    >
    > Here it is:
    >
    > wlan0 IEEE 802.11g ESSID:"sally000"
    > Mode:Managed Frequency:2.462 GHz Access Point: 00:18:4D:49:2C:0E
    > Tx-Power=27 dBm
    > Retry min limit:7 RTS thrff Fragment thr=2346 B
    > Encryption keyff
    > Link Quality:0 Signal level:0 Noise level:0
    > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    > Tx excessive retries:0 Invalid misc:0 Missed beacon:0
    >
    > ----------------------------------------------
    >
    > Also since installing b43-fwcutter I can't get into
    > Sys>Admin>Hardware-drivers by the GUI and I don't know how else to do this
    > using terminal. It generates a "jockey-gtk closed unexpectedly" crash
    > report.
    >
    > I know it's still a beta but anyone able to offer any helpful advise? There
    > seems so much "info" out there using google on wifi that it's all rather
    > confusing. If bcm43xx is not to be used then surprised it's still in the
    > repos. Or is it still necessary for some older cards?
    > Cheers
    >
    >
    >
    >
    >


    Using the 8.04 beta, I found that I had to manually edit some files.
    I removed all but the wireless connection in /etc/network/interfaces (as
    I am only using wireless on that box) and I had to manually edit the
    /etc/wifi-radar.conf file. Otherwise, wifi-radar would not let me
    create/save info. Once I created a valid config it worked. Sometimes
    wifi-radar seems to blow away the config file so I had to create a
    backup. Not sure what causes this.

    --
    Norman
    Registered Linux user #461062

  10. Re: Heron and wifi


    "Meat Plow" wrote in message
    news:1pnfhj.hmt.17.5@news.alt.net...
    > On Sat, 12 Apr 2008 09:31:29 +0100, David wrote:
    >
    >> Have been trying out Hardy Heron (8.04) beta (plus all the updates) to
    >> gain
    >> experience ready for when it's a stable release. I'm hoping that this one
    >> will finally give me the functionality to ditch MS for good.
    >> But wifi still seems to be the area where I am having trouble.

    >
    > I read everything.
    >
    > Can you configure wlan0 for static IP?
    >
    >

    Sorry for the delay in replying. Other things got in the way.
    Tried many things including static IP, turning off WEP etc but still no
    luck.

    I hope that when the final release happens this is fixed but I very much
    doubt it.
    How sad that wireless is so poor in Ubuntu. It's the deal breaker for me.
    Cheers



+ Reply to Thread