Serious packet loss creating roaming network over Ethernet.

Comcast Business Gateway modem/router with static addressing provides one address for an externally accessible web/mail server on one of its four RJ45 LAN ports. The second RJ45 LAN port provides a second external address with NAT & DHCP to an internal private 10.1.10.x network connected to a 24-port Netgear gigabit switch. The Netgear is our home's primary switch, with most of the ports going to different jacks thrpughout our house. We have various PCs and Macs, a home server and other similar devices hardwired through the house jacks back to the Netgear receiving DHCP assignments from the Comcast router.
We've had (1) Airport Extreme base station (last generation, not the tall one) connected to the network, also receiving a DHCP IP address from the Comcast box. It's set to bridging mode, cabled from its WAN port by CAT5e to the Netgear switch and offering a Wi-Fi SSID with WPA2 PSK. NAT/DHCP etc is disabled. IPv6 is set to link-local only. No disks attached. Wireless channels set to Automatically.
At this point we have fairly smooth network performance, everything connects immediately (iOS devices, Android devices, utility boxes, computers, etc) and 0% apparent packet loss.
We have some weak Wi-Fi coverage on the far side of the house and I'd like to establish a roaming network, with a new Airport Express (most recent gen) plugged into a wall jack on that side of the house, cabled by Ehternet back to the Netgear, and set up identically. Same SSID and PSK. But when I activate this, I'm finding the network gets anywhere from 88% to 98% packet loss pinging the Comcast router and going outbound. And none of the iOS devices I tried could establish a functional network connection.
I tried replacing the Airport Express with another similar Airport Express, to same effect. I set the Airport Express to create a second SSID and that seemed to work OK, but then I had two distinct networks instead of a roaming network. I also tried disabling DHCP on the Comcast router and enabling it on the Airport Extreme Base Station, but still had the same packet loss. I also tried setting one, the other, and then both Airport boxes to static addressess bypassing the DHCP for their LAN-side connections (although still bridging) and still too much packet loss. No matter what I do, I can't seem to establish a functional Ethernet-connected roaming network with both Airport boxes.
Any ideas?

Thank you for the reply. The Netgear switch I'm using is a GS724T -- it has management features which I'm working through, but all the ports are set to auto-negotiate and the port the Airport Express is on is lit for 100baseT. I didn't see any way to set the MTU in the Airport Utility menus/buttons.
When I join the Airport Express to the network, it sets up the roaming network as intended. But then performance all across the switch goes downhill -- even when pinging from a PC attached to one of the switch ports to the Comcast router I get 90% packet loss or worse, so that nothing seems to get out or in until I disconnect the Airport Express.. It's that dramatic a difference. It doesn't make sense to me that a wireles roaming network across the two Airport boxes should kill performance through the router...

Similar Messages

HT4260 Creating roaming network problem?

HI
I tried to create roaming network at home with help of that article. I just bought new airport extreme for basestation to first floor and new airport express to 2nd floor. I´m planning to connect them with ethernet.
I´m using Mountain Lion on my mac and airport utility 6.1 . I noticed that I don´t have all the option needed to configure roaming network with that new airport utility?
Can some give me working instructions how to create roaming network with those tools?
Thx, Jukka

Sorry - I am a Windows guy and didn't read your post completely - and yes Apple does want you to use this version - but as I understand it, it can be used to set up a basic roaming network - but I don't have Mountain Lion so I can't advise you - however an alternative would be to use someone else's computer with 5.6.1 to set up your network (by the way you could even use a Windows computer) - but I can say from experience that once you set it up, you will be very happy with it - I have an office with 8 Extremes and 2 Expresses on 2 T1 lines and they work great - I would also suggest that you contact Apple and tell them what you think - maybe if enough people complain that it is broken, they will fix it - and again I am sorry about the mix-up - all the different versions and compatibility make it very confusing - many of the gurus feel the same way and suggest some of the things I mention - and you could re-word your question and post it again (this time I won't jump in) and maybe one of the gurus will answer.- anyway good luck - I was only trying to help

Packet Loss When Extending Network?

Hi there, everyone.
I just purchased the Airport Extreme AC after upgrading to 802.11AC devices in the home. On its own, the Extreme AC performs flawlessly - consistent connections, max speed my ISP provides, no-lag, no studdering, no packet loss. I was dissapointed with the range of the device at the far ends of my home, so I set up my previous generation Airport Extreme to extend the network.
It extends the network fine, speeds are about half of what I get at the source, but the issue is that when it is part of the network, I experience packet loss, anywhere from 3% to 8%. I've tested this multiple times, unplugging, testing, replugging, testing. It happens both wirelessly and through ethernet. The issue is no question caused by the previous gen Airport extending the network.
Any help here would be great!
Setup:
- Motorla Surfboard SB6141
- WAN into Airport Extreme AC
- Previous generation Airport Extreme to extend the network, no special settings.
Don't be afraid to use techincal terminology to help me. I can follow and understand the majority of it, as I'm pretty into all of this.

I'm not aware of anything that has changed in the 802.11ac version of the AirPort base stations that would induce the packet loss that you are seeing with an extended network over using an earlier generation. I am assuming, of course, that you are extending another Apple wireless router ... correct?
Typically I would recommend that you would review the placement of the extending base station to be sure that it is in the optimal spot to reproduce the signal with the greatest amount of bandwidth possible. (Ref: This AirPort User Tip)

Creating "roaming" network

I have two 800.11n Airport Extreme base stations (AE) and an Ethernet network. I connect to the internet via a DSL modem. It is physically connected as follows: DSL - WAN AE1 LAN - LAN AE2. I have read the instruction in the manual on page 40-41. My settings on AE1 are (Internet connection PPPoE) and on AE2 (Connect via Ethernet; Configure using DHCP; connection sharing off (bridge mode)). This is not working. What am I doing wrong? Help!

To setup an 802.11n AirPort Extreme Base Station (AEBSn) as a roaming network:
- Network configuration: DSL/Cable Modem or Internet Router > (Ethernet cable) > [WAN] AEBSn#1 [LAN] > (Ethernet cable) > [LAN] AEBSn#2 [LAN] > (Ethernet cable) > [LAN] AEBSn#X
- Setup the AEBSn connected to the Internet to "Share a public IP address."
Internet > Internet Connection > Connection Sharing: Share a public IP address
- Setup the remaining AEBSn(s), as a bridge.
Internet > Internet Connection > Connection Sharing: Off (Bridge Mode)
- For each AEBSn in the roaming network:
-- Connect to the same subnet of the Ethernet network
-- Provide a unique Base Station Name
-- The Network Name should be identical
-- If using security, use the same encryption type (WEP, WPA, etc.) and password.
-- Make sure that the channel is set at least three channels apart from the next AEBSn.

Creating Roaming Network Help

Hi,
i want to install one AirPort Extreme and one AirPort Express to create (a better) or to extend my current wifi.
All i want to know is whether the setup which i created with my incredible paint-skillz is possible or if i have do put it as Apple did it?
So that both the APExt. and APExp. are connect (via LAN) to my dsl-router (which i really cannot replace) and send out a single wifi-signal. So i dont want them to create two seperate wifi-networks; or even better: they extend the routers current wifi (as shown in the 'painting') signal via LAN to other areas of my apartment.
Thank you!

Yes, you can do that, just change your drawing so that only one connection (green line) exists between your modem/ wireless router and the Extreme. If your need to connect both the Extreme and the Express directly to the modem / router is due to placement constraints, then purchase an Ethernet switch. They are available for $20 or so, sometimes less.
Since you are using the drawing in this document, just refer to the drawing below the one you modified. In that one, an Extreme is shown between the modem and a switch (the black box in the middle). What you will do is eliminate that Extreme from the drawing, and connect the yellow line coming from the modem to the blue line going to the switch. That's what Apple means by "incorporating a network switch".
Both the Extreme and the Express will act as bridges. AirPort Utility will automatically examine your network and propose that configuration. Use the exact same passwords, security type (Open/WEP/WPA), and network name (SSID) as your existing wireless network, as explained in the support document.

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".

A strange packet loss in a switching environment.

I have a switching environment with four switches as the diagram showing below. SW1 and SW2 are two Cisco 6509-E switches, SW3 and SW4 are two Cisco 4848E switches, Host 1 and Host 2 are Solaris servers.
The original issue reported was that the SSH session between two servers were not be able to established. Tcpdump result on the servers indicated there was packet loss in the network. Instead of randomly lost some of the packets, only specific packets were lost in the network.
When running ssh server on Host2 and running ssh client on Host1, the Diff-Hellman Key Exchange Reply packet from Host2 to Host1 was lost.
When running ssh server on Host1 and running ssh client on Host2, the Diff-Hellman GEX Init pakcet from Host2 to Host1 was lost.
There are no ACL configured on the switch interfaces.
The packet loss seems targeted for Diff-Hellman related packets, which is really weird. Does any one know why it happened?

I work with the individual reporting this issue and turns out a bad line card on the 6509-E where these 4948e access switches trunk to is the ultimate root cause. I don't believe there were any syslog or other indicators of the failure and it was semi-masked by the fallout being dependent on where the VLAN roots were homed so it wasn't consistent. Ultimately when the VLAN roots were reviewed in-depth, it did make complete sense on the impact being seen on just some access switches and ports and not others.
I believe I've written up all the pertinent facts here or perhaps left a few out and they will be filled in or corrected later.

Packet loss higher than 100% in SQL Reporting

One of our customers is having network problems and packet loss in their network - according to Lync. The network guys claim these values are unrealistic and there've been no dropped packets on their WAN network.
On the other side, I'm looking at a Call Details Report from Lync SQL Reporting and see this in the gateway leg information:
Audio Stream (Caller -> Callee)
Codec:
PCMU
Sample rate:
8000
Packet utilization:
285
Avg. packet loss rate:
51.20%
Max. packet loss rate:
79.52%
Avg. jitter:
0 ms
Max. jitter:
0 ms
Burst duration:
5980 ms
Burst gap duration:
1890 ms
Burst density:
100.00%
Burst gap density:
0.00%
Avg. concealed samples ratio:
60.00%
Avg. stretched samples ratio:
0.00%
Avg. compressed samples ratio:
0.00%
Avg. network MOS:
1.50
Min. network MOS:
1.50
Avg. network MOS degradation:
2.21
Max. network MOS degradation:
2.21
NMOS degradation (jitter):
0.00%
NMOS degradation (packet loss):
100.00%
Audio Stream (Callee -> Caller)
Codec:
PCMU
Sample rate:
8000
Audio FEC:
False
Bandwidth estimates:
Packet utilization:
146
Avg. packet loss rate:
900.00%
Max. packet loss rate:
900.00%
Avg. jitter:
1540 ms
Max. jitter:
4406 ms
Avg. round trip:
178 ms
Max. round trip:
179 ms
From this I feel there are things to troubleshoot. :-) but how come that Lync reports a 900% packet loss?
I thought that a 100% packet loss was everything... can someone tell me what exactly are these 100+ percentages?
Thanks in advance.

latest patch level :) are you not seeing these values in your Server Performance reports?
The other thing that bugs me is when you have 1 call for 1 second with "900% loss", that would average down to get red values in the summary columns for the other 100 calls as well, as the calls are not counted for seconds, but just piece by piece.
So 8 perfect calls to this one above would average "100% packet loss per call" in the summary, which is just unusable...

Homefusion packet loss

Finally been able to get homefusion working reliably, after many moons of hassle but thats not the issue
While playing online games recently, I would start getting unreal amounts of latency, so I started doing some digging, and it seems like I'm having an issue with packet loss on the network.
3 48ms 4/ 100 = 4% 4/ 100 = 4% 58.sub-69-83-63.myvzw.com [69.83.63.58]
0/ 100 = 0% |
10 58ms 2/ 100 = 2% 2/ 100 = 2% ae-8-8.ebr2.Atlanta2.Level3.net [4.69.140.230]
0/ 100 = 0% |
Also having some large ping spikes as well
49 ms 50 ms 300 ms ae-11-11.car1.Nashville1.Level3.net [4.69.140.226]
Anyone have any ideas as to what is going on? Any ideas on how to fix this issue? It's quickly becoming a problem for me

Sorry to hear about the troubles with your connection. If you are still experiencing the packet los, please send me a private message.
Anthony_VZ
**If someones post has helped you, please acknowledge their assistance by clicking the red thumbs up button to give them Kudos. If you are the original poster and any response gave you your answer, please mark the post that had the answer as the solution**
Notice: Content posted by Verizon employees is meant to be informational and does not supersede or change the Verizon Forums User Guidelines or Terms or Service, or your Customer Agreement Terms and Conditions or plan

NIC teaming creates packet loss (Windows 2008 R2)?

I'm experiencing some packet loss to all of our VMs that we didn't have before we made some changes to our Hyper-V implementation (Windows 2008 R2). Most of the VMs also run 2008 R2 - with 3 that run Server 2003.
The host server is a Dell R610 with three 4 port NICS - two Intel quad port gigabit and a quad port Broadcom.
We us the individual ports of the Broadcom for host management and live migration - no problems here. We use the Intel cards for both iSCSI and VM networks. Calling the two intel cards “A” and “B”, and the ports P1-4 we've used AP1, AP2, BP1, BP2 (ports
1 & 2 of both Intel NICs) for iSCSI connections, and we've created a NIC Team with AP3, AP4, BP3, and BP4 (ports 3 and 4 of both Intel NICs). The team type is "Virtual Machine Load Balancing". We then created a Hyper-V switch based on this team
for use with all of the VMs created on the host. (as a side note: prior to implementing the NIC team, we just had 4 Hyper-V switches, one associated with each of these 4 ports.)
The 4 ports of the NIC team are connected to two different Cisco SG200 switches - AP3 and BP3 are connected to switch1, and AP4 and BP4 are connected to switch2 (in an attempt to maximize redundancy). The two Cisco SG200s are simply connected to the rest
of our network - each to a different switch within the subnet. There is minimal configuration done to the SG200s (for example NO
link aggregation); spanning tree is enable however.
My question is: can the network cables be connected to different switches (as they currently are) and if so is there some configuration piece (either on the switch or within Windows) that I'm missing?
What are the options here if this configuration is incorrect? The packet loss is in the range of 0.1%, but we've had odd spikes where a VM was essentially unavailable for a brief period (a few minutes) then returned to "normal" (0,1% loss).
Pinging a device (like the SG200 itself) or another physical server (for example our domain controller or the hyper-v host itself) results in essentially 0 loss; maybe one or two packets during the course of a 12 hour ping (this was the “normal” ping
response to VMs before we created the NIC team, so I’m quite sure this has something to do with it).
Thanks in advance!

I believe when utilizing the Virtual Machine Load Balancing the ports must be connected to the same switch, stack, or chassis as the arp for the MAC could move. I believe, although I could be wrong, that the outages you see is when the machine "moves"
between ports and the arp being updated between the two switches.
I believe you are looking for switch fault tolerance teaming which will allow for the failure of adapter, cabling, or switch which will achieve your goal of maximum redundancy. This is achieved via spanning tree on the switches, which you indicated
is already configured.

TMS reporting - Network Packet Loss

Hi everyone,
I am trying to see packet loss reports in TMS but there is no info there.
My network is : VCS 7.0.2 with movi, c20 and ex60 registered (SIP) to it and a TMS 13.1.2.
The vcs is a starter pack and the TMS is the demo version. I first registered the endpoint to the vcs and then added the TMS to the network. I the added the endpoints and vcs to TMS. In TMS I see the endpoints and info about them, but unfortunatelly no info in the packet loss report. I made a call between movi and c20 with packet loss but no info was shown in the report.
I am very new to TMS and I wonder if there is something I should do in order to make the endpoints send packet loss info to TMS.
I sshed to the endpoints and I can see the info about packet loss and jitter through the api.
The network described above is my test network on which I can do prety much everything on. I also have the same problem (this time with EX60 endpoints, VCS Control and TMS) on a customer network and on that network I really need to get this working.
Any help would be much appreciated. Form what I read the endpoints should sent this info through HTTP to TMS. Am I right?
Thank you for your help.

Hi Magnus,
Thank you for your reply. I checked the logs and I get some info over there. I have attached the log.
Do you know what doc should I check to see if Ex60 is supported?
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/8/2012 3:58:51 AM
Disconnected
Call id: 3 Port id: 1;
Remote Number: sip:[email protected] Remote Name: 1853;
Direction: Outgoing CallProtocol: SIP;
Bandwidth: 6000 kbps Encryption Mode: Aes128;
Duration: 00:13:33; Cause Code: Normal call clearing
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/8/2012 3:45:19 AM
Connected
Call id: 3 Port id: 1;
Remote Number: sip:[email protected] Remote Name: ;
Direction: Outgoing CallProtocol: SIP;
Bandwidth: 6000 kbps Encryption Mode: Off;
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/7/2012 6:43:15 AM
Disconnected
Call id: 2 Port id: 1;
Remote Number: sip:[email protected] Remote Name: 1853;
Direction: Outgoing CallProtocol: SIP;
Bandwidth: 6000 kbps Encryption Mode: Aes128;
Duration: 00:14:57; Cause Code: CauseCode_Unknown
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/7/2012 6:28:19 AM
Connected
Call id: 2 Port id: 1;
Remote Number: sip:[email protected] Remote Name: ;
Direction: Outgoing CallProtocol: SIP;
Bandwidth: 6000 kbps Encryption Mode: Off;
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/7/2012 6:28:07 AM
Got Response
Got Network Response - TMS will now monitor   the system.;
System: [email protected] -   10.1.x.y ;
System Status: No response;
System Type: TANDBERG C-series   Endpoint;
Software: s52000 TC5.1.0.280662;
Hardware: F1AN19D00469 - ;
System Contact;
No Contact ();
Mobile: ;
Office: ;
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/7/2012 6:28:07 AM
Got Response
Got Network Response - TMS will now monitor   the system.;
System: [email protected] -   10.1.x.y ;
System Status: Idle;
System Type: TANDBERG C-series   Endpoint;
Software: s52000 TC5.1.0.280662;
Hardware: F1AN19D00469 - ;
System Contact;
No Contact ();
Mobile: ;
Office: ;
10.1.x.y
TANDBERG Codec C20
Other type
Endpoint
5/7/2012 6:28:06 AM
Got Response
Got Network Response - TMS will now monitor   the system.;
System: [email protected] -   10.1.x.y ;
System Status: No response;
System Type: TANDBERG C-series   Endpoint;
Software: s52000 TC5.1.0.280662;
Hardware: F1AN19D00469 - ;
System Contact;
No Contact ();
Mobile: ;
Office: ;

Networking via cross-over ethernet

I have two PCs both running Windows 7 Pro 64 bit. Both are fully updated.
One connects via wireless adapter to a router at the other end of my house (not practical to connect it via ethernet).
The router gets my ISP signal and is my Internet access point.
The other PC is in the same room but has no wireless adapter (I know I could just get one, but that is not what I want to do here).
The two PCs are close enough that I can easily connect them directly to each other with an ethernet cable.
I tried a regular cable but connecting gave me problems so I used a cross-over cable to connect them.
My original intent was to be able file access & sharing of the (let's call it guest PC) and the one with the wireless internet access (let's call it the host).
When I rebooted both I was able to open the explorer and see the host computer from the guest and vice versa on the Network list. I allowed file sharing and everything looked great.
I mapped the user and file locations from the guest that I wanted in the host PC as a network drive on the host.
Since I wasn't regularly using the guest, it went to sleep and I could not re-establish the mapped network drives nor the shared file connection. That was a pain, so I set out on another option.
I set up a Home network in the guest PC that is now accessing the Internet.
OK, I'm not exactly sure how I did that. I kept creating unidentified public networks and finally was able to create a private one on the guest that connects (I'm not sure if it was by sharing or merging) to the Internet. It has to be somehow shared
because (as I mentioned above) the guest has no wireless adapter and no other way to get Internet except by sharing the host PC's wireless access.
Well, the drives that I had mapped before setting up the Internet sharing suddenly work again fine.
But, AND HERE'S MY CURRENT PROBLEM, I cannot see the guest computer from the host in the explorer (or the other way either).
I tried then to just join the host computer's HomeGroup, but I can't. I can't join a HomeGroup created on the guest either.
I'd like to be able to view and share my files across both the host and guest.
I'd even like to be able to remote access the guest desktop from the host. (I know I can do that with LogMeIn, TeamViewer, VNC, and other programs).
I also know I can share files using Hamachi (but it does not give remote desktop control so I can't run programs).
Can anybody help me on this? Or is it impossible to use a cross-over ethernet connection between two PCs and have them both share files and be visible either browsing on the Network or in a HomeGroup?

Thanks, I have never solved this. I did check your links. At one point at least I was able to share my wireless connection, but I don't know how I did it and now I have even lost that trying to fix the fact that I could not actually network the two PCs.
Again, both running Windows 7. One has wireless adapter & connects to Internet through router - no problem there.
Second PC has no wireless adapter. I wanted to use cross over ethernet cable to connect it directly to the one that has Internet access. The idea was twofold: first, setting up a peer to peer local network with both PCs on it so I could directly open &
share files from one to the other. I fiddled so much that now I'm getting a message that the PC without the WiFi adapter does not have a valid IP address.
My second (and actually more important goal) was to allow the PC without the WiFi adapter to share the other PC's Internet connection. I did something with the merging option that made it work but I don't know for the life of me what it was. I kept having
trouble with the new network defaulting to Public and I could not change it to Private. That gave me all kinds of problems trying to create and join a HomeGroup. I could create them in each PC but neither could join the other's created HomeGroup.
Now I'm back to square one, or even worse since I can't get either of my goals solved. If it's impossible to network them P2P I'd at least like to share the Internet connection using the cross-over cable as I had it for a few days.

Time Capsule/Airport Express/Ethernet - Setting up Roaming Network?

Hi,
I am trying to setup a network in my house to extend the wifi. Currently the wifi signal is not strong enough to work in the a portion of the upstairs (bonus room). I want to extend the network and have it be as fast as possible.
Here's what I have going on:
There are 2 rooms hard wired with cat 5. The office and the upstairs bonus room. I have a comcast modem in the basement where the cat 5 wires all run to. The comcast modem has three available ethernet out ports. I have one of them running to my office where my time capsule is located which is where I currently have my wifi signal coming from. I have another ethernet plugged into another port on the comcast modem and running to the bonus room. I purchased a Airport express and was hoping to just plug it into the ethernet in the bonus room to extend my extisting network using the ethernet (via a roaming network?) but I can't get it to work.
A couple of questions:
Is this the best way to extend my network so it will be as fast as possible? How do I get it to work? I don't want to have to move the time capsule downstairs to make this work.
I am new to this type of networking so please forgive my ignorance.
Thanks in advance for the help.

Get the IP of the TC and the Express plugged into the Comcast router.. we are assuming router.
You simply click on the airport utility and see what IP it is picking up.
eg
This is bridged and has picked up the address from the main router.. so shows both LAN and IP address as the same.
Actually post a screenshot makes this ever so much easier.
If you are not getting this.. then click edit and go to the tabs..
1. Internet. Should be DHCP
2. Network. Should be Off (bridge mode)
3. Wireless. Should be Create a wireless network.
Post me up the details and "we" can work it out.
The basic Apple doco for roaming is here.
http://support.apple.com/kb/ht4260
As with so much documentation it is out of date against the newest version of the airport utility.. so they are a little behind.

Extending Wireless Network and Bridging Over Ethernet

Have a TimeCapsule and Airport Basestation at home. Both are currently connected over wireless using the "Extend Wireless Network" feature.
On each of the devices have several laptops, mac minis etc. connected over Ethernet (since wireless insufficient for our high speed data transfers etc.)... Trouble we are having is the speed/connection between both the TC and the AP, so considering to connect them both over Ethernet to improve.
Question is once they are connected over Ethernet, what happens to the "Extend Wireless Network", how does the TC and AP know to either use the wireless or the Ethernet to connect with each other? Does one take precedence over the other?
We want to keep them both on Ethernet and Wireless bridge ideally, so that at opposite ends the wireless network is extended for our iPhones and iPads and all devices connected on Ethernet benefit the speed boost over Ethernet, but just not sure how it will behave, and not sure how to test this scenario....
So asking here instead
Thanks!

It sounds like you might want to configure your base stations into a "roaming network".

Network issues. Packet loss when spray is used!!!!!!!!!!!!!!!

Hi, I am not in a position to figure out, is it an issue with my server or my network. I run spray and find packet loss...what should I suspect?
In one way, the packet loss is 0%, while the other way, there is 90% loss. Both machines are located in two different buildings.
here is the output.
bash-2.03# spray 172.16.59.7
sending 1162 packets of length 86 to 172.16.59.7 ...
no packets dropped by 172.16.59.7
34031 packets/sec, 2926694 bytes/sec
bash-2.03# spray 172.16.59.7
sending 1162 packets of length 86 to 172.16.59.7 ...
no packets dropped by 172.16.59.7
33512 packets/sec, 2882044 bytes/sec
bash-2.03# spray 172.16.59.238
sending 1162 packets of length 86 to 172.16.59.238 ...
205 packets (17.642%) dropped by 172.16.59.238
28146 packets/sec, 2420575 bytes/sec
bash-2.05$ spray giove
sending 1162 packets of length 86 to giove ...
1052 packets (90.534%) dropped by giove
7 packets/sec, 629 bytes/sec
bash-2.05$ spray giove
sending 1162 packets of length 86 to giove ...
1052 packets (90.534%) dropped by giove
7 packets/sec, 629 bytes/sec
bash-2.05$ spray giove
sending 1162 packets of length 86 to giove ...
1052 packets (90.534%) dropped by giove
7 packets/sec, 629 bytes/sec
bash-2.05$ spray giove
sending 1162 packets of length 86 to giove ...
1052 packets (90.534%) dropped by giove
7 packets/sec, 630 bytes/sec
bash-2.05$ spray giove
sending 1162 packets of length 86 to giove ...
1052 packets (90.534%) dropped by giove
7 packets/sec, 630 bytes/sec
bash-2.05$ spray giove
sending 1162 packets of length 86 to giove ...
1052 packets (90.534%) dropped by giove
7 packets/sec, 630 bytes/sec

http://docs.sun.com/app/docs/doc/816-5166/6mbb1kqhl?a=view
spray is not useful as a networking benchmark, as it uses unreliable connectionless transports, UDP for example. spray can report a large number of packets dropped when the drops were caused by spray sending packets faster than they can be buffered locally, that is, before the packets get to the network medium.

Serious packet loss creating roaming network over Ethernet.

Similar Messages

Maybe you are looking for