Wireless signal from 2Wire HomePortal 1000HG b/g router stops working until reset

Do you have any logging enabled on the 2wire? Can you see if you can enable logging and set it to the highest level..See if there are any errors reported after a loss of connectivity event and post them here. Thanks

I am including with this comment the detailed event log from the router's control panel. The log appears to begin at the time I power cycled it, which was after the wireless had stopped working. I also changed the channel to see if it would help. I will post an additional log after the wireless signal is lost.

INF	+000 days 00:00:03	initd:  ---------------------------------------------
INF	+000 days 00:00:04	cm:  cm initialized
INF	+000 days 00:00:04	initd:  libcm started
INF	+000 days 00:00:04	initd:  initd starting runlevel: 3 => 7
INF	+000 days 00:00:04	ulib:  System clock initialized
INF	+000 days 00:00:04	ulib:  Board serial number: 294116013534
INF	+000 days 00:00:04	ulib:  ulib initialized
INF	+000 days 00:00:04	initd:  libulib start
INF	+000 days 00:00:04	initd:  initd starting runlevel: 4 => 7
INF	+000 days 00:00:04	initd:  pkg start pid: 11
INF	+000 days 00:00:04	pkg:  extracted system/system
INF	+000 days 00:00:04	initd:  pkgc start
INF	+000 days 00:00:04	initd:  login start pid: 13
INF	+000 days 00:00:04	pki:  pki initialized
INF	+000 days 00:00:04	initd:  pki start
INF	+000 days 00:00:04	initd:  syslogd start pid: 14
INF	+000 days 00:00:04	initd:  initd starting runlevel: 5 => 7
INF	+000 days 00:00:04	initd:  lmd start pid: 15
INF	+000 days 00:00:04	initd:  initd starting runlevel: 6 => 7
INF	+000 days 00:00:04	initd:  nodesd start pid: 16
INF	+000 days 00:00:04	initd:  dhcpd start pid: 17
INF	+000 days 00:00:04	initd:  named start pid: 18
INF	+000 days 00:00:04	initd:  initd starting runlevel: 7 => 7
INF	+000 days 00:00:04	named:  domainname: gateway.2wire.net
INF	+000 days 00:00:04	named:  hostname: homeportal.gateway.2wire.net
INF	+000 days 00:00:06	wave:  fw ver: Rev 0.8.0.37, hw ver: 3.1.1.1
INF	+000 days 00:00:06	lmd:  ipnet1: UP on vlan0 with 192.168.1.254/24
INF	+000 days 00:00:06	atm:  port 0 opened
INF	+000 days 00:00:06	ulib:  Wireless ESSID set to 2WIRE534
INF	+000 days 00:00:06	ulib:  Wireless authentication set to Open
INF	+000 days 00:00:06	ulib:  Wireless encryption set to WEP
INF	+000 days 00:00:06	ulib:  Wireless WEP key set
INF	+000 days 00:00:06	ulib:  Wireless channel set to 6
INF	+000 days 00:00:06	ulib:  Wireless power set to 100
INF	+000 days 00:00:06	named:  listen on address[0]: 192.168.1.254
INF	+000 days 00:00:19	pkg:  extracted ui/base_ui
INF	+000 days 00:00:19	pkg:  extracted provider/2wire
INF	+000 days 00:00:19	pkg:  note: provider/2wire has no uninstall script
INF	+000 days 00:00:20	pkg:  extracted lang/2wire_fr
INF	+000 days 00:00:21	pkg:  extracted lang/2wire_es
INF	+000 days 00:00:21	initd:  pkgc start
INF	+000 days 00:00:21	initd:  rfsd start pid: 28
INF	+000 days 00:00:21	initd:  httpd start pid: 29
INF	+000 days 00:00:21	initd:  System boot to runlevel: 7 complete
INF	+000 days 00:00:21	httpd:  http server initializing
INF	+000 days 00:00:28	lmd:  dsl0: up G.DMT fast Rate:768/384 Max:5120/792
INF	+000 days 00:00:28	lmd:  Margin:16.0/16.0 Atten:43.0/30.0 Power:11.5/8.9
INF	+000 days 00:00:28	lmd:  Country: {F} Vendor: {ALCB} Specific: {0}
INF	+000 days 00:00:30	lmd:  apvc0: found BRDG_LLC PPPoE on 0/35 round 0
INF	+000 days 00:00:31	lmd:  apvc0: using preferred pvc 0/35
INF	+000 days 00:00:31	httpd:  webs xslt uiconf.xml loaded mem:839548 pages:392
INF	+000 days 00:00:31	lmd:  vlan1: creating ethatm0 PVC 0/35 dev:(45,0)
INF	+000 days 00:00:33	lmd:  pppoe0: up with service: (default), ac: se6.bcvloh-B2224060701950 on vlan1
NTC	+000 days 00:00:34	ppp:  local IP address 99.155.83.128
NTC	+000 days 00:00:34	ppp:  remote IP address 99.155.87.254
NTC	+000 days 00:00:34	ppp:  primary DNS address 68.94.156.1
NTC	+000 days 00:00:34	ppp:  secondary DNS address 68.94.157.1
INF	+000 days 00:00:34	ppp:  ppp0: up with ipv4 service on pppoe0
INF	+000 days 00:00:35	httpd:  init module (xslt)
INF	+000 days 00:00:35	httpd:  init module (file)
INF	+000 days 00:00:35	httpd:  vhost home0 listening on 192.168.1.254 port: 80
INF	+000 days 00:00:35	httpd:  vhost home0 listening on 127.0.0.1 port: 80
INF	+000 days 00:00:35	httpd:  vhost home0 listening on 192.168.1.254 port: 443
INF	+000 days 00:00:35	lmd:  ipnet0: UP on ppp0 with 99.155.83.128/32 GW:99.155.87.254
INF	+000 days 00:00:35	lmd:  ipnet0: UP on ppp0 DNS1: 68.94.156.1 DNS2: 68.94.157.1
INF	+000 days 00:00:35	initd:  initd starting runlevel: 8 => 8
INF	+000 days 00:00:35	initd:  sntpcd start pid: 30
INF	2009/08/22 19:15:18 EDT	initd:  initd starting runlevel: 9 => 9
INF	2009/08/22 19:15:18 EDT	ulib:  Updated system clock from: 2002/04/04 03:11:48 PST
INF	2009/08/22 19:15:18 EDT	ulib:  Set system clock to: 2009/08/22 16:15:18 PDT
INF	2009/08/22 19:15:18 EDT	initd:  rpcd start pid: 31
INF	2009/08/22 19:15:18 EDT	rpcd:  Using CMS server at gw-3-7-1.rpc.cms.2wire.com:3479
INF	2009/08/22 19:15:18 EDT	rpcd:  issuing BOOT heartbeat request
INF	2009/08/22 19:15:21 EDT	wave:  Received unknown ie 21 02 08 12
INF	2009/08/22 19:15:21 EDT	wave:  Received unknown ie 24 02 01 0E
INF	2009/08/22 19:15:24 EDT	rpcd:  BOOT heartbeat completed
INF	2009/08/22 19:15:26 EDT	httpd:  Using existing SSL root key, length: 607
INF	2009/08/22 19:15:27 EDT	httpd:  vhost mdc0 listening on 99.155.83.128 port: 50001
INF	2009/08/22 19:15:48 EDT	rpcd:  issuing SCHEDULED heartbeat request
INF	2009/08/22 19:15:50 EDT	rpcd:  SCHEDULED heartbeat completed
INF	2009/08/22 19:17:25 EDT	system:  memfs: compression completed
INF	2009/08/22 19:24:09 EDT	ulib:  Wireless ESSID set to 2WIRE534
INF	2009/08/22 19:24:09 EDT	ulib:  Wireless authentication set to Open
INF	2009/08/22 19:24:09 EDT	ulib:  Wireless encryption set to WEP
INF	2009/08/22 19:24:09 EDT	ulib:  Wireless WEP key set
INF	2009/08/22 19:24:09 EDT	ulib:  Wireless channel set to 1
INF	2009/08/22 19:24:09 EDT	ulib:  Wireless power set to 100
ERR	2009/08/22 19:24:11 EDT	wave:  WDRV_MGMT: Error parsing reAssoc req,Unexpected eleId = 33
ERR	2009/08/22 19:24:11 EDT	wave:  WDRV_MGMT: Error parsing reAssoc req,Unexpected eleId = 36
INF	2009/08/22 20:18:48 EDT	rpcd:  issuing SCHEDULED heartbeat request
INF	2009/08/22 20:18:48 EDT	rpcd:  SCHEDULED heartbeat completed
INF	2009/08/23 03:17:39 EDT	wave:  Received unknown ie 21 02 08 12
INF	2009/08/23 03:17:39 EDT	wave:  Received unknown ie 24 02 01 0E

Select allOpen in new window

From the logs it's a re-association error. Do you have the latest firmware installed? Have you tried changing the security to another method other than WEP like WPA/WPA2 or none? (none would obviously be temporary for testing purposes). Does this happen on multiple clients or just one? (problem with the AP or the client)

The errors in the above log could be from the wireless clients trying to automatically reconnect after the channel was changed. The router reports no available firmware updates, and the problem occurs when using WPA as well. When the signal is lost, all wireless clients (2 laptops and a media center extender) are unable to connect until a reboot or channel change, while wired computers remain connected with no problems.

The router's wireless signal has just stopped working; here is the additional event log.

INF  2009/08/23 17:29:17 EDT  rpcd:  issuing PERIODIC heartbeat request 
INF  2009/08/23 17:29:22 EDT  rpcd:  PERIODIC heartbeat completed 
INF  2009/08/23 19:41:49 EDT  wave:  Received unknown ie 21 02 08 12  
INF  2009/08/23 19:41:49 EDT  wave:  Received unknown ie 24 02 01 0E

Select allOpen in new window

I'm not familiar enough with the logs from this device to decipher the error.

nmcnair?

Hmm..Those log events don't tell us much..Do you have any units hardwired to this router? IF so are they able to access the Internet when the wireless connections go out?

When the wireless goes out the wired computers are completely unaffected. Local network and Internet access continues for all wired computers. The HomePortal router is connected to an Ethernet switch, which connects the desktops. I can only access the Web-based control panel on these computers when the wireless signal goes out; the laptops become completely disconnected and have no network access, giving themselves their own '169.x.x.x' IP address. At one point (see the original question) a Windows server was used for DHCP, and the same problem with wireless clients happened due to the router. The router is a number of years old and has seen a lot of use. Many people are suggesting that it is defective; I would just like a way to confirm that this is case before replacing it.

Hi,

I advise to make a site survey with inssider!

This tool will give you a visual view of signal strength and some basic details:
http://www.metageek.net/products/inssider

Colud you show me the output?

That is a neat tool. I have attached the output; the router is '2WIRE534'.
inssider.jpg

HI,
It ssems channel 3 the best for you

Thanks for the advice, but even on channel 3 it ends up disconnecting all the wireless clients.

Have you tried DetailIT's suggestion of trying a differant router to see if the problem remains?

The channel 14 i sclear but not compatible a lot of wireless card, and don't forget 1-11 channels use in the americans laptops!!The channel 3 is enough, becous there is 25dB benefit

Could this type of problem be a result of nearby networks instead of a faulty device? I would like to determine if this is a hardware issue or a wireless interference issue.

fisrtly change it tho channel 3 and say me whats happened

The same problem occurs when the wireless channel is set to 3.

Is the DHCP is working correctly?

For the wired clients it is always working. For wireless clients, it stops working. This is regardless of which DHCP server is used.

https://www.experts-exchange.com/questions/24674029/Wireless-signal-from-2Wire-HomePortal-1000HG-b-g-router-stops-working-until-reset.html?cid=1575#25169368

> Could this type of problem be a result of nearby networks instead of a faulty device?

Yes, as I said in http:#25303350

Look at the output from inSSIDer... the 2WIRE534 and 2WIRE897 networks are interfering the most, with the 2WIRE059 on channel 10 interfering only slightly.
Switching to channel 3 will just make you overlap and interfere with (and be interfered with by) the neworks named Motorola and SASAK on channel 1, and 2WIRE897 on channel 6.

It's probably going to be fruitless asking everyone to turn down their power and use ONLY channels 1, 6 or 11, to minimize interference, so the best solution is going to be switching to 5GHz (802.11a and/or 5GHz 802.11n when that standard is finalized, hopefully within a few months). There are over a dozen non-overlapping channels in the 5GHz UNII band instead of only 3 as in the 2.4GHz ISM band.

but they it has 2Wire Home Portal 1000HG USB/Ethernet External DSL Modem, it build wirh 802.11b/g Wi-Fi it not suppported 5Ghz, and if you see he has 25 dB to throttle MOtorola SSId and 30 Db to throttle 2WIRE897!!!!

I think it is not channel problem, did you tried reload the modem and pcs?

Yes, I have tried factory resetting the HomePortal and reinstalling Windows.

Overpowering nearby networks is not the answer... if one of the interfering networks is run by a licensed HAM, they can legally use twice as much power that you can. Are you just going to hook up an illegal linear amp and crank it even further until the FCC comes knocking to confiscate your gear and issue citations/fines?

I never said the 2wire unit supports 5GHz, what I was inferring was to buy equipment that DOES support 5GHz.
The 802.11n spec was finally approved by the IEEE standards association group, by the way... hopefully we'll soon be seeing products without the 'draft' appellation.

Hi Darr247!

Please refer the following:
www.cisco.com/en/US/docs/routers/access/3200/software/wireless/RadioChannelFrequencies.pdf

The channel 14 is not supported on all Regulatory Domains!

Recently the router's status lights shut off and all computers became disconnected from the network. The router is now inaccessible and acts dead, no longer making the several quiet 'clicks' it did when it is plugged in or the reset button is pressed. The indicator lights are dim for a quick moment, and then nothing. As the router is also the DSL modem I had no other choice than to replace it at that point. It has been replaced with a 2Wire HomePortal 2700HG-B (wireless b/g) modem/router/AP. I performed a site survey with the new router, named 'CubeZero'. Do these results indicate that there may be future problems with the new device, or (the 1000HG was not surge protected by the previous owner) could this issue have instead been a result of hardware failure?
inssider.jpg

In this case better way to buy 802.1a or 802.1n compatible radios....

If you refer to http://standards.ieee.org/getieee802/802.1.html you'll find a list of 802.1 standards

I don't see 802.1a or 802.1n listed there.
 
While the signal is currently stronger (at the location where you measured it) than the 2WIRE748, 2WIRE063 and Colleen SSIDs, if the owner of the Colleen station is a licensed HAM and decides to double their power level, it will likely knock you and everyone else from channel 2 through channel 10 off the air.

As I noted previously, the best long-term solution will be switching over to the 5GHz band, if possible


In http:#25397482, ikalmar said:
> The channel 14 is not supported on all Regulatory Domains!

Correct, and I did say that in http:#25303198 when I posted the frequency chart to help visualize how the channels overlap and interfere with each other in the 2.4GHz ISM band.