As I said in my subject, I don't want to turn anyone off from reading this e-mail. If you genuinely think you can help, just know, no suggestion is stupid. Especially considerring that I've tried everything under the son. At this point, I'm willing to try literally just about anything including throwing the mac across the room, then screaming! LOL!
So, a little bit of very brief background. I have a Dell computer which apparently has just bitten the dust. It's about 10 years old. This really isn't rellavent more so than to say I just put it in storage until I figure out what to do with it. I also have a Yamaha hifi dolby/prologic surround sound 5.1 receiver. This receiver has an ethernet port on the back of it which allows you to connect it to an internet wired connection for things like Pandora, Spottify, etc. Get to the point, Chris, you say. I am, I am, I promise. Stick with me on this. Just hear me out for a sec as this is actually incredibly rellavant to my problem. So, here's the issue. The receiver doesn't have wifi capability. It's stricly only able to connect to a network via a hardwired ethernet connection. Well, this would be all fine and dandy except for one thing. I don't have room on my desk with my router to set the receiver up. Therefore, I had to set the receiver up across the room beside that old busted Dell machine. Due to home regulations set by my landlord, I cannot tack anything to the walls, nor use double sided tape, or anything of the sort, nor can I tack anything across my ceiling. Therefore, there went using a token ringed topology, let alone a PTP host/client configuration. Therefore, what I was doing was connecting via wifi to my home network's router across the room. This supplied internet connectivity to me on the Dell machine. Then what I did was, I ran an ethernet cable from the on board ethernet port on the back of the Dell tower to the ethernet port on my Yamaha receiver. Then, finally, in Windows XP, I was able to go under Control Panel, Networks, select both my wifi connection as well as my ethernet connection, hit the application's key, or rather, right click, same thing, and then select bridge connectio n from the context menu. Once done, it made my wifi connection carry down to my ethernet port. So, in other words, as long as I have an internet connection on my wifi end, then whatever got plugged into the ethernet port hardwired used that exact same connection. So, now that the Dell system has gone to its grave, and is there rotting, LOL! just kidding, seriously though, I'm trying to achieve this same exact thing with Yosemite 10.10.3. No matter what the heck I do though, try as I may, I just can! not! seem to get this to work. So far, I went into System Preferences, Sharing. Under here, I first selected the internet sharing service in the table. Then, making sure the box in the first column of that table row was unchecked, I moved down and set the share from popup button to wifi. Then, in the share to table, I made sure that the only thing checked was ethernet. Then, I went back to the services table, checked the box beside the Internet sharing service, and started up the service. I should add that all the above things were done while the ethernet cable was plugged in both to the mac, and to the receiver. I then tried getting the receiver to go out online via internet, but it wouldn't. I wondered if something got turned off in the receiver's menus, so I tested with an old laptop I have which doesn't even have wifi ability, only ethernet. It didn't work there either, so trust me. It's not the receiver here that's at fault. I went back to System Prefernces, then to network. I noticed that the first service in the table was eithernet, not wifi, even though wifi is my primary means to connect. Therefore, I went to the actions popup button, and to service order, I think it's called... something to that effect. Using the Voiceover's drag and drop abilities, I dragged the connections around and got them so wifi was first, then Ethernet was second. This way, wifi takes higher priority. This didn't fix the issue. Next, still in network settings, on the ethernet connection, I noticed though connected, it said that it had a self assigned IP address, and will not be able to connect to the internet. The IP address it's showing is: 169.254.105.163. Obviously, from another machine on my network than the mac, if I try pinging this address, it times out instantly. I can't even do a tracert query. It doesn't even complete the first hop if I do. Under Network Settings on the mac, on the Ethernet connection in the table, the IPV4 settings are set to DHCP, however, I tried DHCP with manual address, and entered that in by hand. I've even tried going to manual in the popup button, and entering everything totally! by hand such as the IPV4 address, the router address, the dns server address, which is the same as my router, being my router is serving as my DHCP server to all clients on the network. I've released and renew the dns IP, but it just comes back to the same IP as above. 169.154.X.X isn't even within the subnet range of my router, which is within 192.168.X.X. My router IP is: 192.168.1.1. For future reference, this router is a Linksys WRT1900AC with Linksys Smart Wifi as its web admin interface. I tried turning off internet sharing, rebooting, making sure no active wifi connection was in progress, and that my ethernet cable was disconnected from the mac, then turned on network sharing making sure it was set up from wifi, and to ethernet. Then, I plugged the ethernet cable back in. NO good, I still got the self assigned IP listed above. The 169.154.105.163. I tried looking at the mac address settings on my router, etc. and they all look fine. There are no conflicting IP's on the network's subnet either. I made sure when manually enterring things, that my subnet masc was 255.255.255.0. Still no good. I've gone in and removed the ethernet service from system prefs, network, then readding it. My location is set to automatic, although I tried making a brand new location just to see if that would help. It didn't. I created a new user account on the system, logged in as it, and had the same issue, so it's not an issue with my user account being corrupted a bit. I ran disc permission check/repair from the recovery partition, and all was fine there. When I verified permissions, they all came back as being perfectly intact correctly. Finally, at my whit's end, I went into terminal, and executed ifconfig -l I noticed that all my network adaptors look correct, and seem to be functioning. I then attempted to stop internet sharing with: sudo launchctl unload -w\ /System/Library/LaunchDaemons/com.apple.InternetSharing.plist Apparently, that plist file no longer is there in Yosemite like it was in Mavericks. BTW, I dono if this would a worked in Yosemite, what I'm trying to do. I never had a need to try, as back then, I just bridged with my Windows machines. Finally, I turned off Internet Sharing again from the GUI, not the CLI. I restarted, then went back to terminal. I then issued ifconfig -l I determined that my ethernet and my wireless adaptors are on en0, and en1. Therefore, I typed: sudo ifconfig bridge create this created a bridge called bridge0. I then proceeded to add those two interfaces to the bridge... sudo ifconfig bridge0 addm en0 addm en1 This seemed to work correctly. I don't recall where I found the file, but it was under /etc. I found a conf file which did show the two adapters attached to the bridge. I know this is really a piss poor way to do this, as then, I'd have to recreate the bridge, and re-add the interfaces manually by hand. I'll fix that later with a cron job which I'll place in the default system profile via a shell script, but I can't do that until I get things working to start with. LOL! Right now, doing that is the least of my concerns! Anyway, after doing this, I tried to see if I had any success. Of corse, go figure, I didn't. So, yeah, I'm totally outta options. I've even gone into my router and changed the dns/dhcp settings so they matched what OSX is automatically giving that stupid ethernet connection. Obviously, this meant having to reconfigure all other clients on my network which was a royal pain in the ass! I diddit though, so you can't say I didn't try! Ha ha. Lord though! Even that! didn't work! Folks, I'm throwing my hands in the air! I give the heck up! I dono what's left to do! I literally! have tried every ***ing thing under the sun that I know to try! Any thoughts would be profoundly appreciated. If you can help me get this working, I'm so determined, I'll even be willing to put a tip on my blog on how to properly set up bridging, and you better believe I'll give you public credit by name! OK guys, have at it! See if you can figure this one out! Eat your hearts out! LOL! Chris. <--- Mac Access At Mac Access Dot Net ---> To reply to this post, please address your message to mac-access@mac-access.net 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/mac-access@mac-access.net/>. Subscribe to the list's RSS feed from: <http://www.mail-archive.com/mac-access@mac-access.net/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/>
