Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[biker]

  I know very little about routers. I bought a DIR 655 and got it hooked up with the disc, also Network Magic is running now.
  I have a wireless device hooked to port #4 and my computer hooked to port # 1.
   

The computer seems to work great, however the wireless device (Home Plug Wave) works and doesn’t work as it pleases it seems. On Network Magic you can watch it engage and disengage as though it looses connection and finds it again. Each time this happens it takes varying times to “reconnect’ and stays “connected” for varying lengths of time.
  I got this unit before Christmas and the firmware is 1.1 as I have not done any upgrades.
  I have done a ping test and if I put in my computer IP and there was nothing, but if I put in the wireless device address it comes back in milli seconds.
  If I am in the wrong section or have made any other faux pas please forgive and direct me to where I should go.
TKS,
biker

[biker]

I should have mentioned that I am working with a SB 5100 Motorola modem on the Rogers network.
TKS, again
biker

[EddieZ]

Thanks for the info, Biker.

You might want to upgrade to 1.21 first and see how things go.

[biker]

I read alot of problems on this forum about 1.21 and because of my newbie status have a certain amount of fear at doing so as I can't figure this out and may just be going deeper.
Just to clear up something, when I say wirelessI mean there is a cat5 cable from #4 port on the 655 to the plugin which plugs into a wall outlet. Another plugin( same device) plugs in in another room and has a cat5 hooked into the device, I believe this is wireless...correct?

[EddieZ]

Nope, that's what we call Power line communication (also known as 'Homeplug'), internet through your home electricity powerlines. Wireless is what is says: no wires, not even electricity wires. 

I'm incliden to say that the powerline adapters can equally be the cause. Just make sure you can eliminate the powerline internet from being the cause of the problems. Powerline can work great but does not always deliver good quality (interference, different groups).
- connect the powerline directly into the wall socket (no extention cable);
- when you have multiple wall sockets (usually two next to eachother), do not use the other connection

To eliminate the powerline adapters:
1. plug the receiving powerline adapter in a very nearby wall socket, preferably one that is connect in the same socket 'grouping' (phase). If the signal is OK (no on/off), the electricty powerline is the cause (redesigning your home electricty plan is the only soltion/ bridging differtent groups (can be dangerous))
2. The powerline adapters can be configured (fixed IP, use DHCP). Try different settings.

[biker]

I ran direct with cat 6 and had the same thing.
I checked the log on the router and found alot of blocked incoming from some addresses that looked the same,could it be the configuration of the router?

[EddieZ]

Post them and we'll have a look

[biker]

is this enough?

Priority   Time   Message
[INFO]   Fri Jan 16 09:35:31 2009   Allowed configuration authentication by IP address 192.168.0.197
[INFO]   Fri Jan 16 09:33:11 2009   Blocked incoming TCP connection request from 200.117.208.127:50066 to 99.252.46.163:12500
[INFO]   Fri Jan 16 09:32:50 2009   Above message repeated 3 times
[INFO]   Fri Jan 16 09:26:19 2009   Blocked incoming TCP connection request from 90.200.164.71:2293 to 99.252.46.163:12500
[INFO]   Fri Jan 16 09:26:10 2009   Above message repeated 2 times
[INFO]   Fri Jan 16 09:25:55 2009   Blocked incoming TCP connection request from 82.149.28.248:1142 to 99.252.46.163:12500
[INFO]   Fri Jan 16 09:25:46 2009   Above message repeated 2 times
[INFO]   Fri Jan 16 09:24:50 2009   Blocked incoming UDP packet from 71.245.108.227:44852 to 99.252.46.163:41224
[INFO]   Fri Jan 16 09:24:29 2009   Blocked incoming TCP connection request from 76.124.229.129:49164 to 99.252.46.163:41224
[INFO]   Fri Jan 16 09:24:20 2009   Above message repeated 2 times
[INFO]   Fri Jan 16 09:24:09 2009   Blocked incoming UDP packet from 98.227.79.133:17339 to 99.252.46.163:41224
[INFO]   Fri Jan 16 09:23:46 2009   Blocked incoming TCP connection request from 86.210.40.160:52214 to 99.252.46.163:28932
[INFO]   Fri Jan 16 09:23:41 2009   Above message repeated 5 times
[INFO]   Fri Jan 16 09:22:47 2009   Blocked incoming UDP packet from 218.110.159.123:30710 to 99.252.46.163:41224
[INFO]   Fri Jan 16 09:22:39 2009   Blocked incoming UDP packet from 86.210.40.160:50203 to 99.252.46.163:28932
[INFO]   Fri Jan 16 09:21:19 2009   UPnP deleted entry 255.255.255.255 <-> 99.252.46.163:64737 TCP
[INFO]   Fri Jan 16 09:21:18 2009   UPnP added entry 255.255.255.255 <-> 99.252.46.163:64737 <-> 192.168.0.197:8593 TCP timeout:-1 'MsnMsgr (192.168.0.197:8593) 64737 TCP'
[INFO]   Fri Jan 16 09:21:18 2009   UPnP added entry 255.255.255.255 <-> 99.252.46.163:51165 <-> 192.168.0.197:7594 UDP timeout:-1 'MsnMsgr (192.168.0.197:7594) 51165 UDP'
[INFO]   Fri Jan 16 09:21:18 2009   UPnP deleted entry 255.255.255.255 <-> 99.252.46.163:13539 TCP
[INFO]   Fri Jan 16 09:21:18 2009   UPnP deleted entry 255.255.255.255 <-> 99.252.46.163:58336 UDP
[INFO]   Fri Jan 16 09:20:16 2009   Blocked incoming UDP packet from 60.222.224.135:39316 to 99.252.46.163:1027
[INFO]   Fri Jan 16 09:19:00 2009   Blocked incoming TCP connection request from 79.109.218.128:48580 to 99.252.46.163:12500
[INFO]   Fri Jan 16 09:18:51 2009   Above message repeated 2 times
[INFO]   Fri Jan 16 09:18:42 2009   Blocked incoming UDP packet from 60.15.177.168:54586 to 99.252.46.163:1026
[INFO]   Fri Jan 16 09:18:13 2009   Blocked incoming UDP packet from 78.183.18.108:17520 to 99.252.46.163:41224
[INFO]   Fri Jan 16 09:16:31 2009   Blocked incoming TCP connection request from 79.147.113.1:51271 to 99.252.46.163:12500
[INFO]   Fri Jan 16 09:16:22 2009   Above message repeated 2 times
[INFO]   Fri Jan 16 09:13:34 2009   Blocked incoming UDP packet from 125.28.159.137:39893 to 99.252.46.163:41224
[WARN]   Fri Jan 16 09:12:46 2009   A network computer (DAVID) was assigned the IP address of 192.168.0.197.
[INFO]   Fri Jan 16 09:11:37 2009   Blocked incoming UDP packet from 94.122.221.200:18372 to 99.252.46.163:41224
[INFO]   Fri Jan 16 09:05:42 2009   Blocked incoming TCP connection request from 78.182.221.210:4805 to 99.252.46.163:12500
[INFO]   Fri Jan 16 09:05:33 2009   Above message repeated 2 times
[INFO]   Fri Jan 16 09:01:54 2009   Blocked incoming TCP connection request from 90.200.164.71:1721 to 99.252.46.163:12500
[INFO]   Fri Jan 16 09:01:45 2009   Above message repeated 2 times
[INFO]   Fri Jan 16 09:01:04 2009   Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 119.42.149.27
[INFO]   Fri Jan 16 09:00:05 2009   Above message repeated 2 times

[EddieZ]

I don't see any de-authentifications or disconnections in the log you psted.... I could be the connection (with the connected device) is put 'to sleep' and when it awakes receives authentification.

Are they there in your logs (de-authentification/disconnects)?

[biker]

I don't see any de-authentification/disconnects that I can see.
I did update the software to 1.21 and the same still happens.
I get a warning screen saying: suns - disconnected and after a short or longer time (no set time as to lenght) it comes back on. This happens when it feels like it and when it wants.

[EddieZ]

"Suns", "I don't see any de-authentification/disconnects that I can see."

To be honest, I don't understand what you mean. And what warning screen, from which application?

[biker]

Thanks for all the help, but you cannot legislate against stupidity.
Stupid mistakes come with all installs. I was plugged into a power bar instead of directly into the wall and told it would probably work, the first thing to change when things don't go to plan.
Things work as to plan now so thanks again for your help in trying to save me from my self.
biker

[Lycan]