I had similar issues a few years ago, and did finally get them solved, but it was with tiger/leopard, not 10.9, so your mileage may vary. However, Eventually, I had to change all my 192.168.1.x addresses to 192.2.x addresses, assign static ips to the various machines, and then share my ethernet connection via wireless. This last step is the only thing that made it all work, no matter how I plugged things together, I had the same problem you did with the self assigned ip of 169.254.x.x. I notice the mac always does this if it doesn't immediately see a network connection when it starts up, even if the network is there, if osx doesn't see it for whatever reason, you get a 169.254 ip, and there's nothing you can do about it, until you get it to play nice with your other network parts. Stick with it though, it does work, it's just a matter of making sure everything is talking, which sometimes could be something as simple as the fact that you're using a crossover cable instead of a straight through one. Most equipment is smart enough these days to deal with this automatically, but sometimes, various equipment doesn't know how to do so, and so it just throws an error, even though it works perfectly well on other pieces of equipment. Also, I had a serious problem, because once I shared my wireless connection via ethernet, osx tried to assign everything to the 192.168.1.x framework, even though I'd told it not to do so, (this is why I had to change everything over to 192.168.2.x networking), it was because no matter what I did, osx refused to use the ip numbers I wanted, and so I had to retool everything to fit osx. As it turned out though, this wasn't a bad thing, because it has thwarted local hackers many times, who expected to find everything on the 192.168.1.x ip ranges. Now I just laugh at them when I see such silly attempts to penetrate my wireless network (which isn't advertised). As I recall, (this was a few years you understand, and my memory isn't what it used to be) I had to fiddle with the ipfwadm rules in the firewall settings too, most of which had to be done from terminal. I finally came to the conclusion that apple really had no clue what they were doing when they setup this whole internet sharing thing, and reconfigured the whole thing from scratch, without telling the mac it was supposed to share, and eventually (after much ip jockeying) I got it all to work. Of course, after all that, Our entire network setup changed, and all the work wound up being useless, but I was proud I did get it working, even if it was only for a few months until I purchased the required equipment to make the whole bridging thing unnecessary. Now we just use a 48-port cisco hub/router plugged into a linksys wrt54G wireless router to handle everything we need to plugin, and it works nicely. However, I feel your pain on this one, as I recall, setting up that internet sharing thing was a serious pain, and as I said, I eventually just gave up on getting the apple supplied easy method to work, and just built it all out manually on the network. Occasionally though, I still share my wireless network via ethernet (reverse of what I needed to do initially) because when our main internet is down, I hook the mac to a cell hotspot, then share my ethernet connection via wireless, and everything just works just as if I'm still plugged in the proper way, only now all the traffic flows in reverse. Not sure why it works so easily now, when it gave me so much trouble before, because I'm sure I didn't go through all that configuring on this imac, all that configuring happened on the mini, but it still works, so who knows. But, anyway, the solution for me was to ignore the apple provided configurations, and setup up static ips (as you've done) configure proper gateways between the mac and the outside world (I didn't use bridging for this) and once I added the proper default routs (remember, in most cases, automated processes won't override default routes) everything finally flowed properly. It was a major pain, and it took me days to figure it all out, but have faith that you too can eventually get it all working. hope this helps. If you need more details, let me know, and I'll try to remember what it was I did in more detail.
<--- Mac Access At Mac Access Dot Net ---> To reply to this post, please address your message to [email protected] You can find an archive of all messages posted to the Mac-Access forum at the list's public Mail Archive: <http://www.mail-archive.com/[email protected]/>. Subscribe to the list's RSS feed from: <http://www.mail-archive.com/[email protected]/maillist.xml> As the Mac Access Dot Net administrators, we always strive to ensure that the Mac-Access E-Mal list remains malware, spyware, Trojan, virus and worm-free. However, this should in no way replace your own security strategy. We assume neither liability nor responsibility should something unpredictable happen. Please remember to update your membership preferences periodically by visiting the list website at: <http://mail.tft-bbs.co.uk/mailman/listinfo/mac-access/options/>
