HomeForums → Recent Posts
11,765 posts found
|
May 19, 2008 4:49pm
finsprings
268 posts
|
Topic: BUG SDK / New connection required each time? This was after I restored my original plist, where original already had multiple connections from the bug from a random MAC. These enXXs were in the original plist but I’d already -’ed them from the Network utility. I will try going back to a nice empty list and start the bug multiple times and hope it comes up as en2 or something reasonable. I’ll then try starting ICS and stopping it to see if I can reboot the bug, get ICS, undo it and come back up again without needing to reboot my Mac. Fingers crossed…. BTW, thanks for all the help and support Al. It’s much appreciated. |
|
May 19, 2008 4:21pm
agordon
74 posts
|
Topic: BUG SDK / New connection required each time? Okay, so that makes sense. When your Mac boots and tries to instantiate ICS between two interfaces, and one of then doesn’t even exist because the BUG’s not plugged in, something in some part of the Mac’s network stack is probably in an unhappy state. Come to think of it, I think I did not keep ICS enabled on my Mac other than when I wanted the BUG to have access, and disabled it afterward. So, let me get another thing straight: You’re clearing out your plist file and are still seeing interface numbers in the double digits? :shock: Are you also perhaps not removing those stale interfaces from the Network preference pane (Network GUI)? I realize now that I had not mentioned that specifically before, but I seem to recall doing that on my Mac prior to editing the plist file. You know, it would be nice if you could either edit a text file OR just work in a GUI in the Mac, but it seems often, you need to do both. :x |
|
May 18, 2008 2:42pm
finsprings
268 posts
|
Topic: BUG SDK / New connection required each time? After last post, rebooted Mac and bug came back as en27 again (I disabled Internet Sharing before rebooting). |
|
May 18, 2008 2:38pm
finsprings
268 posts
|
Topic: BUG SDK / New connection required each time? Next I left the bug running and restarted the Mac, with the USB cable detached. Once the Mac was up I plugged in the USB cable and the bug came up as en27 - it was en21 before.Here's my rc diffs so you can see it shouldn't be randomizing anything: root@BUG /etc/rc.d # diff rc.conf.save rc.conf I shutdown and restarted the bug 5 times in a row and each time it came back up properly as en27. I then went in and turned on Internet Sharing from Airport to en27. I could ping yahoo. I then restarted the bug and it did *not* come up this time - I could the same "failed to name" error. So, I am wondering if Internet Sharing is what's causing the problem. I tried turning it off, but it seems like once it's in the "failed to name" state it won't come back. |
|
May 18, 2008 2:25pm
finsprings
268 posts
|
Topic: BUG SDK / New connection required each time? Al,After our discussion, I restored the original plist, rebooted, reinstalled the CDC driver and rebooted again. I started up the bug and it connected. I turned on Internet Sharing and the bug could ping yahoo.com. I shutdown the bug from serial and turned it back on. It came up, en21 went live and again the bug could ping yahoo.com. I shut it back down, turned it back on and this time en21 didn't go green. I tried several more times without success. The difference in the Mac's system.log is the following line: May 18 14:14:03 dfindlay-macbook configd[14]: InterfaceNamer: failed to name the interface, kr=0xe00002bcWhen it works I see: May 18 14:04:41 dfindlay-macbook kernel[0]: 0 0 AppleUSBCDCACMData: start - Find CDC driver failedWhen it doesn't work I see: May 18 14:17:48 dfindlay-macbook kernel[0]: 0 0 AppleUSBCDCACMData: start - Find CDC driver failedBSD help says: Why it would work a couple of times then stop working, I don't know. |
|
May 17, 2008 11:02pm
finsprings
268 posts
|
Topic: BUG SDK / New connection required each time? I’ve cleared out the networks plist several times. The problem I’m having now is the one I’ve listed before showing an error in the Mac’s syslog, where the USB-to-IP connection simply doesn’t come up at all. It’s up on the bug’s side, which I can see from the handylink serial connection via minicom, but it won’t come up on the Mac, and the Mac gives me that error. This happens regardless of whether I’ve got tweaked rc.conf/rc.local or the originals. I booted the bug 3 times without touching its files and the Mac only brought up an enX once out of those 3. I have a minimal plist right now, so I don’t think that’s the problem but it’s possible I guess. It just seems like that USB/IP ko is being flakey. If I could get the bug to show up on the Mac consistently I can do the rest to get the sharing working, but as you said this is pointless until the bug comes up with the same MAC on the Mac, as otherwise you need to redo the Internet Sharing. So, my problem right now is in getting the Mac not to give me that CDC driver failure when the bug starts its usb0 interface. |
|
May 17, 2008 9:15pm
agordon
74 posts
|
Topic: BUG SDK / New connection required each time? If you can ping a host on the internet by IP but not by name, it's a DNS problem. Most likely, the /etc/resolv.conf file on your BUG has the IP address of a computer that is not a DNS resolver, or is refusing to accept DNS connections from your BUG.That file should contain a line like this: nameserver 4.2.2.2 ...where the IP address is that of a known server acting as a DNS resolver. The address listed above is a DNS server on the internet, so you'll need to make Internet Sharing work before that will work for you. Alternatively, you can enter the IP address of your router, if it has DNS server capabilities, or of a DNS server provided by your ISP. Next: I'm not sure what the limit is on enx devices is on OS X, but I'm sure it can't be unlimited. If I were in the situation you describe, I would do the following: First, unplug your BUG from your Mac. Next, on the Mac: Backup /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist, then edit it to remove all instances of RNDIS/Ethernet Gadget. Disable Internet Sharing. Reboot. A side note: Since Internet Sharing maps traffic between two specific network adapters, your really want to get your Mac working so that it does not create a new connection each time you plug the BUG in, or reboot your BUG or Mac. If Network Sharing is setup to direct your BUG's packets on en4 to the internet through your ethernet adapter en0, and the next time you plug in your BUG, it's no longer mapped as en4 on the Mac, your Internet Sharing isn't going to work. So, back to business... Plug the BUG back in. As long as the networking config files on the BUG aren't totally fubar, the interface should come back, hopefully with a low number (like en2 or en3, unless you have other interfaces configured, like virtual interfaces from VMWare or Parallels or whatever). Log into the BUG and configure it as previously specified: Comment out or remove the appropriate line in /etc/rc.d/rc.conf, and make the changes in /etc/rc.d/rc.local. If you decide to back out of these changes for some reason, you'll need to undo all of the changes. This means editing both files I just previously mentioned, not just one or the other. If you delete the line in rc.conf rather than comment it out, make sure to backup that file, or at least make a note of exactly what you did so that you can undo it later. If you have half-done or half-undone these changes, you may need to re-flash your BUG's MMC card, basically resetting it to defaults. I'm not sure how to describe what needs to be done any better than this. But, if you're still having problems, and are running OS X 10.5, maybe I can do a remote desktop connection and walk through the config with you some time. The new features in iChat in Leopard are pretty nice for remote support. |
|
May 17, 2008 11:08am
finsprings
268 posts
|
Topic: BUG SDK / New connection required each time? So now it's in the state again where it won't come up at all: I put the original rc.conf and rc.local back and the Mac won't connect to it:May 17 11:02:29 dfindlay-macbook kernel[0]: USBF: 1024. 42 AppleUSBHubPort: Port 1 of Hub at 0x3d000000 reported error 0xe00002ed while doing set feature (resetting port)
|
|
May 17, 2008 11:05am
finsprings
268 posts
|
Topic: BUG SDK / New connection required each time? I went back to the original rc.conf and rc.local and the Mac again prompted me for a new enX. I then went to the modified ones and it didn't, so I think it was finding the old en7 somehow even though I had deleted it from Network. So I edited rc.local to make the host_addr end in ec instead of eb, just to make it different. Then when I restarted the bug it came up and prompted me for en9. I rebooted it again and en9 went live by itself.I turned on Internet Sharing from Airport to en9 and I set the router and DNS Server fields of en9 to 192.168.13.1 to match my home network. After that I was able to ping yahoo.com by domain name from the bug. So it looked good...but to be sure I shut the bug down and started it back up. This time en9 didn't connect itself and the Mac's system log again shows an error: May 17 10:59:01 dfindlay-macbook kernel[0]: 0 0 AppleUSBCDCACMData: start - Find CDC driver failedSo I can get this to work once, but not twice. Any ideas? |
|
May 17, 2008 10:46am
finsprings
268 posts
|
Topic: BUG SDK / New connection required each time? So I made the changes, including adding the default route, and I got to the point where I could ping yahoo.com by IP address, but not by DNS name. Still, progress!However, I shut the bug down again from the serial connection and next time it came up the Mac didn't recognize it. I noticed the following in the system.log on the Mac:I tried rebooting the Mac but it didn't help, and I tried putting the original rc.conf and rc.local back and it didn't help, so I don't think it's necessarily related. I'm going to try reinstall the USB ether driver and see what that does. |
