Some new information: Today I used a Huawei Mobile Broadband Stick and, as expected, the USB insert was detected and notified normally. Then followed two network notifications:
Airport Disconnected (null) IP Address Updated No Routable IP Addresses. Note: Airport was already disconnected and I got no message. Turning Airport back on, it joins fine but I don't see the Notification until I drop the USB modem connection. On Saturday, November 24, 2012 9:49:23 AM UTC, Mark Foster wrote: > > Nothing out of the ordinary in the console. The log for a network state > change looks remarkably the same whether growl is running or not. > > I cannot think of anything that makes this MacBook Pro different to your > machine any more than it is different to the Mac Pro on my desk at work or > the machines of the other people reporting the problem. Mine are both > different hardware, different OS versions, different network connection > (wi-fi vs eth). The similarity is that they both run Growl 2.0 and HWG 2.0. > Both worked up to the point that HWG was updated via the App store. > > (Side Note: The App Store model of software downloads means that I cannot > revert to the previous, working, version. This is a bad thing. The old way > was better.) > > On the laptop I would normally expect to see notifications as it joins the > network on wake from sleep. I see nothing. The only time I see anything > network related is on HWG app startup and only then if the preference is > ticked to show connected devices at launch. At that time only do I see a > notification about Airport Connected and IP address updated. > > On the desktop I would expect to see notifications when switching > locations, i.e. switching interface priority so that I can use a different > IP address. I would also expect to see notifications when plugging or > unplugging interface cables. Again, I see nothing. > > I don't really know what else to say. What worked in the previous version > does not work now. > > On Saturday, November 24, 2012 1:17:55 AM UTC, Rudy Richter wrote: >> >> that all looks ok, is anything logged to console.app when you perform the >> actions you feel should be presenting you with notifications? (the reason >> we're stepping through these hoops is because I'm running the app store >> build and i get notifications when i wake my computer from sleep as it >> reestablishes its wifi connection, if i turn wifi off/on, if i change >> locations in the network prefpane, etc) >> >> so any information you can think of that might make your configuration >> different would be helpful. >> >> it might also be helpful if you could detail step by step what you're >> doing when it should be firing a notification, maybe something in your >> steps will hint at where the problem lies. >> >> -rudy >> >> On Friday, November 23, 2012 1:52:02 PM UTC-5, Mark Foster wrote: >>> >>> Daniel, Rudy, >>> >>> "Show Connected Devices at Launch" is off. Turning it on and relaunching >>> HWG does show a whole bunch of alerts, including one for the IP address. >>> Leaving it on has no effect on the lack of notifications when switching >>> networks, connecting or disconnecting. >>> >>> The Network Monitor is enabled in HWG preferences. The only one disabled >>> is the keyboard monitor. >>> All notification preferences are set to their default values except for >>> the display style which is "Bubbles". Changing this to a different style >>> does not help. >>> >>> As requested, output of ifconfig -a (hw addrs anonymised, IP addrs NAT >>> anyway): >>> >>> pointyheed:~ markf$ ifconfig -a >>> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 >>> options=3<RXCSUM,TXCSUM> >>> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 >>> inet 127.0.0.1 netmask 0xff000000 >>> inet6 ::1 prefixlen 128 >>> gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280 >>> stf0: flags=0<> mtu 1280 >>> en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 >>> options=2b<RXCSUM,TXCSUM,VLAN_HWTAGGING,TSO4> >>> ether 00:1b:xx:xx:xx:xx >>> media: autoselect >>> status: inactive >>> fw0: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 2030 >>> lladdr 00:19:e3:ff:xx:xx:xx:xx >>> media: autoselect <full-duplex> >>> status: inactive >>> en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 >>> ether 00:17:xx:xx:xx:xx >>> inet6 fe80::217:xxxx:xxxx:xxxx%en1 prefixlen 64 scopeid 0x6 >>> inet 172.16.0.4 netmask 0xffffff00 broadcast 172.16.0.255 >>> media: autoselect >>> status: active >>> >>> As mentioned: this all worked perfectly in the previous version. >>> >> -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/growldiscuss/-/FfdxuDeaniMJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
