Yukon: Ethernet and Airport: Ethernet addresses...

Sorry if this is a stupid question but what is the difference between the Yukon and Airport ethernet addresses? Are they supposed to be the same or different? Many thanks.

Hello,
The first is Ethernet, the second is Wifi or Airport, those are two different interfaces, now as far as addresses go, they have IP addresses, and Hardware Machine Access Code addresses.
To see them, At the Apple Icon at top left>About this Mac, then click on More Info, then click on Network.
It can be confusing how the term Ethernet is used.

Similar Messages

Connecting iMac to Network via Ethernet Cable and Airport Express

I've tried reading through the various posts to solve this and haven't had any luck. Any help is deeply appreciated.
I have an Airport Extreme as my main 'base' for our wireless network. I purchased an Airport Express today with the notion of using it to extend my network in the following way: I want to connect an iMac and a printer to the Express (using Ethernet and USB cables respectively) and have the Express serve as a remote for the Extreme base. I have found a number of websites saying this is possible, but none explain how to. I tried the WDS option, which failed to work. I later saw posts here saying that was not the optimal scenario. I'm afraid the 5Ghz/2.4Ghz settings combined with Airport ID addresses has pushed me past my competency!
Thanks in advance for your help and a festive St. Patrick's Day!

Temporarily, power down the AirPort Express and concentrate on the AirPort Extreme to make sure that it is functioning correctly, can get an Internet connection, etc.
A complete power cycle of the network is often useful when you have been making changes. Power everything off, order is not important.
Wait a moment, (or wait 5-10 minutes if you have cable modem), then power up the modem first and let it run a moment by itself. Then power up the AirPort Extreme the same way.
Check your settings using AirPort Utility - Manual Setup
Click the Wireless tab just below the row of icons
If the Wireless Mode setting is "Create a wireless network", make sure there is a check mark next to "Allow this network to be extended"
Note the exact setting for Security that is being used
Update to save any changes
Post back when the AirPort Extreme is functioning correctly as above and we'll tackle the AirPort Express

Mini Server, bridging Ethernet and Airport ?

Hy there.
I´ve got a Mini running 10.5 Server with Ethernet en0 and Airport. To set up for testing I´m want to set the Mini as a wireless bridge. With NAT and the gateway assistant, I`m only apple to set up routing with a block Airport -> Ethernet. In detail:
Ethernet 192.168.100.x
Airport 192.168.1.x with NAT and DHCP
Clients connected to Airport aren`t able to go to the 192.168.100.x network.
Is it possible to bridge the two nic´s?
Aggregation won´t work on Airport.
Thanks for reply.

The network configuration details and the goals aren't entirely clear (to me) here, so I'm going to shot-gun several answers here. I (also) don't know how experienced you are with IP networking and terminology; apologies in advance.
"Bridging" occurs at layer 2 and is relatively comparable to a network cable or such and thus arguably transparent to network traffic (you can't "see" a bridge at the network layer any more than you can "see" a hunk of network cable), where "Routing" is layer 3 and typically involves IP addresses and a routing stack. Bridging doesn't involve an IP network address for the intermediate device, where routing does.
Your Mac Mini here lacks bridging capabilities, and would be either a non-routing host or (with two NICs and a requirement to route traffic through) an IP router.
Various Airport devices can be configured as routers or as bridges. The default configuration is the former; as a WiFi router. If you want to run the Airport as a bridge, then it won't have an IP address. Various folks will refer to a WiFi device set up as a bridge as an Access Point, as well.
Depending on the subnet configuration (and I will here assume you are using two subnets here, the 192.168.1.0/24 and 192.168.100.0/24 subnets) and if you're using your Airport as a router in 192.168.100.0/24, you'll need to set up the Mac Mini or another IP router-capable device in 192.168.1.0/24 as the default IP gateway (default router) within the Airport configuration. That default gateway (router) will itself need a path to the wider Internet, and routes to other subnets.
Getting a Mac to function as a router and as a network gateway (and with NAT and firewall) is possible, but you'll have to set up the default routes appropriately. It's generally (far!) easier to use an external box for this purpose; a dedicated firewall and NAT and router box. It's also something I typically prefer; having users and software configuration changes and the usual sorts of activity found on a Mac OS X or Mac OS X Server occurring on a firewall can risk (accidentally, unintentionally) open up a remote exposure.
If you want to use link aggregation with Mac OS X Server, then you'll usually need a network switch capable of IEEE 802.3ad link aggregation. AFAIK, Airport doesn't provide link aggregation.
Apropos of nothing else in this reply, if you're planning to eventually use VPNs (tunnels), I'd also suggest getting out of 192.168.0.0/16 address range (and into 10.0.0.0/8 or 172.16.0.0/12, per RFC 1918), everybody uses that, and various tunnels need unique subnets both locally and on the target end of the connection.
Here's an intro to [networking, routers and firewall|http://labs.hoffmanlabs.com/node/275] pieces, and a previous discussion of [IEEE 802.3ad link aggregation, BGP and such|http://discussions.apple.com/thread.jspa?messageID=9141545] here in the forums.
It's my general preference to block access to the LAN with a dedicated firewall/NAT/router box for the reasons described above as well as other reasons; that box can act as the default gateway for all subnets, as well.
If I've entirely missed your question with the above answer(s), hopefully the above can help us get a little closer to your particular goal and an appropriate solution.

It seems like Ethernet backup and Airport backup goes in different ways

Since one month a go, I've been having problems with Time Machine backup over Time Capsule.
When I run Time Machine through Ethernet, there is no problem. Fast and clean. In the Console there is not any error message.
I unplug ethernet cable, start airport, and in the next copy appears: "Bulk settings atributes failled", several times. Few backups after it will appear problems with a "file path" and few after will appear "deep traversal".
I plug the Ethernet cable, disconnect airport and I forced to re-index the image bundle. Few backups correct with Ethernet. Unplug ethernet, connect airport, and again the same history.
It seems like Ethernet backup and Airport backup goes in different ways.
Permissions are corrected and there is no problems in any disc with First Aid.
¿Any idea?. Thanks in advance.

I am having the same issue. I have three layered elements as three columns in the body of the page. When I add the farthest right element it pushes the other left elements to the bottom of the page. There are aren't any other elements on the page.
Is this a CSS issue? I thought about exporting to Dreamweaver and fixing it there but would like to take the easy route first.

Swirching between ethernet and airport

i want to be able to easily switch back and forth between ethernet and airport. is there a way to do this without having to plug/unplug the ethernet cable from airport to computer, computer to airport each time i want to change?

Try the following:
Open System Preferences (gear icon) on the dock
Open Network
Click the small gear icon at the bottom of the connection list area
Click Set Service Order
If Ethernet is at the top of the list and you want to switch to an AirPort connection, drag AirPort to the top of the list. Click OK, Click Apply
If AirPort is at the top of the list and you want to switch to an Ethernet connection, drag Ethernet to the top of the list. Click OK, Click Apply

Ethernet and Airport Interfaces Reversed

I created an image of the new Mac Book Pro(Mid 2010) and slapped it on the new Mac Mini(Mid 2010) and everything worked fine except one thing. I used the DVD that came with the Mac Book Pro(Mid 2010) to create the Master Image.
Under Network Preferences, the Ethernet Interface is displaying the Airport status window(i.e, "Turn Airport On/Off" button is in there). And the Airport Interface is displaying the Ethernet stats.
Any ideas what could be causing this?
Message was edited by: jjpotter

I had the same problem (reversed Ethernet and Airport interfaces) on my 13" MacBook Air after plugging in my Thunderbolt Display. The solution was to go to Network in System Preferences, click the minus symbol under interfaces to delete both of them, click plus to add each one back, then click Apply. Now everything is as it should be.

10.5.6 - Network System Preferences confuses Ethernet and Airport

Since upgrading to 10.5.6 I'm having odd behavior from Airport (which is the only network connection I typically use). Symptoms include Airport turning off when the MacBook wakes from sleep, and Airport not automatically connecting to my home network (to which it regularly reconnected prior to 10.5.6).
The strangest symptom, however, is how Ethernet and Airport are mixed-up in the Network preference pane. I can't post a screen shot (hey Apple - why not?!) so I'll describe:
* In the list of Services on the left side, the service named "Ethernet" has an Airport icon, and the service named "AirPort" has an Ethernet icon.
* When Airport connects, a green dot appears next to the service named "Ethernet".
* When I select the service named "Ethernet" (with the AirPort icon) I see options to the right mostly related to AirPort. Thus, it looks like the Network pref pane has become confused about the names of the services... BUT when I rename the services to correct, then restart the computer, the names go back to the mixed-up situation described above.
Any ideas of how to fix?

Or somebody's playing a prank on him.
AirPort does turn itself off when the computer is asleep. It takes a few seconds for AirPort to reconnect. If the WiFi signal is weak or if there are a lot of network noise, AirPort may not reconnect for a long time.

When connected cable ethernet and assign ip address windows automatically restart

Hello ,
i have windows 7 with 2 NIC ,the additional Network card working fine
but the built-in card when connected cable and assign ip address automatically restart
please help to avoid this problem
thanks

Hi,
first, try the jacky's solution, and verify if the issue is not from Hardware.
and , It looks like the definition of distributed by
policy for more secure.
I remember in the past I've set up for
such a solution for company to prevent
unauthorized access.
Please check with your network administrator
and security if is defined.
You can examine the event log to identify if you have
trigger for action .
you can see this link about the identify if you have trigger :
http://windows.microsoft.com/en-us/windows-vista/automate-tasks-with-task-scheduler-from-windows-vista-inside-out
thanks,
Israel Chemo

Ethernet address setup

Hi,
I am trying to configure a network interface
for IPv4 in Solaris 8.
I setup the IP address, the broadcast
address and the Interface flags using
ioctl commands SIOCSIFADDR,
SIOCSIFBRDADDR and SIOCSIFNETMASK.
How do I setup the MAC address (Ethernet address)
for this interface? Its different from that for
the rest of the network interfaces in this machine,
so the default address doesn't work.
Thanks.

Hello,
I, also, am trying to get the ethernet address for a Solaris machine. I have been looking though the Documentation and using ioctl; however, I do not know what flags to use. The main one I have been working with is SIOCGLIFADDR. Moreover, I use lifr_req.lifr_name, hme0. But, when I print the ethernet address one byte at a time as a unsigned char, my results are not the same as the output using ifconfig -a. Does anyone know how to retrieve the ethernet address on a Solaris machine?
Thank you,
Larry-0 at Conetic

Multiple ethernet addresses vs. IP addresses

Hi,
Using Workgroup Manager on SLS 10.6.4, I have successfully mapped hosts and their MAC addresses to fixed IP addresses within our LAN. All is well, until someone works on the back of one of the Mac Pros and ends up plugging the ethernet cable into jack #2 instead of #1. Now the MAC address is unintentionally different.
I suppose I could make a secondary set of hostnames for ethernet2, but that seems ugly and if you're depending on host foobar being available for a particular printer, but it's now foobar2, that seems unpredictable.
How do you deal with this? I assume this is in the same realm as having a laptop that connects via wireless one day but via an ethernet cable the next day? It's the same host, just not the same MAC address. Does WGM have a way to deal with multiple ethernet addresses?
Thanks,
-- Antoine

ahh, i see.
you're running up against a few limitations here.
bootpd uses MACs to define static mappings.
OD uses MACs to identify nodes/clients.
your client machines have multiple MACs and may present one or the other on the network, depending on whether someone plugs in the wrong port.
here are some options/workarounds off the top of my head:
1. disable the second interface. if you need it for some reason, you'll have to deal with this situation another way.
2. bond the two interfaces. the downside is that you'll need to have both plugged in for optimal results, but you'll have one MAC, i believe.
3. use another dhcp server configured to deny all dhcp requests except those from your approved MACs (en1, let's say).
4. use local MCX and not deal with changing MACs at all. this is a little more difficult to manage, however.
5. manage prefs in some other way, like with puppet or casper, that don't strictly depend on MACs.
i'm sure there are other ways to deal with this situation, but if you're managing these systems, i'd probably just disable the second interfaces. people will learn quickly when they can't access the network. determine if this is more of a technological or a policy/personnel management issue.

Ethernet address conflict

So I have been getting the message:
"The ethernet address you have chosen conflicts with an ethernet address to another computer.
You can't assign the ethernet address xx:xx:xx:xx:xx:xx to two different computers."
Of course I use the actual MAC address in place of the x's, but I have searched the entire directory and this MAC address is not in use.
Now it use to be bound, but was deleted some time ago. I changed its name, to assign it to another lab on campus, and rebound it with this error message. I have a handful of Macs this is happening to. Not sure how to purge or "cleanup" OD. I am sure it needs a good cleaning to clear out its spiderwebs, but flushing OD cache did not help.
Any advice or references would be most appreciated. I am running 10.5.8 Server on an Xserve.
Thank you

Of course I use the actual MAC address in place of the x's, but I have searched the entire directory and this MAC address is not in use.
I don't understand this statement. The message isn't telling you there is a device in your directory with that IP address, it's telling you that there's a machine on your network that's using the address.
That device doesn't have to be in your directory, it doesn't have to be using DHCP.. it's just physically connected. Whether it should be, or whether it should have a different IP address is something you'll need to determine.
Do you know the device it's referring to? The MAC address will map to a physical device. If you don't know which device it is you may be able to wean that information from your switches, which may tell you which port it's connected to (assuming it's a wired ethernet device).

Acsess ethernet address???urgent

How to access the ethernet address of a machine?

Perhaps coul you use the output of ifconfig or ipconfig of the OS and parse it

Ethernet address on two trunked switches at the same time

I have two access layer switches sharing a dot1q trunk ( a port channel with four members), and an HP blade server with one connection (a port channel with two members) into each.. The blade server's connections into each switch is also a dot1q trunk tagging just one vlan. In each connection from the blade server to each switch the mac addresses look very much alike. I determine this by writing a script to log into both switches at once and run the "show mac add int" command on each port channel to the blade server. In tcpdumps the commands are sent typically about .1 - .4 seconds apart on average.
So if the "show mac addr int" command is being run .1 - .4 seconds apart on each switch and have a number of mac addresses in common, would this indicate that these ethernet addresses are flapping in a way that might cause interruptions in packet delivery? Some are experiencing missed pings. No VPCs are used in this configuration - just a pair of either 6509 or 7018 switches connected via a dot1q port channel.

It sounds to me like what you are trying to achieve is network teaming on the HP Blade Server whereby you can have a connection to two different switches.
Natively something like this would cause problems because both switchports (or portchannels) would see the same L2 Address which would then confuse upstream switches as they would not know where to forward frames to. I believe the HP servers may allow this type of setup but it requires a specific config on the teaming element to prevent a single MAC address being shown on two different ports.
Have a read of the whitepaper below:
http://www.hp.com/sbso/bus_protect/teaming.pdf

Re: Updating Marvell Yukon ethernet driver on an Equium A300D

About a month ago I think it was I got an alert on the Toshiba Tempro tool to update a driver for the Marvell Yukon ethernet driver on my laptop. I downloaded the zip file as instructed from the Marvell website (an updated driver was released on 18/8/08) and attempted to install it, but it was then I hit a problem. When I try to install it I'm told a previous version is already installed, and to uninstall the previous version first.
The problem is when I go to the Device Manager and try and find the driver, the only entry there's for a "Marvell Yukon 88E8040T PCI-E Fast Ethernet Controller" , but the driver I was prompted to install was for a Marvell Miniport Driver.
At the time I simply ignored it, thinking the update wasn't relevant to me, but since then I've had a number of BSODs - the latest this afternoon - and in all the cases when Windows has finished doing it's error reporting thing, it comes back with the advice that I need up update the Marvell Yukon Semiconductor driver...and directs me to the same download that I was originally directed to by the Tempro alert. Of course again, it tells me I have to uninstall the previous version before installing it, but as I can't find a previous version of this Miniport driver to uninstall there's nothing I can do about it, so again I ignore it. Everything appears to be working fine (apart from my ongoing dropped internet connection problems with my wireless network and the fact that I can't seem to set up a wired connection (maybe because of this driver problem?), but then sooner or later I get a BSOD again, and it blames the Marvell Yukon driver, and I'm back to square one again. I've had the BSOD now 4 or 5 times over the last month.
Any advice appreciated.

Hello
Have you tried to roll back the OS to earlier time using system restore tool?
Try it and let us know if everything works well again. If yes leave it and be happy without updates.

Ethernet address lost after uninstalling Office 2008

I use AsanteTalk with an Ethernet cable to print to HP printer. Uninstalled Office 2008 and can no longer print. Assumed first it was a Printer/OS X issue and have question in that forum. Have now noticed that there is no longer an Ip address for the built in Ethernet. Unfortunately, uninstalled on 2 laptops, and both can no long print.
How to recapture the IP address would be very helpful in starting to problem solve this issue.

Ok, computer finally found it's ethernet address. Still can't print but that could be another issue.

Yukon: Ethernet and Airport: Ethernet addresses...

Similar Messages

Maybe you are looking for