Remote or Relay

I did RTFM and I'm still not clear. Have an Airport Express being used as a base station. works fine. in-laws live in physically adjacent house. had cat5e strung from their place to mine, but couldn't string directly to closet where switch is.
So, two wired connections coming into switch and one wired connection out to a second Airport Express, thinking I could just hop over to the Base Station (the other Express) a few feet away. Under this scenario, is the 2nd Express acting as a remote or a relay? And not clear how it and the "base station" need to be configured to allow this.
Do I need to put in the Mac address of each on the other one so that 2nd knows who base is and 1st one "allows" 2nd to talk to it?
Thanks (my hair is too short to pull out, but I'm trying)

I'm not sure I understand the physical connections in your scenario.
The terms "relay" and "remote" only apply when using WDS to wirelessly connect the base stations. If you are using Ethernet to connect them, these terms do not apply.
A relay allows you to connect another base station to it. For example:
main<-> relay<-> remote
A remote does not allow other base stations to connect to it.
If they are connected via Ethernet, the base stations do not really talk to each other. Data packets flow between them as the clients need, but the base stations aren't passing control or status information back and forth.
If they are connected via Ethernet, the one not connected to the internet directly should be configured to act as a bridge (not sharing a single IP address).

Similar Messages

Remote and Relay in a WDS

What is the exact difference between remote a relay in a WDS. Also I don't really know what bridge mode is.
I have an airport extreme and want to increase the range with an airport express, what is the best way to do this?
Thanks for any help out there.

bogiegolfer, Welcome to the discussion area!
The best way is to connect the AirPort Express (AX) via Ethernet to one of the LAN ports on the AirPort Extreme base station (AEBS). Then you would configure the AX to act as a bridge (not distributing IP addresses). You would also configure the AX to use the same SSID, wireless encryption type/level/password, and a different channel (as far from the one used by the AEBS as possible).
A "remote" base station does not allow signals to be passed to another base station, only to wireless clients.
A "relay" base station can pass signals along wirelessly to another base station as well as wireless clients.
When a base station is operating in bridge mode it is not acting as a router. It is not handing out IP addresses and it is not doing DHCP.
Be aware that iIf you use WDS your wireless bandwidth will be cut in half.

Remote vs Relay - stability issue?

I am setting up a network with three base stations (one AEBS, two expresses). If all three stations are in range of each other, is there a difference between setting them up as remotes vs relays? Basically, both expresses will be connecting to the AEBS, should I have them connect to each other as well?

WDs reduces the speed of the network, Using a relay makes it even slower.
If all remotes are within range of the main base stations. Set them as remotes for WDS.
Relay is a last ditch effort for extending to a part of the home/office that will not be in range of the main airport.
" Plus, you have to manually do everything for a relay.... UGH"

WDS Remote vs Relay performance

Hi All,
I've an Airport setup that has organically grown over time using WDS. I now have the max of 5 stations with one WDS Main and 4 slaves, One extreme (with attached USB disk) and 3 expresses (One for a USB printer + IMac connection) one for Airtunes and one in the kitchen for extending access.
Over time these 4 remotes have all been configured as Relay stations but in fact all 4 can directly connect to the WDS Main.
The question is is there any performance gain to reconfigure the 4 as Remotes rather than Relays?
Regards,
Shawn

1. Can you daisy-chain four relay stations between the main and a single remote to get a super long distance?
Sure but your bandwidth would suffer greatly. Every WDS link cuts the bandwidth in half. With your proposed configuration, you would have 5 WDS links which would mean that you bandwidth would be
1/(2**5) = 54/32 of your current bandwidth. In a perfect (laboratory) environment, the resulting bandwidth would be:
54/(2**5) = 54/32 = 1.6875 Mbps

Should I add third AE base as remote or relay?

I have an Airport network with two AE bases, one as the main and the second as the remote. I am planning on adding a third one and I have a doubt: should this also be a "remote" or a "relay" when added to the existing bases?
Thank you for your help!

If this third base station is going to be communicating directly with the main base station just as your existing remote base station - then it too should be added as a remote (and not a relay) base station.
A relay base station is used when you need to have a base station that communicates with a main base station as well as a remote base station - useful if you want to get even more range. In such a case, the remote base station would be configured to connect to the relay base station.

Relay or Remote?

Hardware: Airport Extreme (as base station) at 2nd Floor, Airport Express at 1st Floor, Airport Express at 3rd Floor.
How to set up the Airport Express (as remote or relay)?
Am I right to set both Airport Express as relay? It works but not fully utilize the hardware?
Thanks.

it would be kind of you to share the answer with others who have had the same problem

Remote Desktop Connection won't connect to ip address through my airport extreme?

I can't seem to get my RDC to connect through my airport extreme. I know it must be a setting on my airport extreme, but can't figure it out.
When I hardwire the ethernet cable from the modem to the computer it connects fine, and when I set up a hot spot through my iphone, it also works fine every time as well.
I've made sure to add "Windows Remote Desktop" through the port setting in Network settings on the Airport. Can someone please help me??
Many thanks in advance...

Hello Jedid4n. Welcome to the Apple Discussions!
Do you have the AirPort Express Base Station (AX) configured as the remote base station in a WDS with the AirPort Extreme Base Station (AEBS) configured as the main base station? In order for the AX's Ethernet port to be enabled, the AX would have to be set up as either a remote or relay in a WDS.

WDS create vs join net, and WDS relays

1) To configure a WDS remote or relay the docs say you must check create network and (usually anyway) give the same network name that the main base unit is creating. This seems rather odd to me for WDS, so I just wanted to make sure this is correct. (it seems to work so I assume it is but just checking)
2) When configuring a base (an express in this case) as a relay you are asked not only for the mac address of the main unit, but of the remote units that this relay will connect with. How about for the case when the relay will only be passing data to another relay (in addition to local clients). In this case do you give it the mac address of the next relay or the remote at the end (one hop away) from this relay?

1) To configure a WDS remote or relay the docs say you must check create network and (usually anyway) give the same network name that the main base unit is creating. This seems rather odd to me for WDS, so I just wanted to make sure this is correct. (it seems to work so I assume it is but just checking)
All relay/remote base stations in a WDS must have both the same network name and be on the same channel as the main base station.
2) When configuring a base (an express in this case) as a relay you are asked not only for the mac address of the main unit, but of the remote units that this relay will connect with. How about for the case when the relay will only be passing data to another relay (in addition to local clients). In this case do you give it the mac address of the next relay or the remote at the end (one hop away) from this relay?
You only need to provide the Mac address of the next relay station.

Do I need a Roaming Network or a Wireless Distribution System?

Hello - as the title says, I am confused about which type of network I should create.
My specs: Macbook Pro
Windows XP Toshiba Laptop
White UFO-shaped Airport Extreme Base Station
New White Square-shaped Airport Extreme Base Station
1 USB HP Deskjet printer
1 Ministack USB hub/external hard drive
1 LaCie USB external hard drive
I am in the process of finishing my basement and will finally have an "office" to place all of my stuff. I want to be able to hook up the USB printer and USB external hard drives at the same time for wireless availability, so I bought the new AEBS. I am concerned about placing the AEBS in the basement and its impact on wireless signal strength to the upper floors of the house, so I thought I would connect the older UFO-shaped AEBS into the system to extend the wireless range.
I am confused, however, about whether to set up a "roaming network" or a "Wireless Distribution System". I am not sure of the particular benefits of either system given my situation so any help someone could provide would be greatly appreciated.
My house is fairly new, and has a data line system to each room, and I have a cable modem and router in the basement and can share the internet connection to the whole house in this manner. My UFO-shaped AEBS was hooked up to the internet connection via this method with an ethernet cable into the back of the AEBS on the main floor of the house. The USB printer was plugged into the UFO-shaped AEBS. This worked well. Again, now that the new AEBS will be in the basement, I am concerned about signal strength, and would like to use my old AEBS to help out.
I have looked at the Designing Airport Extreme 802.11n Networks pdf document and while it is very detailed about how to set up each of these networks, it does not seem to adequately (in my opinion) address why I would choose one setup over another. For example, should I continue to connect the old AEBS to the ethernet wall connection to get internet connectivity, or should the old AEBS receive its connection wirelessly?
Thanks in advance.

I am confused, however, about whether to set up a "roaming network" or a "Wireless Distribution System".
A roaming network uses Ethernet to connect the base stations. Therefore they all transmit good quality wireless data signals. Physically adjacent base stations should be configured to use channels 3 or more apart to reduce interference with each other. Everything gets full bandwidth.
A WDS network connects the base stations via wireless. Therefore the remote and relay base stations can only transmit data with the same quality as they receive it wirelessly. So if a remote station receives a lousy wireless signal from the main base, all of the clients of that remote station will get a lousy data rate. Also each WDS link cuts the available bandwidth in half.
Since your house is already wired for Ethernet, I would use the "roaming network".

Solution to Airport Extreme Base Station + Airport Express networking probs

I've been investigating this for 3 straight days after inadvertently destabilizing my network. There are tons of posts discussing a variety of issues, all of which seem related. My goal here is to provide links to other relevant posts and explain what I ended up doing to get things to work.
First, the background. You can skip below to SOLUTION if you don't really care... However, I highly recommend you take the time to read everything, as you'll get other useful information in the BACKGROUND section. I'm guessing many of you have similar, related problems so BACKGROUND might help provide context (and solutions) to some things you are seeing...
MY SETUP:
AirPort Extreme Base Station (AEBS) of type b/g (round one, not square one), connects to the cable modem, and creates a WDS network that is then shared across two standard AirPort Express (AEX) units (100megabit, not the gigabit ones). One AEX serves as a relay unit that accepts clients, the other serves as a remote unit that also accepts clients. The intent is to show a single network throughout the house and let users log on to one network and move between networking units without having to switch from network to network.
I have a variety of networked devices throughout the house all running on the same network (2 Mac Pros, a Powerbook G4, a Mac Mini, an Apple TV, a Windows XP laptop, two iPhones, two wifi printers, and a 5-unit Sonos system, plus the AEBS and two AEXs). Yeah, I'm a geek.
The Mac Pros are both running 10.4.11, and the Powerbook is running 10.5.2.
AEBS is running firmware 5.7
AEXs are running firmware 6.3
All Macs were initially accessing configs via the recently released AirPort Utility 5.3.1. More on that later.
BACKGROUND:
I've had this network setup working for about a year now. Recently, I've been having poor network performance problems and came to the conclusion it was a LAN problem (ie. problem with my home network, as opposed to with my ISP). Upon initial investigation, I began by looking at my networking logs (via AirPort Utility 5.3.1). You get to those by selecting the unit in question, choosing "Manual Configuration", the selecting the "Advanced" tab up top with the "Logging and SNMP" sub-tab. Click the "Logs and Statistics" button therein for log details from that unit.
The first thing I noticed was "Administrative access denied to ff80::xxxxxxxxx" messages - a lot of them. I didn't recognize the ff80:: address in question, and so became concerned it was someone outside the network trying to hack one (or all) of the AEBS/AEX units. You can see threads discussing that investigation here:
"Hack or panic?" - http://discussions.apple.com/thread.jspa?threadID=1438486
"Administrative access denied" - http://discussions.apple.com/thread.jspa?threadID=1438865
Long and short of it is that the recent AirPort Utility 5.3.1 release (current as of March 13) seems to have problems (keychain) when attempting to access the AEBS and AEX units. The "Administrative access denied" logs actually refer to the client machine you are using when you try to read the logs. The ff80::xxxxxx address is simply the IPv6 address for the machine you are using; if you turn off IPv6 on your client machine, that address should switch over to begin showing a regular IP address instead (something like 10.0.1.xxx), which makes it easier to associate the IP to the machine. I explain how to deactivate IPv6 on both Tiger (10.4.x) and Leopard (1.5.x) here:
http://discussions.apple.com/thread.jspa?messageID=6814978#6814978
Anyway, in the process of investigating the "Administrative access denied" problem, I began tinkering with my AEX settings. Specifically, I ended up performing a hard factory reset (unplug unit, plug back in while holding down the little button with paper click/pen for ~10-15 seconds until light flashes green 4x then reverts to amber/yellow/orange). I began reconfiguring my entire WDS network using the newly updated AirPort Utility 5.3.1, and that's when the trouble started.
(If you are having problems seeing either your AirPort Extreme Base Station or AirPort Express, read this:)
In short, each time I thought I had properly configured things and then confirmed settings (kicking off a reboot on the AEX unit) the unit would restart with new settings but not properly join the WDS and not show up in the AirPort Utility list of units. More specifically, I would start with a "wiped" AEX and see both the AEBS and the AEX in my AirPort Utility list, but upon confirm/reboot the AEX would disappear and the AEBS would remain. However, that's not 100% correct. It seems that sometimes I would end up with the AEX and NOT the AEBS. Because both the AEX and AEBS were theoretically "hosting" the same network name (remember, WDS shares the network name across units) my auto-login feature for my client computer's wifi seemed to "jump on" whichever unit it first saw hosting the default network name for my house. In other words, it seems what was really happening was that I was ending up with two separate networks in my house, both with the same name but not talking to each other (as opposed to two units sharing the same network name and internet connection). The AEX would continue to blink orange/amber/yellow (whichever color it is to your eyes ) because it could not grab an internet connection -- and if I was on the network through that AEX unit I would not get internet. But if i was connected through the AEBS I would continue to have internet access. As far as my client computer (my Mac Pro) was concerned, I was on the home wifi network even if I was on the AEX rather than the AEBS -- it would show the home wifi network name as the name of the network it had connected to. But when I opened the AirPort Utility 5.3.1 I would see only the AEX (if I was connected through it) or the AEBS (if connected through it) -- a clear indication that the units were not truly sharing the same network.
I tried rebooting and reconfiguring the AEBS and AEX about 50 times (literally). I even tracked down an older version of the AirPort Utility 5.2.1 via this thread (see Tesserax post):
http://discussions.apple.com/thread.jspa?threadID=1067565
One interesting thing re: 5.2.1 is that the "Administrative access denied" errors summarized above disappeared. As explained in a post reference above, the going theory is that this a permissions/keychain problem new and unique to AirPort Utility 5.3.1. However, even though 5.2.1 does have a slightly different interface with different settings, I still couldn't get the WDS to work.
EVENTUALLY, I came across this post:
http://discussions.apple.com/thread.jspa?threadID=1422527
MuaddibOfArrakis walks through setting up a WDS from scratch, and the workflow is different than what is possible with either AirPort Utility 5.3.1 or 5.2.1. He's doing it with the old version of AirPort Admin Utility, which I fortunately saved a copy of many moons ago when I had somewhat-related problems with my WDS (since forgotten). In fact, it's a lot easier. What's nice about this older app is that it literally does the heavy lifting of "connecting" the AEBS and AEX units during the configuration -- it reboots both at the same time as the config is happening, and lets you choose from a list of available units to "add" to your WDS network. In short, it's a FAR SUPERIOR workflow even though some of the GUI isn't as intuitive as the newer AirPort Utilities that were designed to replace it.
SOLUTION:
If still have a copy of the AirPort Admin Utility follow the instructions from MuaddibOfArrakis here:
http://discussions.apple.com/thread.jspa?threadID=1422527
If not, try setting up your WDS network using AirPort Utility (hereafter AU), with these configs (take from my now-working network), as viewed through AirPort Utility 5.3.1.
I. Configure your AEBS.
Select the AEBS from AU, and choose "Manual Setup"
1. Under the AirPort tab up top:
a. Under "Base Station" sub-tab:
i.) assign a name for that specific unit, so you can later identify the specific unit from the list of units -- this is the name that will show up beside the unit in the AU list of configurable units. You can name it something like "kitchen", or "office". I have mine numbered, so XXXXXv1, XXXXXv2 etc where the XXXXX is the name of the shared network and the numbers help me tell the units apart. Just be sure you name each uniquely, and if you have several you might write the name on the unit itself.
ii.) pick a password for logging into that unit. This is different from the network password, its a security check to get in and change the configs on this unit later. Be sure to remember it in your keychain for the sake of simplicity, and write it down somewhere secure.
iii.) if you choose to set time automatically, pick a location that you will use consistently across all your units. I use time.apple.com.
iv.) uncheck "Allow configuration over Ethernet WAN port" unless you want to be able to remotely mess with settings -- which you almost certainly do not need to do.
v.) I left the "Options" button alone - no settings there.
b. Under the "Wireless" sub-tab:
i.) Wireless Mode: "Participate in a WDS network"
ii.) Network Name: this will be the name of your wifi network shared by all units, so be sure to remember what you pick. If you are already connected to this AEBS via wifi while you are making these changes, then you can use the same wifi name you already have set up -- you don't have to change it. Note that if you DO change it, after reboot your will LOSE connection to the network and have to reset your wifi settings on your client machine to match the new network/password in order to be able to access the network.
iii.) pick a Radio Mode. I'm using b/g compatible. You'll want to do the same, unless you are on the new gigabit AEX. I'm pretty sure about this, but not 100% -- others post if I'm wrong.
iv.) choose a Channel. This can be a more complicated procedure, but for now just pick something consistent across all your units. If you get everything working and find that you're having intermittent network problems, you could later try changing your Channel -- it can pick up interference from phones, microwaves, etc and changing it can help.
v.) I have wireless security set to WPA/WPA2 Personal.
vi.) Wireless Password is the password for access to your wifi network (not your unit itself). If you are connecting to your AEBS via wifi while doing this config, then you can use the same password you have already set up. Pick a good one unless you want other folks jumping on your wifi and stealing your bandwidth and/or credit card numbers . Remember it in your keychain and write it down someplace secure, because you'll need it for the other units too. As noted above, note that if you DO change it, after reboot your will LOSE connection to the network and have to reset your wifi settings on your client machine to match the new network/password in order to be able to access the network.
vii.) Click the "Wireless Options" button. I have my multicast rate set to 2mbps, transmit at 100%, timeout at 1 hour, and i have checked the "Create a closed network". This last step keeps your network from advertising itself to the outside world. Users can only find it by explicitly typing the network name into their wifi settings (e.g. AirPort -> Other... then enter Network Name, Security and Password). I leave interference robustness unchecked.
c. Under the "WDS" sub-tab:
i.) the AEBS should have it's WDS Mode set to "WDS main".
ii.) Check the "allow wireless clients" box on the AEBS; this lets you connect client machines to it directly too.
iii.) hit the plus button to add the Remote system (AEX). There are two types of configs for the AEX's - "remote" and "relay". Assuming you have 3 units like me (2 AEX and 1 AEBS) the key question is whether you will place each AEX within direct reach of the AEBS (remotes), or if you will have one AEX in the middle connecting to an AEBS on one side and an AEX on the other -- where the furthest AEX is out of reach from the AEBS (remote) and connects only to the AEX in the middle (relay). I'm using a relay setup. If you are using relay, you can still set up the AEX relay to serve client computers too -- it doesnt have to JUST relay. More on that later. For now, you want to add only AEX units that will talk DIRECTLY to the AEBS. So if you have a setup like mine, just add one (the one in the middle - the relay). If you have two remotes connecting directly to the AEBS, you will add them both here. When you hit the '+' button it will ask for both an ID and description. For description I use the name I'm assigning to each unique unit (as above, "kitchen" or XXXXXv1 or whatever you use). For AirPort ID, use the number listed on the AEX unit itself (not the number for "Ethernet", also on the AEX unit).
d. Under the "Access" sub-tab:
i.) I have it set to "Not Enabled". I'd suggest you start that way too, and you can go change it later if you get everything working correctly.
2. Under the "Internet" tab up top:
a. Under the "Internet Connection" sub-tab:
i.) Connect Using: Ethernet
ii.) Configure IPv4: Using DHCP
iii.) Ethernet WAN Port: Automatic (Default)
iv.) Connection Sharing: Share a public IP address
b. Under the "DHCP" sub-tab:
i.) DHCP Beginning Address: 10.0 . 1 . 2
ii.) DHCP Ending Address: 10.0.1.200
DHCP Lease: 4 hours
c. Under the "NAT" sub-tab:
i.) nothing should be checked;
ii.) nothing under Port Mappings either
3. Under the "Printers and Advanced" tabs up top:
Nothing special needs to be configured there.
THAT'S IT.
=============
I. Configure your AEX(s)
Select the AEX from AU, and choose "Manual Setup"
1. Under the "AirPort" tab up top:
a. Under "Base Station" sub-tab:
i.) pick a unique name for this unit, same logic as for AEBS
ii.) pick a password specific for accessing this unit, same logic as for AEBS
iii.) Set time automatically: be sure to use the same settings used on your AEBS
iv.) Options: no need to set any
b. Under "Wireless" sub-tab:
i.) Wireless Mode: Participate in a WDS network
ii.) Network Name: same name used for AEBS, this is the name of your wifi network
iii.) Channel: same as AEBS
iv.) All settings here (those above, plus Security and Password & in Options button) should be the same as for AEBS settings on this tab
c. Under the "WDS" sub-tab:
...if AEX is "in the middle" (as described above):
i.) WDS Mode: WDS relay
ii.) Allow wireless clients: check (unless you only want to bridge between the edges without letting folks connect on this AEX in the middle)
iii.) WDS Main: set to the AirPort ID (aka MAC address) for the AEBS. You can find it on the bottom of the AEBS, either labeled as such or at the bottom beside the logo of a wireless signal (square logo, with semi-circles mimicing a radio signal).
iv.) WDS Remotes: click the '+' to add any AEX's that will connect to this relay rather than directly to the AEBS. Same deal as above, use the name in the description and use the AirPort ID from the side of the AEX (not the Ethernet ID).
.....if AEX is connecting to a relay ("on the end", as above) or if there is no relay and AEX connects directly to the AEBS:
i.) WDS Model: WDS remote
ii.) Allow wireless clients: checked
iii.) WDS Main: if connected to a relay, use the AirPort ID of the relay AEX. If connected to the AEBS directly, use the AirPort ID of the AEBS
d. Under the "Access" sub-tab:
i.) MAC Address Access Control: Not Enabled (for now, you can change later)
2. Under the "Internet" tab up top:
a. Under the "Internet Connection" sub-tab:
i.) Connect Using: AirPort (WDS) -- should be selected and gray'ed out.
ii.) Configure IPv4: Using DHCP
iii.) Ethernet WAN Port: Automatic (Default)
iv.) Connection Sharing: Off (Bridge Mode)
3. Under the Music, Printers and Advanced tabs up top:
Nothing special needs to be configured there. You can worry about AirTunes settings later...
That should be it. I'd recommend setting up the AEBS first, then the relay (if applicable), then the remotes. Initially, you can bring each unit in the same room with you for configuring. After configured and restarted the AEX should blink then turn solid green. If it turns green you should be good to go.
HOPE THIS HELPS. As noted above, I did not config through AirPort Utility 5.3.1 so I haven't tested this procedure through that app. However, after getting my network to work I went back and transposed all settings into this post to help others. Please provide feedback on whether or not this is working, so we can collectively try to move towards a setup procedure that works for everyone....
Good luck!
Message was edited by: b.byrd

I'm not convinced that the problem lies in Airport Utility. This same thing was happening to me, nearly exactly as you describe it. The thing is that with me, the problems clearly started when I updated the firmware in my Airport Express (n). That's when all the wacky stuff started happening. Sometimes it would show up in AU, sometimes it didn't and even if it didn't, I could still access the internet through it.
But as you said, the problems got really bad when another Express (b/g) was put on the network with it. Even when it did work, the (b/g) would make it impossibly slow.
You know more about this than me, and clearly have more patience if you've restarted the network fifty times. I gave up at about ten.
In any case, your solution is more of a work around and if you're still having that slow connection problem, I'm not sure you've got it. But thanks for your reporting of this. At least I know I'm not crazy.

Sharing internet to wired client using Airport Express

hey
I'm trying to connect a client to my home network through ethernet to a airport express which is wirelessly connected to a Airport extreme base station (802.11n).
This is what i would like my setup to be.
ADSL to modem to Airport extreme wirelessly to Airport Express wired to client (will eventually be a xbox media center).
It says in the apple FAQs that this is possible by configuring the AX as a WDS remote or relay. Since i have no desire to extend the rage on the network, I've made it a WDS remote, but I tried to connect my macbook to it over ethernet to test, which didn't work. Is there any settings that need to be changed it the connection is going to be shared to a wired client?
Thanks
Mike

I have the xact same question as Mcgio. Earlier in this thread there was mention of WDS. From what I have gathered elsewhere, WDS is only necessary if you want to extend your wireless network? That is not what I want to do - I essentilly want to extend my wired network using the AX wirelessly.
I ask about WDS because it does not appear that my Netgear WNR834M router supports WDS (nothing about it in config or the manual).
Will what we are trying to work and what do we need to do?

Adding a Time Capsule to an existing AEBS

Hi, thanks in advance for any advice. I've been reading Apple's "Designing Networks" doc and digging around the forums for days and haven't been able to find all the pieces that add up to a solution for my situation.
I have an existing wireless network using an AEBS (802.11g). My DSL modem and HP LaserJet via Ethernet are both connected.
I just bought a Time Capsule for backup, and I'm trying to add it to this existing network. I would have simply replaced the old AEBS entirely but suddenly I can no longer use the phone jack near the printer. So one of the wireless units has to be in one room, with the DSL modem, and the other wireless unit will end up with the HP printer connected.
I've tried adding the TC to the existing network (not WDS), keeping the AEBS as the main base station connected to the DSL modem; the TC shows up on the network. However, I have been unable to "find" the printer that's connected to the TC LAN ethernet port.
--Should I start from scratch and create a WDS network--is that only way to get the HP printer to show up? (I found one other post about HP ethernet printing in the Graphite/Snow forum; but their solution didn't work for some reason)
--Since I'm using a TC and an older AEBS, should the TC be set as the main base station or doesn't it matter?
--Does the DSL modem have to be connected to the main base station or can it be connected to a remote or relay device (and thus allow my laptop and desktop to connect)?
I hope that's all clear enough, and thanks very much for any advice!

Hello drm1029. Welcome to the Apple Discussions!
I've tried adding the TC to the existing network (not WDS), keeping the AEBS as the main base station connected to the DSL modem; the TC shows up on the network. However, I have been unable to "find" the printer that's connected to the TC LAN ethernet port.
I believe that the AirPorts only support sharing a printer connected to its USB port when the AirPort is configured to "join an existing wireless network" as a wireless client. I don't think printers connected to it LAN port will work this way.
--Should I start from scratch and create a WDS network--is that only way to get the HP printer to show up?
Yes, and again, that would be based on my statement above for the reason.
--Since I'm using a TC and an older AEBS, should the TC be set as the main base station or doesn't it matter?
It really won't matter as the WDS can only operate in the 802.11g radio mode when using "mixed mode" base stations.
--Does the DSL modem have to be connected to the main base station or can it be connected to a remote or relay device (and thus allow my laptop and desktop to connect)?
It must be connected to the main base station in the WDS. When properly configured devices will be able to gain Internet access from any of the base stations in the WDS.

How can I add additional airport expresses to my system that are not being recognized by Airport utility?

I recently purchased time capsule to upgrade my wireless system. I have 3 airport expresses in my network; I was able to reconfigure one, but the other 2 won't reconfigure. They are not recognized by Airport utility after being reset; the time capsule and one reconfigured airport express shows up. I would like to use the other two airport expresses to extend my wireless system. I would appreciate any help and suggestions.

Unfortunately, you will have to use Apple's WDS setting for all of the devices on the network....Time Capsule, new AirPort Express and older AirPort Express devices.
That is going to slow things down tremendously on the network.
WDS only operates at "g" wireless speed, so you lose any "n" speed advantage of your newer devices.
Worse, the bandwidth is cut in half on the entire network for each device that is set up as "relay" or "remote" on the system.
So, the first "remote" (or relay) cuts wireless speed from 54 Mbps down to 27 Mbps. The second cuts everything down to about 14 Mbps and the third drops everything down to about 7 Mpbs. That is much slower than the old wireless "b" systems.
Compare that to "n" speeds of 130 Mbps or up to 300 Mbps (if you are using 5 GHz) and you can easily see that you are losing more than 90% of the speed capability on the network.
Do you even want to consider doing this?

Which bit instructs msgsrv to log deposition of messages in mailboxes?

I hope this is a short question with a one-liner answer:
I want to keep a log of all messages received by the Messaging Server,
including common headers like from, to, subject, size - pretty much
like sendmail logs.
I believe this mode can be toggled on by a bit in LOG_CONNECTION or
something similar, but I didn't yet find what exactly should be set.
At the moment mail.log_current does log connections from localhost and
remote smtp relays, but that's just it - a couple of IP addresses and ports,
i.e.:
12-Mar-2009 06:35:01.32 tcp_local    +            O TCP|127.0.0.1|25|127.0.0.1|49050 SMTP
12-Mar-2009 06:35:01.32 tcp_local    +            C TCP|127.0.0.1|25|127.0.0.1|49050 SMTP
12-Mar-2009 06:35:01.32 tcp_submit   +            O TCP|127.0.0.1|587|127.0.0.1|49051 SMTP
12-Mar-2009 06:35:01.32 tcp_submit   +            C TCP|127.0.0.1|587|127.0.0.1|49051 SMTPAlmost all of the detail I want is there in log lines for messages relayed from
this Messaging Server to a remote relay (they seem to include both messages
initiated by this server's users and messages created via Forward to remote
mailbox), i.e.:
11-Mar-2009 11:24:34.16 tcp_local    +            O TCP|127.0.0.1|25|127.0.0.1|39285 SMTP
11-Mar-2009 11:24:34.23 tcp_intranet tcp_local    EE 14 [email protected] rfc822;[email protected] [email protected] mailsrv domain.ru ([127.0.0.1]) '' TCP|127.0.0.1|25|127.0.0.1|39285
11-Mar-2009 11:24:34.23 tcp_local    +            C TCP|127.0.0.1|25|127.0.0.1|39285 SMTP
# I guess at this point the message was received from webmail
# then queued to a remote server and processed again while it
# was relayed to our internet mailhub
11-Mar-2009 11:24:34.52 tcp_local    -            O TCP|mail.srv.ip.addr|39288|mail.relay.ip.addr|25 SMTP/relay.domain.ru/relay.domain.ru
11-Mar-2009 11:24:34.79 tcp_local                 DE 15 [email protected] rfc822;[email protected] [email protected] mailsrv relay.domain.ru '' dns;relay.domain.ru (TCP|mail.srv.ip.addr|39288|mail.relay.ip.addr|25) (relay.domain.ru ESMTP Sendmail 8.14.3/8.14.3; Wed, 11 Mar 2009 11:24:34 +0300 [MSK]) smtp;250 2.1.5 <[email protected]>... Recipient ok TCP|mail.srv.ip.addr|39288|mail.relay.ip.addr|25
11-Mar-2009 11:24:34.79 tcp_local    -            C TCP|mail.srv.ip.addr|39288|mail.relay.ip.addr|25 SMTP/relay.domain.ru/relay.domain.ru
...I want to have similar entries for messages received by this server both
from remote servers and from this server itself to its users as sole
recipients.
If possible, I'd also like to log the message sizes in order to respond to
questions like "did my big attachment come through?"
# imsimta version
Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 64bit)
libimta.so 6.3-7.04 (built 18:29:00, Sep 26 2008; 64bit)
SunOS sunmail 5.10 Generic_127112-07 i86pc i386 i86pcCurrent option.dat:
! MTA configuration options
! This sets the alias resolution order
!   8 = Use ALIAS_URL0
!   7 = Use ALIAS_URL1
!   6 = Use ALIAS_URL2
!   4 = Use the alias file
ALIAS_MAGIC=4876
ALIAS_URL0=ldap:///$V?*?sub?$R
! REVERSE mapping suggested here: http://forums.sun.com/thread.jspa?messageID=10610989
! Bits described here: http://docs.sun.com/app/docs/doc/819-4429/6n6j50mmo?a=view#fvkaz
!USE_REVERSE_DATABASE=4
USE_REVERSE_DATABASE=13
REVERSE_URL=ldap:///$V?$N?sub?$R
USE_DOMAIN_DATABASE=0
! MISSING_RECIPIENT_POLICY controls how illegal headers that don't
! contain any To:, Cc:, or Bcc: fields are handled for channels that
! do not have their own explicit missingrecipientpolicy keyword set.
! The default of 0 means that the envelope addresses are used to
! construct a valid To: header field. This default behavior tends
! to be especially appropriate for the tcp_local channel.
MISSING_RECIPIENT_POLICY=0
MISSING_RECIPIENT_GROUP_TEXT=Undisclosed recipients
ALIAS_DOMAINS=6
LDAP_SCHEMALEVEL=2
VACATION_TEMPLATE=file:///opt/SUNWmsgsr/messaging64/data/vacation/$3I/$1U/$2U/$U.vac
! Limit message size; default block = 1024b
BLOCK_LIMIT=21000
! http://wikis.sun.com/display/CommSuite/Performance+Tuning+DNS+Realtime+BlockLists+(RBL)+Lookups
! Log if a connection is dropped due to spam RBL
!!!LOG_CONNECTION=7
! http://forums.sun.com/thread.jspa?messageID=10605405
! ...also log more details on timing and password attempts
LOG_CONNECTION=167
LOG_USERNAME=1
! debugging sieve filters - actions logged in the mail.log_current file
LOG_FILTER=1
! --20081205: debugging SMTP dialogs, see http://forums.sun.com/thread.jspa?threadID=5352689
! MM_DEBUG=9Thanks,
//Jim

JimKlimov wrote:
I hope this is a short question with a one-liner answer:
I want to keep a log of all messages received by the Messaging Server,
including common headers like from, to, subject, size - pretty much
like sendmail logs.You can log specific email headers as per the following:
http://msg.wikidoc.info/index.php/Log_email_header
"size" is not an email header.
I believe this mode can be toggled on by a bit in LOG_CONNECTION or
something similar, but I didn't yet find what exactly should be set.
At the moment mail.log_current does log connections from localhost and
remote smtp relays, but that's just it - a couple of IP addresses and ports,
i.e.:
12-Mar-2009 06:35:01.32 tcp_local    +            O TCP|127.0.0.1|25|127.0.0.1|49050 SMTP
12-Mar-2009 06:35:01.32 tcp_local    +            C TCP|127.0.0.1|25|127.0.0.1|49050 SMTP
12-Mar-2009 06:35:01.32 tcp_submit   +            O TCP|127.0.0.1|587|127.0.0.1|49051 SMTP
12-Mar-2009 06:35:01.32 tcp_submit   +            C TCP|127.0.0.1|587|127.0.0.1|49051 SMTP
These entries appear to be msprobe monitoring connections and disconnections -- not email delivery attempts. You will see the same entry if you telnet to port 25, then close the connection.
Almost all of the detail I want is there in log lines for messages relayed from
this Messaging Server to a remote relay (they seem to include both messages
initiated by this server's users and messages created via Forward to remote
mailbox), i.e.:
11-Mar-2009 11:24:34.16 tcp_local    +            O TCP|127.0.0.1|25|127.0.0.1|39285 SMTP
11-Mar-2009 11:24:34.23 tcp_intranet tcp_local    EE 14 [email protected] rfc822;[email protected] [email protected] mailsrv domain.ru ([127.0.0.1]) '' TCP|127.0.0.1|25|127.0.0.1|39285
11-Mar-2009 11:24:34.23 tcp_local    +            C TCP|127.0.0.1|25|127.0.0.1|39285 SMTP
# I guess at this point the message was received from webmail
# then queued to a remote server and processed again while it
# was relayed to our internet mailhub
11-Mar-2009 11:24:34.52 tcp_local    -            O TCP|mail.srv.ip.addr|39288|mail.relay.ip.addr|25 SMTP/relay.domain.ru/relay.domain.ru
11-Mar-2009 11:24:34.79 tcp_local                 DE 15 [email protected] rfc822;[email protected] [email protected] mailsrv relay.domain.ru '' dns;relay.domain.ru (TCP|mail.srv.ip.addr|39288|mail.relay.ip.addr|25) (relay.domain.ru ESMTP Sendmail 8.14.3/8.14.3; Wed, 11 Mar 2009 11:24:34 +0300 [MSK]) smtp;250 2.1.5 <[email protected]>... Recipient ok TCP|mail.srv.ip.addr|39288|mail.relay.ip.addr|25
11-Mar-2009 11:24:34.79 tcp_local    -            C TCP|mail.srv.ip.addr|39288|mail.relay.ip.addr|25 SMTP/relay.domain.ru/relay.domain.ru
...I want to have similar entries for messages received by this server both
from remote servers and from this server itself to its users as sole
recipients.If you have added the "logging" keyword to the defaults line in your imta.cnf file then every email that passes through the MTA, regardless of whether it is destined for remote (tcp_intranet/tcp_local) or internal (ims-ms) will be logged.
If possible, I'd also like to log the message sizes in order to respond to
questions like "did my big attachment come through?"The size is already recorded. It is the argument after the "EE" and "DE". So in your above example the enqueued message was 14KB, and the dequeued message size was 15KB. There is a size difference because the email will increase in size during transit (additional Received: header etc.).
Regards,
Shane.

My itunes are only playing on two of my three aiport express. Why? The green light is on Airport Express. The WiFi is connecte to my commuter. I am hearing music in the other rooms...

My itunes are only playing out of two of my three airport express. Why

Ok, it sounds like what your are trying to do, up-and-above your current configuration, is to both extend your Internet connectivity to additional wireless computers AND stream iTunes to a stereo...correct?
If so, your AirPort Express (AX) will need to operate as either a Remote or Relay Base Station in Apple's Wireless Distribution System (WDS) mode. (ref: http://docs.info.apple.com/article.html?artnum=107454) In order for this to work, you would have to use either another AX or an AirPort Extreme Base Station (AEBS). However, there are some other 3rd-party routers (like Linksys) that may work as well. (ref: http://discussions.apple.com/thread.jspa?threadID=121820)
What is the make/model of your current wireless router...and does this connect directly to your ISP's DSL/Cable modem?

Remote or Relay

Similar Messages

Maybe you are looking for