Wireless Repeaters

Hello, I have a few coverage deadspots that I want to elimate with my WRV200.  I see in the configuration that I can use a second WRV200 as a wireless signal repeater.  Does this meanthe second box just needs to be within wireless range of the primary box (with the corrcet configuration) and it will simply pass the traffic on, or does it in fact need any wired cable connections?
Thanks
Rich

Where exactly do you see in the configuration that you can use a second WRV200 as repeater? I don't know the WRV200 but the manual has only the part with the WDS and there it says in the manual:
WDS allows a wireless signal to be repeated by a repeater. This mode allows a wireless client to connect to the
Router through a repeater, such as WAP54G, WAP54GP, WAP54GPE, when operating in the Repeater Mode. This
mode allows you to extend the coverage of the Router by using up to three repeaters. Select Auto to enable the
remote access point when operating in Repeater Mode or select Manual and enter the MAC address of the
repeater.
This means you can use a WAP as repeater but not a WRV. Generally, as far as I know, all Linksys wireless routers do not work as wireless repeater or wireless bridge with standard Linksys firmware. The routers require a wired connection. Only the access points like the WAPs do repeating and bridging.
You are correct about how a repeater works. You set it up somewhere and it picks up a wireless signal and retransmits it. Remember, however, that it is in the nature of a repeater to severely reduce the possible throughput in a wireless network. For example any traffic send out from the router to the repeater is send back from the repeater to the router. This additional traffic will cause additional transmission collisions on the wireless. Thus, the overall speed in your whole wireless network may go down to as low as half of the speed you are able to establish between the router and the repeater.
Due to this, I always recommend to install a wired connection whenever it is possible. With a wired connection you are also able to use a second WRV200 with standard Linksys firmware (in case you already have one) to extend the wireless coverage with much better speeds. But it requires a special setup on the second WRV, basically connecting the second through a LAN port to the LAN. The normal "dedicated" device for a wireless network extensions, however, would be an access point like the Linksys WAPs...

Similar Messages

  • Recommendations for good wireless repeaters

    I have a Linksys WRT610N router.  It works fine.  However, I have it at one end of my house, because that's where the phone line comes into the house and I've got DSL.  Therefore, the wireless signal gets weak towards the other end of the house, especially for 802.11g.  Today I learned that there's a thing called wireless repeaters.  This sounds like a great idea, and may help me with being able to get the G band to the rest of the house.  What makes/models of wireless repeaters would work best with my WRT610N router, especially for 802.11g?

    Check this article. HTH

  • Wireless Repeaters Extender issues!

    I have recently discovered that I can stream audio from my WRT54G V2 via a wireless extender.
    I can not play internet radio, or stram Rhapsody via the extender.
    The extender will not stream audio.
    This is actually quite normal behavior of a Range Extender. Range Extenders work off of the idea of pulling a signal from the Base Station and then repeating the signal frequently, this generally causes rebuffering issues with most wireless devices within a network.
    I belive I need a wireless extender that does not repeat the signal, more of a wireless access point.
    How do I set this up.  What do I need?

    It actually should okay through the extender but since you're experiencing some buffering with the connection then I believe that this has something to do with the signal from the router. The extender is an N-standard while the router is just on G. So I suggest you buy a new router with MIMO technology. For the meantime with the router, just make sure the firmware is up to date then try again.

  • How do I set up my AirPort Time Capsule to connect wirelessly to my VisionNet modem?

        I'm trying to get my AirPort Time Capsule to work with my landline phone DSL company. They supply all customers with a VisionNet modem/router. My problem is getting the Capsule to work wirelessly with the VisionNet modem. I want to put the Capsule on the other end of the house so I have internet connectivity all around my house. I have no idea how to do this. Is there anyone out there who is tech savvy enough to help me? Your help and response will be truly appreciated.

    It will not work.. Apple routers cannot wirelessly extend other brands..
    You must plug the TC into the modem router with ethernet.. and put it in bridge mode. You can then get another apple router, like an express or extreme (or even another TC) to extend its wireless.
    This is fairly typical btw if you are thinking apple is being exclusivist.. well they are but the fact is wireless repeater (WDS is normal term), is not a standard and so every company does what is right in their own eyes.
    WDS is not cross platform.. you always need to stick to the same brands.. or use universal wireless repeaters. But these are not recommended as they are generally unreliable and have other impacts on the network.
    Run ethernet or use EOP (homeplug) adapters to connect the TC to the VisionNet modem.

  • Wireless Roaming with more than one access point

    Dear All,
    I am trying to set up roaming access points around my home. My main router is the Hub 3 and what I am doing is setting the SSID and channel i want on the hub 3 then setting the same SSID on the additional access point (WNR1000v3) and disabling DHCP on the additional access point and setting a static IP and a different channel to the one  on the hub 3. 
    The problem I am getting is that my devices (android smartphone and tablet) will either only connect to one of the access points when I am near it and then when I go to the area that the hub 3 is in it drops the connection.
    I want to know why this is happening because at another house where I work I have additional access points broadcasting the same SSID as the home hub 2! which works. 
    Please could someone tell me why this is happening and what I can do to prevent it.
    Many Thanks,
    Dominic
    Solved!
    Go to Solution.

    dombullion wrote:
    Thanks for the reply Keith, 
    But why does it not allow for Roaming?
    There is an internal Ethernet switch which routes the Ethernet frames to a specific device MAC address, via the wireless module, or the LAN ports, but not both.
    Once a device MAC address appears on the LAN side, all frames are routed to that interface, until the physical interface is disconnected.
    That prevents the same MAC address connecting to the wireless interface.
    Universal wireless repeaters do not have that problem, as all connections take place on the wireless interface.
    There are some useful help pages here, for BT Broadband customers only, on my personal website.
    BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

  • Wireless printing with Brother - Time capsule

    I try to get my printer Brother DCP-J715W up and running, but I can't connect to the router, Time Capsule.
    Any suggestions? Is it a problem with WPS or AOSS, don't know exactly what it is, but that's what the error report says ...
    Tx, Aldert

    Using extend a wireless network on a TC wirelessly is a major no no and I quote from the web
    Wi-Fi extenders (sometimes called wireless repeaters) seem like the obvious choice for helping a wireless router cover an entire house with Internet access. Essentially, they pick up a wireless signal just like your tablet or laptop, then rebroadcast that signal, giving you a second access point to connect to. But there’s a big problem with that which kind of cripples the functionality of extenders. Networking expert Tim Higgins wrote this about extenders on SmallNetBuilder in 2011:
    “No matter what they are called or technology they use, repeaters start out with a minimum 50% throughput loss. The reason is that a repeater must receive, then retransmit each packet using the same radio on the same channel and with the same SSID. If the repeater is very efficient, then your loss will be close to 50%. But if it’s not, throughput loss can be higher.”
    This is why I think you have to restart with cabling to the TCs

  • More than 1 SSID when using repeaters.

    I have a E2500 and 2 repeaters to get full home coverage. All of the outputs have the same SSID and I get confused. Can I add a number behind the SSID on each so I will know which one to connect to?

    Hi nodsirrah. Yes, you may add a number to the SSID's that were configured on each repeater's setup page to be able to differentiate it from the main one.  By the way, are they also Linksys wireless repeaters? If so, this link may help, http://kb.linksys.com/Linksys/ukp.aspx?vw=1&docid=206954591ff54e36884bb4636fcfd3d9_Manually_configur...
    Hope that helps.

  • Time Capsule wireless connection to DGN1000

    Hi there, what I'd like to do is... Connect my Time Capsule (upstairs) to my Netgear DGN1000 router (downstairs) wirelessly! Therefore increasing my wireless range, and allowing me ethernet ports upstairs, instead of sharing my Macs airport connection via ethernet.
    Thanks, Adam

    It's also quite a long distance for an ethernet cable
    the ethernet cable will work fine for 100M.. and I doubt it is that far.
    In the end the actual cost to install ethernet between two levels of the house can be well repaid with reliable connections.. and fast. Everything else.. whether wireless bridging or EoP are simply trying to do what ethernet does but less well.. less fast.. less reliably.
    After trying wireless repeaters and bridges doing video streaming.. for ages.. and getting it to work really well.. until the gremlins get in.. ie it runs perfectly for 49 minutes of a 55min show and will then begin to glitch.. It was like clockwork.. if the show was a 2 hour film it would not glitch until 1hour 50min. Running ethernet fixed it permanently.. then you can just plug in wireless AP at those points you need wireless.
    The hassle for people who rent though is not being able to do this so EOP is the best alternative.. and work well generally but still depends on the standard of wiring.. and type of breakers used in fuse box if they are on different circuits in the house. As Bob says.. make sure the store allows returns if they don't work well or at all.

  • [SOLVED] Puzzled: Web site visible on network but not outside network

    Edit: Ok, nevermind . . . somehow the problem has resolved itself. Perhaps my ISP was having a bad hair day or something.
    I'm puzzled by this small problem I'm having. It is NOT a critical problem or anything, just something I'd like to solve.
    I've installed the LAMP packages, set up a small MySQL database and made a very simple web interface for it. The web pages open fine on my main computer and all the other computers on our network, but it is not visible outside our network.
    I am behind a router and I have forwarded port 80 to my local IP. I've set httpd: ALL, http: ALL and (finally) ALL: ALL: ACCEPT in /etc/hosts.
    I got to thinking maybe my ISP (RoadRunner) is blocking port 80 requests to my home, so I changed the port to 9292 and forwarded that to my local IP. Still not visible from the outside.
    I've tinkered with the /etc/httpd/conf/httpd.conf file (pasted in below) but still there is no outside connectivity, changing the listen settings and the server name settings. I can still access it fine from this side of the router. I've restarted the httpd service many times.
    I've done all I can think to do to solve the issue. it is likely I am overlooking something very basic. Any help or ideas are appreciated. Below is my httpd.conf.
    # This is the main Apache HTTP server configuration file. It contains the
    # configuration directives that give the server its instructions.
    # See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
    # In particular, see
    # <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
    # for a discussion of each configuration directive.
    # Do NOT simply read the instructions in here without understanding
    # what they do. They're here only as hints or reminders. If you are unsure
    # consult the online docs. You have been warned.
    # Configuration and logfile names: If the filenames you specify for many
    # of the server's control files begin with "/" (or "drive:/" for Win32), the
    # server will use that explicit path. If the filenames do *not* begin
    # with "/", the value of ServerRoot is prepended -- so "/var/log/httpd/foo_log"
    # with ServerRoot set to "/etc/httpd" will be interpreted by the
    # server as "/etc/httpd//var/log/httpd/foo_log".
    # ServerRoot: The top of the directory tree under which the server's
    # configuration, error, and log files are kept.
    # Do not add a slash at the end of the directory path. If you point
    # ServerRoot at a non-local disk, be sure to point the LockFile directive
    # at a local disk. If you wish to share the same ServerRoot for multiple
    # httpd daemons, you will need to change at least LockFile and PidFile.
    ServerRoot "/etc/httpd"
    # Listen: Allows you to bind Apache to specific IP addresses and/or
    # ports, instead of the default. See also the <VirtualHost>
    # directive.
    # Change this to Listen on specific IP addresses as shown below to
    # prevent Apache from glomming onto all bound IP addresses.
    #Listen 12.34.56.78:80
    Listen 192.168.1.100:9292
    #Listen *:9292
    # Dynamic Shared Object (DSO) Support
    # To be able to use the functionality of a module which was built as a DSO you
    # have to place corresponding `LoadModule' lines at this location so the
    # directives contained in it are actually available _before_ they are used.
    # Statically compiled modules (those listed by `httpd -l') do not need
    # to be loaded here.
    # Example:
    # LoadModule foo_module modules/mod_foo.so
    LoadModule authn_file_module modules/mod_authn_file.so
    LoadModule authn_dbm_module modules/mod_authn_dbm.so
    LoadModule authn_anon_module modules/mod_authn_anon.so
    LoadModule authn_dbd_module modules/mod_authn_dbd.so
    LoadModule authn_default_module modules/mod_authn_default.so
    LoadModule authz_host_module modules/mod_authz_host.so
    LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
    LoadModule authz_user_module modules/mod_authz_user.so
    LoadModule authz_dbm_module modules/mod_authz_dbm.so
    LoadModule authz_owner_module modules/mod_authz_owner.so
    LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
    LoadModule authz_default_module modules/mod_authz_default.so
    LoadModule auth_basic_module modules/mod_auth_basic.so
    LoadModule auth_digest_module modules/mod_auth_digest.so
    LoadModule file_cache_module modules/mod_file_cache.so
    LoadModule cache_module modules/mod_cache.so
    LoadModule disk_cache_module modules/mod_disk_cache.so
    LoadModule mem_cache_module modules/mod_mem_cache.so
    LoadModule dbd_module modules/mod_dbd.so
    LoadModule dumpio_module modules/mod_dumpio.so
    LoadModule ext_filter_module modules/mod_ext_filter.so
    LoadModule include_module modules/mod_include.so
    LoadModule filter_module modules/mod_filter.so
    LoadModule substitute_module modules/mod_substitute.so
    LoadModule deflate_module modules/mod_deflate.so
    LoadModule ldap_module modules/mod_ldap.so
    LoadModule log_config_module modules/mod_log_config.so
    LoadModule log_forensic_module modules/mod_log_forensic.so
    LoadModule logio_module modules/mod_logio.so
    LoadModule env_module modules/mod_env.so
    LoadModule mime_magic_module modules/mod_mime_magic.so
    LoadModule cern_meta_module modules/mod_cern_meta.so
    LoadModule expires_module modules/mod_expires.so
    LoadModule headers_module modules/mod_headers.so
    LoadModule ident_module modules/mod_ident.so
    LoadModule usertrack_module modules/mod_usertrack.so
    #LoadModule unique_id_module modules/mod_unique_id.so
    LoadModule setenvif_module modules/mod_setenvif.so
    LoadModule version_module modules/mod_version.so
    LoadModule proxy_module modules/mod_proxy.so
    LoadModule proxy_connect_module modules/mod_proxy_connect.so
    LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
    LoadModule proxy_http_module modules/mod_proxy_http.so
    LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
    LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
    LoadModule ssl_module modules/mod_ssl.so
    LoadModule mime_module modules/mod_mime.so
    LoadModule dav_module modules/mod_dav.so
    LoadModule status_module modules/mod_status.so
    LoadModule autoindex_module modules/mod_autoindex.so
    LoadModule asis_module modules/mod_asis.so
    LoadModule info_module modules/mod_info.so
    LoadModule suexec_module modules/mod_suexec.so
    LoadModule cgi_module modules/mod_cgi.so
    LoadModule cgid_module modules/mod_cgid.so
    LoadModule dav_fs_module modules/mod_dav_fs.so
    LoadModule vhost_alias_module modules/mod_vhost_alias.so
    LoadModule negotiation_module modules/mod_negotiation.so
    LoadModule dir_module modules/mod_dir.so
    LoadModule imagemap_module modules/mod_imagemap.so
    LoadModule actions_module modules/mod_actions.so
    LoadModule speling_module modules/mod_speling.so
    LoadModule userdir_module modules/mod_userdir.so
    LoadModule alias_module modules/mod_alias.so
    LoadModule rewrite_module modules/mod_rewrite.so
    LoadModule php5_module modules/libphp5.so
    LoadModule php5_module /usr/lib/httpd/modules/libphp5.so
    AddHandler php5-script php
    <IfModule !mpm_netware_module>
    <IfModule !mpm_winnt_module>
    # If you wish httpd to run as a different user or group, you must run
    # httpd as root initially and it will switch.
    # User/Group: The name (or #number) of the user/group to run httpd as.
    # It is usually good practice to create a dedicated user and group for
    # running httpd, as with most system services.
    User http
    Group http
    </IfModule>
    </IfModule>
    # 'Main' server configuration
    # The directives in this section set up the values used by the 'main'
    # server, which responds to any requests that aren't handled by a
    # <VirtualHost> definition. These values also provide defaults for
    # any <VirtualHost> containers you may define later in the file.
    # All of these directives may appear inside <VirtualHost> containers,
    # in which case these default settings will be overridden for the
    # virtual host being defined.
    # ServerAdmin: Your address, where problems with the server should be
    # e-mailed. This address appears on some server-generated pages, such
    # as error documents. e.g. [email protected]
    ServerAdmin [email protected]
    # ServerName gives the name and port that the server uses to identify itself.
    # This can often be determined automatically, but we recommend you specify
    # it explicitly to prevent problems during startup.
    # If your host doesn't have a registered DNS name, enter its IP address here.
    ServerName 192.168.1.100:9292
    # DocumentRoot: The directory out of which you will serve your
    # documents. By default, all requests are taken from this directory, but
    # symbolic links and aliases may be used to point to other locations.
    DocumentRoot "/srv/http"
    # Each directory to which Apache has access can be configured with respect
    # to which services and features are allowed and/or disabled in that
    # directory (and its subdirectories).
    # First, we configure the "default" to be a very restrictive set of
    # features.
    <Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
    </Directory>
    # Note that from this point forward you must specifically allow
    # particular features to be enabled - so if something's not working as
    # you might expect, make sure that you have specifically enabled it
    # below.
    # This should be changed to whatever you set DocumentRoot to.
    <Directory "/srv/http">
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    # The Options directive is both complicated and important. Please see
    # http://httpd.apache.org/docs/2.2/mod/core.html#options
    # for more information.
    Options Indexes FollowSymLinks
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    # Options FileInfo AuthConfig Limit
    AllowOverride None
    # Controls who can get stuff from this server.
    Order allow,deny
    Allow from all
    </Directory>
    # DirectoryIndex: sets the file that Apache will serve if a directory
    # is requested.
    <IfModule dir_module>
    DirectoryIndex index.html
    </IfModule>
    # The following lines prevent .htaccess and .htpasswd files from being
    # viewed by Web clients.
    <FilesMatch "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy All
    </FilesMatch>
    # ErrorLog: The location of the error log file.
    # If you do not specify an ErrorLog directive within a <VirtualHost>
    # container, error messages relating to that virtual host will be
    # logged here. If you *do* define an error logfile for a <VirtualHost>
    # container, that host's errors will be logged there and not here.
    ErrorLog "/var/log/httpd/error_log"
    # LogLevel: Control the number of messages logged to the error_log.
    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel warn
    <IfModule log_config_module>
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common
    <IfModule logio_module>
    # You need to enable mod_logio.c to use %I and %O
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here. Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    CustomLog "/var/log/httpd/access_log" common
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #CustomLog "/var/log/httpd/access_log" combined
    </IfModule>
    <IfModule alias_module>
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL. You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client. The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    ScriptAlias /cgi-bin/ "/srv/http/cgi-bin/"
    </IfModule>
    <IfModule cgid_module>
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #Scriptsock /var/run/httpd/cgisock
    </IfModule>
    # "/srv/http/cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have that configured.
    <Directory "/srv/http/cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
    </Directory>
    # DefaultType: the default MIME type the server will use for a document
    # if it cannot otherwise determine one, such as from filename extensions.
    # If your server contains mostly text or HTML documents, "text/plain" is
    # a good value. If most of your content is binary, such as applications
    # or images, you may want to use "application/octet-stream" instead to
    # keep browsers from trying to display binary files as though they are
    # text.
    DefaultType text/plain
    <IfModule mime_module>
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    TypesConfig conf/mime.types
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #AddType application/x-gzip .tgz
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #AddHandler cgi-script .cgi
    # For type maps (negotiated resources):
    #AddHandler type-map var
    # Filters allow you to process content before it is sent to the client.
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
    </IfModule>
    # The mod_mime_magic module allows the server to use various hints from the
    # contents of the file itself to determine its type. The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    #MIMEMagicFile conf/magic
    # Customizable error responses come in three flavors:
    # 1) plain text 2) local redirects 3) external redirects
    # Some examples:
    #ErrorDocument 500 "The server made a boo boo."
    #ErrorDocument 404 /missing.html
    #ErrorDocument 404 "/cgi-bin/missing_handler.pl"
    #ErrorDocument 402 http://www.example.com/subscription_info.html
    # EnableMMAP and EnableSendfile: On systems that support it,
    # memory-mapping or the sendfile syscall is used to deliver
    # files. This usually improves server performance, but must
    # be turned off when serving from networked-mounted
    # filesystems or if support for these functions is otherwise
    # broken on your system.
    #EnableMMAP off
    #EnableSendfile off
    # Supplemental configuration
    # The configuration files in the conf/extra/ directory can be
    # included to add extra features or to modify the default configuration of
    # the server, or you may simply copy their contents here and change as
    # necessary.
    # Server-pool management (MPM specific)
    #Include conf/extra/httpd-mpm.conf
    # Multi-language error messages
    Include conf/extra/httpd-multilang-errordoc.conf
    # Fancy directory listings
    Include conf/extra/httpd-autoindex.conf
    # Language settings
    Include conf/extra/httpd-languages.conf
    # User home directories
    Include conf/extra/httpd-userdir.conf
    # Real-time info on requests and configuration
    #Include conf/extra/httpd-info.conf
    # Virtual hosts
    #Include conf/extra/httpd-vhosts.conf
    # Local access to the Apache HTTP Server Manual
    #Include conf/extra/httpd-manual.conf
    # Distributed authoring and versioning (WebDAV)
    #Include conf/extra/httpd-dav.conf
    # Various default settings
    Include conf/extra/httpd-default.conf
    Include conf/extra/php5_module.conf
    # Secure (SSL/TLS) connections
    #Include conf/extra/httpd-ssl.conf
    # Note: The following must must be present to support
    # starting without SSL on platforms with no /dev/random equivalent
    # but a statically compiled-in mod_ssl.
    <IfModule ssl_module>
    SSLRandomSeed startup builtin
    SSLRandomSeed connect builtin
    </IfModule>
    Last edited by Rumor (2009-01-29 15:04:27)

    You could try a factory reset of the home hub, as sometimes the config can get corrupted.
    There is some general help on this page.
    Help with setting up routers, wireless repeaters, TVs and printers, CCTV cameras, VOIP Phones
    There are some useful help pages here, for BT Broadband customers only, on my personal website.
    BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

  • How to connect your Verizon 4510L to your home Wifi Network

    Hello there! 
    I recently set my mom up with one of these guys and ran into the problem of having more than 5 devices that need to connect to the Internet and/or each other.  I couldn't find any resources online that described how this can be done, or even if it is allowed.  So I figured I would finally contribute to the Online community and share my success with all of you!  As a disclaimer:  I am not Verizon/Linksys/etc technical support and provide the following information freely and without warranty. The instructions below are specific to my configuration, and while yours WILL work using the same general principles, the exact steps required to make it work may be different.  In other words, YMMV   Good Luck!
    First off, my environment doesn't equal your environment, and what I will describe below is one of the more complex scenarios.  You can disregard any extra routers if you only use 1.  Here is the environment I had to work with:
    A large 2 story home with a basement area as well.  The wifi signal does not travel well from floor to floor, so we had to have 1 wireless router per floor.  We DID have the luxury of using home wiring to to phsycally connect both routers together, if you don't have that luxury, I might suggest using a "Powerline" adapter to help wire your two routers together.  Some devices required wired connectivity on both floors as well, so wireless repeaters would not be sufficient.  We purchased 2 routers to accomplish the following task.  Brand of router should not matter.  If your home is a 1 story, or have adequate coverage from a single router, you can disregard the 2nd (SLAVE) router instructions (4-5) below. 
    First off, what you will need to make this work:
    One or more Wireless Routers (we used Linksys Wireless-G or Wireless-N 4-port routers)
         *EDIT: You need only 1 router, and if an additional access point is needed, purchase an Access Point or repeater with wired/wireless capabilities*
    Verizon JetPack 4510L MiFI device
    One Wireless Bridge (we used Linksys WET610 1-port Entertainment Bridge)
    Next, lets setup the wireless/wired home network to connect all devices with one another:
    1) Choose one router to be the MASTER, and the other to simply be your SLAVE/repeater for the other floor.
    2) Before physically connecting the MASTER and SLAVE routers together perform the following:
    3) On the MASTER router:
         - Change the router IP address to 192.168.10.1
              - The 10 is random, and you can make it whatever you want (as long as it isn't "1"), just remember it and keep it consistent.
         - Configure DHCP (usually on by default) but change the subnet from 192.168.1.x to 192.168.10.x.
              - The reason for changing the DHCP subnet is because your 4510L device uses DHCP as well, and it is configured to use 192.168.1.x
                   - They can't be the same or it won't work
         - Configure your wireless SSID and security (preferably WPA2)
    4) On the SLAVE router *EDIT: or repeater or access point*:
         - Change the router IP address something outside the DHCP range 1-100, but on the same subnet as the master router (ie. 192.168.10.101)
         - Disable DHCP on the router, as all address assignment is going to come from the MASTER
              - You may want to tape over the WAN port as well to remind yourself that it will not be used
         - Configure your wireless SSID and security to match that of the MASTER router
              - This will make it easier for your clients to use both access points and move throughout your home without having an issue
    5) Connect both routers together with Ethernet (either direct cable, home ethernet wiring, powerline adapter, etc)
         - You want to connect both routers using one of the built in network ports (1-4)
    There, now you have both floors of your home setup to accept either wired or wireless clients who will be assigned 192.168.10.x IP addresses.  However, they will not have access to the Internet...yet!
    The MiFi device by default has a long SSID, and the password to connect is on a label on the bottom of it.  Power it on in the room next to a computer (probably a windows computer), and view your wireless networks to connect to from the desktop.  You will probably see the wireless network name you just created on the routers and the "Verizon ..." MiFi name.  Simply make a note of the EXACT SSID being broadcasted by the MiFi device.  If you changed the default WiFi password before attempting this, make a note of that new password as well.
    Next, lets use the key to making this thing work...the Wireless Bridge.  The wireless bridge first needs to be physically connected to either router on ports 1-4.  The bridge will get an IP address assigned to it and you will need to find that address out so that you can access it from a web browser.  The easiest way to find that out is to connect to the MASTER routers web-based administration page (http://192.168.10.1), click on Status menu->Local network, and then click the "DHCP client table" button.  You will find the bridge name and IP address there.  Keep that administration window open. 
    Next, connect your web browser with the bridges IP address so that you can manually configure it to access the MiFi device.  The bridge will ask if you want auto or manual configuration, and you want manual.  When prompted for the SSID and security type, type in the SSID of the MiFi device EXACTLY as you wrote it down.  Next, under security, change the type to WPA2-Personal, and type in the password to access the Verizon MiFi device (either on the sticker under it, or whatever you previously changed it to).  Once you complete that setup, the status page should tell you that the bridge is connected and have an IP address (192.168.1.x) assigned to it.  Once that is done, you can close your web browser to the wireless bridge.
    Disconnect the bridge from the routers network ports and now connect it to the MASTER routers WAN port.
    Next, return to the MASTER routers web-based administration page (http://192.168.10.1), click on the Status menu and view the WAN IP information.  If everything was connected correctly:
    MiFi wirelessly -> Wireless Bridge wired -> Master router WAN port (then optionally wired from port 1) -> Slave router port 1 
    Then, you should see the WAN IP address of 192.168.1.x assigned to your MASTER router.
    If you do see that, then congratulations, open a web browser from any of your wired/wireless clients connected to your home network, and you should be able to access the Internet!  You will be able to support as many clients as your Routers will allow you to directly connect (104 if I am not mistaken)...Yay!
    I hope my experience helps you all in achieving the same results!
    Troubleshooting:
    If you do not see a WAN IP address, you might want to power off the MASTER router, the Wireless Bridge and MiFi device.  Then in the following order power up each one, one at a time, giving the unit time to fully configure and connect to their respective networks:  First MiFi, then the Bridge, then the MASTER router.
    After the Master router is fully powered on, test a webpage again from any client connected to your new home network and it should work. 
    If it _still_ doesn't work, I would recheck the steps listed above to see if anything was missed.  Particularly, making sure you changed the router IP and DHCP subnet of the MASTER router to something other than 192.168.1.x.
    Good Luck!

    Q: "In your example of using the wireless repeater, assuming it is on a different floor than the main router, how are the clients connecting to the network on that floor?"
    A: However you like, both devices support thier own cabled and wireless connections. 
    I assume you are only interested in wireless client connections since cable connections are straight forward.  Depending on how you setup the SSID's clients will connect to either the router or the repeater and they should be overlapping eachother a little. 
    Same SSID:
    If the router and repeater share the same SSID then the client will decide on thier own which one to connect to.  The client will roam between the two on its own criteria as the user moves around the enviornment.  Roaming and transitioning will happen seamlessly for you and you should not notice a break in your connection unless you have something really specific connected to the internet.  In most cases you cannot influence this behavior on your devices as they all have thier own criteria for choosing one SSID over another with a similar name. 
    Different SSID:
    If the SSID's are different then the user must manually connect to one network or the other.  Roaming will not be seamless and as the user walks out of range the client will be disconnected from the device.  This provides the best reliability and control but requires more user intervention.
    Q:"So correct me if I am wrong, but in your setup, there would be 2 wifi network, and the soft limitation of 4 devices on the repeater floor.
    A. Nope, the repeater will support as many devices as it can, depending on the model you purchase.  Even though the repeater needs a wireless connection with the MiFi, the Repeater rebroadcasts and acts as its own independant wireless router.  The MiFi could care lesss how many people are connected to the Repeater, all it see's is one connection.  If you removed the MiFi from the repeater then the repeater will continue to broadcast its own SSID.  Clients connected to the repeater will not be disconnected from the repeater SSID but they would not recieve internet until the MiFi returns.
    With the repeater enviornment you could have 10 people on the repeater, 10 people on the wireless router and 4 people directly conneted to the MiFi all at the same time.  I dont suggest it running like that for performance reasons but hopefully you get the idea.

  • Linking D-Link DIR 655 and AirPort Extreme

    Help! I need to link my D-Link DIR-655 and new Airport Extreme, but have no idea how to do it. I use the D-Link as my base router and want to use the Airport Extreme as a repeater/range extender upstairs in the house (the D-Link is in my office in the basement)where I use my Macbook Pro. The D-Link signal isn’t strong enough to reach areas of the upstairs. How can I make these two pieces of hardware work together? Is it possible? Any help would be greatly appreciated. I’m not a tech whiz.

    I use the D-Link as my base router and want to use the Airport Extreme as a repeater/range extender upstairs in the house
    The "extend a network" feature of the Extreme is intended to extend a wireless network created by another 802.11n Apple Airport product (Extreme, Express or Time Capsule).
    Wireless repeaters or "extenders" use proprietary techniques that don't work well among different manufacturers. To extend your network wirelessly in the manner you seek would require that you replace your D-Link with another Airport, or replace the Express with a D-Link product.
    The ideal solution in your case would be to run an Ethernet cable between the devices. That will work.

  • Very slow BB since modem upgrade

    Hi
    I've recently went through with the modem upgrade provided by Kelly Comms. Seemed ok at first but now my connection is pretty much unusable upstairs.
    Download speed is 1.6MBs upstairs but much better close to the modem (understandably).
    Any options? Powerline? How much to get a cable professionally done ?
    Can BT do anything? this is useless
    Robert

    Yeah, wireless
    So the only options are powerline adapter, cable (unlikely option) really. Wonder why it has reduced as much though.
    Do wireless repeaters help?

  • Bt Infinity and variable channels used with fixed ...

    Hi
    I have BT Infinity and 2 wireless repeaters. One for Sky and the other in a blind spot in the house. I've found that Infinity
    seems to work best when I change the settings so that the hub automatically changes the channel however the repeaters
    only have a fixed channel option and so keep dropping out.
    So for instance I'll set the repeaters to channel 11 and the hub to varied channel. This means that the repeaters only work when the hub switches to channel 11.
    Is there any way around this?
    Thanking you
    JoJoH

    No, you could set your hubs channel to 11.
    If this helped you please click the Star beside my name.
    If this answered your question please click "Mark as Accepted Solution" below.

  • IP CCTV viewing on my iphone

    I am installing a Foscam ipcctv camera. At present I have a BT Homehub2 and wish to set up my hub so I can view the camera on my iphone and my wife's andriod nokia. I have 2 questions.
    a  Is there a help page that will advise me of procedures
    b Would I be better to update to the new HH4. 
     Really need some help hear as I have been told that I may need to replace my hub with none BT.
                                              Thanks John

    The camera should work fine, especially on the home hub 2.
    There is help on these pages.
    Help with setting up routers, wireless repeaters, TVs and printers, CCTV cameras, VOIP Phones
    Port forwarding problems
    There are some useful help pages here, for BT Broadband customers only, on my personal website.
    BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

  • Amplifying the WiFi signal

    Hello. I am a new member here. I want to amplify the already existing WiFi signal in our house. Is it a good idea to buy an AirPort Express to do that? Or a simple repeater would do the job?
    Thanks in advance for any reply.
    Autolykos

    An Express cannot amplify wireless ever..
    It can act as extender to another Apple wireless router.. but no other brand.
    I would strongly recommend you buy a repeater based on the exact hardware you already own.. or plan on connecting various wireless items by ethernet..
    The problem is wireless repeater tends to be propriety. Apple routers cannot extend wireless for other brands.. and many other brands cannot extend wireless for apple. The old wireless repeater codes were not updated from WEP security.. and so each company does what they think is best.
    You can buy universal wireless repeaters but they work poorly.. !!
    And I strongly encourage you not to wireless repeat at all.. due to the fact that it will slow the network down drastically.

Maybe you are looking for