Strange errors in my D-Link DI-634M router log today

Hi.

I have a D-Link DI-634M router.

While in my log today I noticed tons of errors, but everything is working
perfectly.

I'm getting this every 3 to 7 seconds from 3 different IP addresses:

Dropped packet from 169.254.1.82 to 169.254.1.255 that was received from the
wrong network interface (IP address spoofing)

The 3 IP addresses are 169.254.1.146, 169.254.1.82, and 169.254.1.188.

A call to D-Link suggested someone was accessing my router such as a
neighbor. I don't think that's correct. I have WEP encryption set on all my
devices, with a password none one could guess. I changed my SSID to
something no one would guess. I have SSID broadcast disabled, and I use MAC
filtering to only allow devices I've put in the router.

I did have FIOS TV installed the other day and they installed a Motorola
NIM100 (Network Interface Module) in my home near the router. I'm new to
this and can't find a manual for it.

I'm a bit lost when it comes to it's MAC address and IP stuff. The bottom of
the NIM100 has a HFC MAC ID that ends in 87 and also says cLINK MAC ID and
ends in 88. Does this mean it has two MAC addresses? Should I have both in
my MAC filter list?

When I added both of those to my MAC filters in my router setup (and
temporarly disabled MAC filters) I noticed my DHPC server assigned 3 IP's to
my STBs (Set Top Boxes), so I wrote down those and added them to my MAC
filters section to be safe and re-enabled MAC filtering.

After all that stuff everything seemed to work fine. I was NOT seeing any of
these strange errors in my router log.

The only reason I even looked in the log yesterday was because our Xbox Live
connection dropped at noon and I was trying to look for errors in the log. I
then noticed the new errors.

So my point is I'm thinking these errors probably don't have anything to do
with my new NIM100, but i'm not certain. I'm so new to networking that I
understand VERY little.

I'm a bit nervous about calling FIOS since they do NOT want people using
their own routers even though many online say they do just fine.

I'm so lost and feel that D-Link support was 'blowing me off'. It was
suggested initially that my network was unsecure and he lead me through
securing it, to which HE found out it WAS already secure.

Help.

I'm lost.

Don


p.s. Pardon the multiple posts. I'm not sure what newsgroup to ask for
help in.

Hi.

Just to clarify, it HAS to be a wireless device causing the problem, or
could it be a wired connected device causing the problem?

Don


"Diamontina Cocktail" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> "Don Naegele" <(E-Mail Removed)> wrote in message
> news:h_Fwg.5734$yN3.2828@trnddc04...
>> Hi.
>>
>> I have a D-Link DI-634M router.
>>
>> While in my log today I noticed tons of errors, but everything is working
>> perfectly.
>>
>> I'm getting this every 3 to 7 seconds from 3 different IP addresses:
>>
>> Dropped packet from 169.254.1.82 to 169.254.1.255 that was received from
>> the
>> wrong network interface (IP address spoofing)
>>
>
> No it isnt. That is just a wi-fi NIC somewhere (yours or someone else's)
> not getting an IP asigned but nevertheless connecting to your wireless
> signal if not your actual internet or network.
>
>> The 3 IP addresses are 169.254.1.146, 169.254.1.82, and 169.254.1.188.
>>
>> A call to D-Link suggested someone was accessing my router such as a
>> neighbor. I don't think that's correct. I have WEP encryption set on all
>> my
>> devices, with a password none one could guess. I changed my SSID to
>> something no one would guess. I have SSID broadcast disabled, and I use
>> MAC
>> filtering to only allow devices I've put in the router.
>
> It IS possibly correct but it can be one of your own wi-fi NICs too.
>
>
>

without more info it could be anything connected to your network either
wired or wireless. are all 3 of them sending to the network broadcast
address (.255)?? that block of numbers should not be routable on the
internet, so it has to be local to your network. that block is also what
windows (and other) machines randomly pick from when they can't get an
address via dhcp, so its likely a machine trying to get an ip address and
failing. what ip range does your router serve? which interface does the
router say these are coming in from?? have you tried unplugging or turning
off each of your devices to see if they go away?

by the way, as long as your network is active the ssid will be visible to
anyone monitoring. turning off broadcasting just keeps it from being sent
when there is no network traffic.

"Don Naegele" <(E-Mail Removed)> wrote in message
news:C5Owg.11898$aW2.8756@trnddc03...
> Hi.
>
> Just to clarify, it HAS to be a wireless device causing the problem, or
> could it be a wired connected device causing the problem?
>
> Don
>
>
> "Diamontina Cocktail" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>
>> "Don Naegele" <(E-Mail Removed)> wrote in message
>> news:h_Fwg.5734$yN3.2828@trnddc04...
>>> Hi.
>>>
>>> I have a D-Link DI-634M router.
>>>
>>> While in my log today I noticed tons of errors, but everything is
>>> working
>>> perfectly.
>>>
>>> I'm getting this every 3 to 7 seconds from 3 different IP addresses:
>>>
>>> Dropped packet from 169.254.1.82 to 169.254.1.255 that was received from
>>> the
>>> wrong network interface (IP address spoofing)
>>>
>>
>> No it isnt. That is just a wi-fi NIC somewhere (yours or someone else's)
>> not getting an IP asigned but nevertheless connecting to your wireless
>> signal if not your actual internet or network.
>>
>>> The 3 IP addresses are 169.254.1.146, 169.254.1.82, and 169.254.1.188.
>>>
>>> A call to D-Link suggested someone was accessing my router such as a
>>> neighbor. I don't think that's correct. I have WEP encryption set on all
>>> my
>>> devices, with a password none one could guess. I changed my SSID to
>>> something no one would guess. I have SSID broadcast disabled, and I use
>>> MAC
>>> filtering to only allow devices I've put in the router.
>>
>> It IS possibly correct but it can be one of your own wi-fi NICs too.
>>
>>
>>
>
>

Hi.

I have my DHCP IP Address Range set from 192.168.0.2 to .99. Is that what
you're talking about? I'm so lost on this stuff.

I'm not sure what you mean by 'which interface does the router say these are
coming from'. This is all I get from the log:

[INFO] Sun Jul 23 15:38:49 2006 Dropped packet from 169.254.1.82 to
169.254.1.255 that was received from the wrong network interface (IP address
spoofing)

I've not tried unplugging or turning off each device one at a time, but
that's a good idea. Thanks for the suggestion.

Don




"Dave" <(E-Mail Removed)> wrote in message
news:er5$(E-Mail Removed)...
> without more info it could be anything connected to your network either
> wired or wireless. are all 3 of them sending to the network broadcast
> address (.255)?? that block of numbers should not be routable on the
> internet, so it has to be local to your network. that block is also what
> windows (and other) machines randomly pick from when they can't get an
> address via dhcp, so its likely a machine trying to get an ip address and
> failing. what ip range does your router serve? which interface does the
> router say these are coming in from?? have you tried unplugging or
> turning off each of your devices to see if they go away?
>
> by the way, as long as your network is active the ssid will be visible to
> anyone monitoring. turning off broadcasting just keeps it from being sent
> when there is no network traffic.
>
> "Don Naegele" <(E-Mail Removed)> wrote in message
> news:C5Owg.11898$aW2.8756@trnddc03...
>> Hi.
>>
>> Just to clarify, it HAS to be a wireless device causing the problem, or
>> could it be a wired connected device causing the problem?
>>
>> Don
>>
>>
>> "Diamontina Cocktail" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>>
>>> "Don Naegele" <(E-Mail Removed)> wrote in message
>>> news:h_Fwg.5734$yN3.2828@trnddc04...
>>>> Hi.
>>>>
>>>> I have a D-Link DI-634M router.
>>>>
>>>> While in my log today I noticed tons of errors, but everything is
>>>> working
>>>> perfectly.
>>>>
>>>> I'm getting this every 3 to 7 seconds from 3 different IP addresses:
>>>>
>>>> Dropped packet from 169.254.1.82 to 169.254.1.255 that was received
>>>> from the
>>>> wrong network interface (IP address spoofing)
>>>>
>>>
>>> No it isnt. That is just a wi-fi NIC somewhere (yours or someone else's)
>>> not getting an IP asigned but nevertheless connecting to your wireless
>>> signal if not your actual internet or network.
>>>
>>>> The 3 IP addresses are 169.254.1.146, 169.254.1.82, and 169.254.1.188.
>>>>
>>>> A call to D-Link suggested someone was accessing my router such as a
>>>> neighbor. I don't think that's correct. I have WEP encryption set on
>>>> all my
>>>> devices, with a password none one could guess. I changed my SSID to
>>>> something no one would guess. I have SSID broadcast disabled, and I use
>>>> MAC
>>>> filtering to only allow devices I've put in the router.
>>>
>>> It IS possibly correct but it can be one of your own wi-fi NICs too.
>>>
>>>
>>>
>>
>>
>
>

Hi again.

Just for fun I unplugged the new NIM100 and rebooted the router. The error
messages stopped.

I then plugged in the NIM100 and the error messages started again.

So it has something to do with my new NIM100. I cannot find any manual on
it online anywhere.

I have a feeling calling Verizon to ask what the error message is for is
going to result in them commenting that I need to use their VDI-624 crappy
router that messes up our Xbox connection and is slow.

Don


"Don Naegele" <(E-Mail Removed)> wrote in message
news:dgQwg.8092$6G3.4107@trnddc05...
> Hi.
>
> I have my DHCP IP Address Range set from 192.168.0.2 to .99. Is that what
> you're talking about? I'm so lost on this stuff.
>
> I'm not sure what you mean by 'which interface does the router say these
> are coming from'. This is all I get from the log:
>
> [INFO] Sun Jul 23 15:38:49 2006 Dropped packet from 169.254.1.82 to
> 169.254.1.255 that was received from the wrong network interface (IP
> address spoofing)
>
> I've not tried unplugging or turning off each device one at a time, but
> that's a good idea. Thanks for the suggestion.
>
> Don
>
>
>
>
> "Dave" <(E-Mail Removed)> wrote in message
> news:er5$(E-Mail Removed)...
>> without more info it could be anything connected to your network either
>> wired or wireless. are all 3 of them sending to the network broadcast
>> address (.255)?? that block of numbers should not be routable on the
>> internet, so it has to be local to your network. that block is also what
>> windows (and other) machines randomly pick from when they can't get an
>> address via dhcp, so its likely a machine trying to get an ip address and
>> failing. what ip range does your router serve? which interface does the
>> router say these are coming in from?? have you tried unplugging or
>> turning off each of your devices to see if they go away?
>>
>> by the way, as long as your network is active the ssid will be visible to
>> anyone monitoring. turning off broadcasting just keeps it from being
>> sent when there is no network traffic.
>>
>> "Don Naegele" <(E-Mail Removed)> wrote in message
>> news:C5Owg.11898$aW2.8756@trnddc03...
>>> Hi.
>>>
>>> Just to clarify, it HAS to be a wireless device causing the problem, or
>>> could it be a wired connected device causing the problem?
>>>
>>> Don
>>>
>>>
>>> "Diamontina Cocktail" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>>
>>>> "Don Naegele" <(E-Mail Removed)> wrote in message
>>>> news:h_Fwg.5734$yN3.2828@trnddc04...
>>>>> Hi.
>>>>>
>>>>> I have a D-Link DI-634M router.
>>>>>
>>>>> While in my log today I noticed tons of errors, but everything is
>>>>> working
>>>>> perfectly.
>>>>>
>>>>> I'm getting this every 3 to 7 seconds from 3 different IP addresses:
>>>>>
>>>>> Dropped packet from 169.254.1.82 to 169.254.1.255 that was received
>>>>> from the
>>>>> wrong network interface (IP address spoofing)
>>>>>
>>>>
>>>> No it isnt. That is just a wi-fi NIC somewhere (yours or someone
>>>> else's) not getting an IP asigned but nevertheless connecting to your
>>>> wireless signal if not your actual internet or network.
>>>>
>>>>> The 3 IP addresses are 169.254.1.146, 169.254.1.82, and 169.254.1.188.
>>>>>
>>>>> A call to D-Link suggested someone was accessing my router such as a
>>>>> neighbor. I don't think that's correct. I have WEP encryption set on
>>>>> all my
>>>>> devices, with a password none one could guess. I changed my SSID to
>>>>> something no one would guess. I have SSID broadcast disabled, and I
>>>>> use MAC
>>>>> filtering to only allow devices I've put in the router.
>>>>
>>>> It IS possibly correct but it can be one of your own wi-fi NICs too.
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

i have no idea what that is, but keep looking, there must be something for
it. meanwhile, what it would sound like is that its trying to find
something in the right ip address range to talk to. when you send to .255
that is considered a broadcast for that 169.254.1.* address block. that is
the type of thing devices that need to phone home for configuration
information, but don't know the address do. so maybe there was a
configuration step you missed, or something else that needed to be installed
for it to talk to.

"Don Naegele" <(E-Mail Removed)> wrote in message
news:VlQwg.6018$yN3.3307@trnddc04...
> Hi again.
>
> Just for fun I unplugged the new NIM100 and rebooted the router. The
> error messages stopped.
>
> I then plugged in the NIM100 and the error messages started again.
>
> So it has something to do with my new NIM100. I cannot find any manual on
> it online anywhere.
>
> I have a feeling calling Verizon to ask what the error message is for is
> going to result in them commenting that I need to use their VDI-624 crappy
> router that messes up our Xbox connection and is slow.
>
> Don
>
>
> "Don Naegele" <(E-Mail Removed)> wrote in message
> news:dgQwg.8092$6G3.4107@trnddc05...
>> Hi.
>>
>> I have my DHCP IP Address Range set from 192.168.0.2 to .99. Is that
>> what you're talking about? I'm so lost on this stuff.
>>
>> I'm not sure what you mean by 'which interface does the router say these
>> are coming from'. This is all I get from the log:
>>
>> [INFO] Sun Jul 23 15:38:49 2006 Dropped packet from 169.254.1.82 to
>> 169.254.1.255 that was received from the wrong network interface (IP
>> address spoofing)
>>
>> I've not tried unplugging or turning off each device one at a time, but
>> that's a good idea. Thanks for the suggestion.
>>
>> Don
>>
>>
>>
>>
>> "Dave" <(E-Mail Removed)> wrote in message
>> news:er5$(E-Mail Removed)...
>>> without more info it could be anything connected to your network either
>>> wired or wireless. are all 3 of them sending to the network broadcast
>>> address (.255)?? that block of numbers should not be routable on the
>>> internet, so it has to be local to your network. that block is also
>>> what windows (and other) machines randomly pick from when they can't get
>>> an address via dhcp, so its likely a machine trying to get an ip address
>>> and failing. what ip range does your router serve? which interface
>>> does the router say these are coming in from?? have you tried
>>> unplugging or turning off each of your devices to see if they go away?
>>>
>>> by the way, as long as your network is active the ssid will be visible
>>> to anyone monitoring. turning off broadcasting just keeps it from being
>>> sent when there is no network traffic.
>>>
>>> "Don Naegele" <(E-Mail Removed)> wrote in message
>>> news:C5Owg.11898$aW2.8756@trnddc03...
>>>> Hi.
>>>>
>>>> Just to clarify, it HAS to be a wireless device causing the problem, or
>>>> could it be a wired connected device causing the problem?
>>>>
>>>> Don
>>>>
>>>>
>>>> "Diamontina Cocktail" <(E-Mail Removed)> wrote in message
>>>> news:(E-Mail Removed)...
>>>>>
>>>>> "Don Naegele" <(E-Mail Removed)> wrote in message
>>>>> news:h_Fwg.5734$yN3.2828@trnddc04...
>>>>>> Hi.
>>>>>>
>>>>>> I have a D-Link DI-634M router.
>>>>>>
>>>>>> While in my log today I noticed tons of errors, but everything is
>>>>>> working
>>>>>> perfectly.
>>>>>>
>>>>>> I'm getting this every 3 to 7 seconds from 3 different IP addresses:
>>>>>>
>>>>>> Dropped packet from 169.254.1.82 to 169.254.1.255 that was received
>>>>>> from the
>>>>>> wrong network interface (IP address spoofing)
>>>>>>
>>>>>
>>>>> No it isnt. That is just a wi-fi NIC somewhere (yours or someone
>>>>> else's) not getting an IP asigned but nevertheless connecting to your
>>>>> wireless signal if not your actual internet or network.
>>>>>
>>>>>> The 3 IP addresses are 169.254.1.146, 169.254.1.82, and
>>>>>> 169.254.1.188.
>>>>>>
>>>>>> A call to D-Link suggested someone was accessing my router such as a
>>>>>> neighbor. I don't think that's correct. I have WEP encryption set on
>>>>>> all my
>>>>>> devices, with a password none one could guess. I changed my SSID to
>>>>>> something no one would guess. I have SSID broadcast disabled, and I
>>>>>> use MAC
>>>>>> filtering to only allow devices I've put in the router.
>>>>>
>>>>> It IS possibly correct but it can be one of your own wi-fi NICs too.
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Hi.

Why does pulling the WIRED Motorola NIM100 from the system stop all errors
then?

I'm so lost.

Everyone is saying it must a wireless device causing the problem.

Is it possible that when I reconnect the NIM100 then the THREE Set Top Boxes
are causing the problem? They are not 'hard wired' into my router, but one
STB is connected COAX to the NIM100. And I'm get three errors with three IP
addresses in the errors.

Maybe I should disconnect all 3 STBS's one at a time and reboot and see if
connecting them one at a time starting errors coming in one at a time?

Thoughts?

Don


"Diamontina Cocktail" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> "Don Naegele" <(E-Mail Removed)> wrote in message
> news:dgQwg.8092$6G3.4107@trnddc05...
>> Hi.
>>
>> I have my DHCP IP Address Range set from 192.168.0.2 to .99. Is that
>> what you're talking about? I'm so lost on this stuff.
>>
>> I'm not sure what you mean by 'which interface does the router say these
>> are coming from'. This is all I get from the log:
>>
>> [INFO] Sun Jul 23 15:38:49 2006 Dropped packet from 169.254.1.82 to
>> 169.254.1.255 that was received from the wrong network interface (IP
>> address spoofing)
>>
>> I've not tried unplugging or turning off each device one at a time, but
>> that's a good idea. Thanks for the suggestion.
>>
>
> Just to clarify, this can NOT in ANY way, be a WIRED NIC in your case,
> only wireless or wi-fi if you like.
>
> There is a NIC in range somewhere that is connecting to your SSID on your
> router but not to Internet or your network. It is NOT being supplied with
> an IP number from your DHCP server (assuming you have one turned on) and
> is thus giving itself a standard number for a wi-fi NIC that isn't being
> supplied a number.
>
> There is one simple way to check which NIC is causing it. You know which
> ones are working getting internet or your network so discount all of those
> at first. Now look at the ones that are left. Close any log report you may
> be viewing now go to one of those wi-fi NICs you think AREN'T connected
> (did you say Playstation or something like that before? In any case, one
> of those) and turn it completely off so that it cant attempt to connect to
> anything. Go back to your logs and see if it is still attempting to
> connect. If not, then that was the problem and if more connect attempts
> are coming in, shut down the log viewing you have up, go to the next one
> while leaving the first off, turn IT off and come back and open the logs
> again. Is it fixed? Do this for every wi-fi device you have in range that
> you KNOW isn't connected. One thing to remember is that some routers don't
> do anything more than fill up the log page and don't put anything newer in
> the logs. If this is the case with yours, you may have to clear the logs
> after looking at them so more lines can be written.
>
> Another much simpler alternative is to go to where "DHCP" is in your
> router and turn it ON if it is currently off (which it sounds like it is)
> and see if the problem resolves itself. This DOES mean, though, that if
> someone outside your premises is trying to connect to you, they will if
> they know the WEP key or whatever you have set up for encryption.
>
> Did you manually assign IP and DNS to your computers that are OK on your
> router? If so, another way to fix this is to go to those kiddy consoles
> you mentioned and assign an IP to them within the range the router allows
> and of course set up encryption. If the problem goes away, you have fixed
> it.
>
> Other than that, if you are not seeing a connect by the other IP numbers,
> why is it a problem? They aren't actually doing anything of note if they
> cant connect.
>
>

Hi again.

I did some testing.

I kept the NIM100 connected, but then disconnected all 3 STBs. No errors.

I then reconnected the first STB and was getting one error with an IP ending
in .82.

I then reconnected the second STB and was getting two errors. The first
with .82 and now the 2nd adds .146.

I then reconnected the third STB and was getting three errors. This adds
..188 to my list of error IPs.

So it appears that the STBs are causing the errors.

I have alreading included the STBs in my MAC filter, and I have also
assigned all 3 STBs their own IP address in my DHCP Reservation List.

Any further suggestions?

Don



"Don Naegele" <(E-Mail Removed)> wrote in message
news:4h0xg.8384$6G3.6121@trnddc05...
> Hi.
>
> Why does pulling the WIRED Motorola NIM100 from the system stop all errors
> then?
>
> I'm so lost.
>
> Everyone is saying it must a wireless device causing the problem.
>
> Is it possible that when I reconnect the NIM100 then the THREE Set Top
> Boxes are causing the problem? They are not 'hard wired' into my router,
> but one STB is connected COAX to the NIM100. And I'm get three errors
> with three IP addresses in the errors.
>
> Maybe I should disconnect all 3 STBS's one at a time and reboot and see if
> connecting them one at a time starting errors coming in one at a time?
>
> Thoughts?
>
> Don
>
>
> "Diamontina Cocktail" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>
>> "Don Naegele" <(E-Mail Removed)> wrote in message
>> news:dgQwg.8092$6G3.4107@trnddc05...
>>> Hi.
>>>
>>> I have my DHCP IP Address Range set from 192.168.0.2 to .99. Is that
>>> what you're talking about? I'm so lost on this stuff.
>>>
>>> I'm not sure what you mean by 'which interface does the router say these
>>> are coming from'. This is all I get from the log:
>>>
>>> [INFO] Sun Jul 23 15:38:49 2006 Dropped packet from 169.254.1.82 to
>>> 169.254.1.255 that was received from the wrong network interface (IP
>>> address spoofing)
>>>
>>> I've not tried unplugging or turning off each device one at a time, but
>>> that's a good idea. Thanks for the suggestion.
>>>
>>
>> Just to clarify, this can NOT in ANY way, be a WIRED NIC in your case,
>> only wireless or wi-fi if you like.
>>
>> There is a NIC in range somewhere that is connecting to your SSID on your
>> router but not to Internet or your network. It is NOT being supplied with
>> an IP number from your DHCP server (assuming you have one turned on) and
>> is thus giving itself a standard number for a wi-fi NIC that isn't being
>> supplied a number.
>>
>> There is one simple way to check which NIC is causing it. You know which
>> ones are working getting internet or your network so discount all of
>> those at first. Now look at the ones that are left. Close any log report
>> you may be viewing now go to one of those wi-fi NICs you think AREN'T
>> connected (did you say Playstation or something like that before? In any
>> case, one of those) and turn it completely off so that it cant attempt to
>> connect to anything. Go back to your logs and see if it is still
>> attempting to connect. If not, then that was the problem and if more
>> connect attempts are coming in, shut down the log viewing you have up, go
>> to the next one while leaving the first off, turn IT off and come back
>> and open the logs again. Is it fixed? Do this for every wi-fi device you
>> have in range that you KNOW isn't connected. One thing to remember is
>> that some routers don't do anything more than fill up the log page and
>> don't put anything newer in the logs. If this is the case with yours, you
>> may have to clear the logs after looking at them so more lines can be
>> written.
>>
>> Another much simpler alternative is to go to where "DHCP" is in your
>> router and turn it ON if it is currently off (which it sounds like it is)
>> and see if the problem resolves itself. This DOES mean, though, that if
>> someone outside your premises is trying to connect to you, they will if
>> they know the WEP key or whatever you have set up for encryption.
>>
>> Did you manually assign IP and DNS to your computers that are OK on your
>> router? If so, another way to fix this is to go to those kiddy consoles
>> you mentioned and assign an IP to them within the range the router allows
>> and of course set up encryption. If the problem goes away, you have fixed
>> it.
>>
>> Other than that, if you are not seeing a connect by the other IP numbers,
>> why is it a problem? They aren't actually doing anything of note if they
>> cant connect.
>>
>>
>
>

the 169... ip address means they are not getting addresses from your dhcp
server and are picking those numbers for themselves. the router complains
because those are not in the range of addresses it is expecting. so you
have to figure out how to configure your router, the nim100 (whatever that
is), or the stb's (whatever they may be), or all 3, in such a way that they
all get proper ip addresses.

"Don Naegele" <(E-Mail Removed)> wrote in message
news:rY0xg.6658$yN3.2226@trnddc04...
> Hi again.
>
> I did some testing.
>
> I kept the NIM100 connected, but then disconnected all 3 STBs. No errors.
>
> I then reconnected the first STB and was getting one error with an IP
> ending in .82.
>
> I then reconnected the second STB and was getting two errors. The first
> with .82 and now the 2nd adds .146.
>
> I then reconnected the third STB and was getting three errors. This adds
> .188 to my list of error IPs.
>
> So it appears that the STBs are causing the errors.
>
> I have alreading included the STBs in my MAC filter, and I have also
> assigned all 3 STBs their own IP address in my DHCP Reservation List.
>
> Any further suggestions?
>
> Don
>
>
>
> "Don Naegele" <(E-Mail Removed)> wrote in message
> news:4h0xg.8384$6G3.6121@trnddc05...
>> Hi.
>>
>> Why does pulling the WIRED Motorola NIM100 from the system stop all
>> errors then?
>>
>> I'm so lost.
>>
>> Everyone is saying it must a wireless device causing the problem.
>>
>> Is it possible that when I reconnect the NIM100 then the THREE Set Top
>> Boxes are causing the problem? They are not 'hard wired' into my router,
>> but one STB is connected COAX to the NIM100. And I'm get three errors
>> with three IP addresses in the errors.
>>
>> Maybe I should disconnect all 3 STBS's one at a time and reboot and see
>> if connecting them one at a time starting errors coming in one at a time?
>>
>> Thoughts?
>>
>> Don
>>
>>
>> "Diamontina Cocktail" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>>
>>> "Don Naegele" <(E-Mail Removed)> wrote in message
>>> news:dgQwg.8092$6G3.4107@trnddc05...
>>>> Hi.
>>>>
>>>> I have my DHCP IP Address Range set from 192.168.0.2 to .99. Is that
>>>> what you're talking about? I'm so lost on this stuff.
>>>>
>>>> I'm not sure what you mean by 'which interface does the router say
>>>> these are coming from'. This is all I get from the log:
>>>>
>>>> [INFO] Sun Jul 23 15:38:49 2006 Dropped packet from 169.254.1.82 to
>>>> 169.254.1.255 that was received from the wrong network interface (IP
>>>> address spoofing)
>>>>
>>>> I've not tried unplugging or turning off each device one at a time, but
>>>> that's a good idea. Thanks for the suggestion.
>>>>
>>>
>>> Just to clarify, this can NOT in ANY way, be a WIRED NIC in your case,
>>> only wireless or wi-fi if you like.
>>>
>>> There is a NIC in range somewhere that is connecting to your SSID on
>>> your router but not to Internet or your network. It is NOT being
>>> supplied with an IP number from your DHCP server (assuming you have one
>>> turned on) and is thus giving itself a standard number for a wi-fi NIC
>>> that isn't being supplied a number.
>>>
>>> There is one simple way to check which NIC is causing it. You know which
>>> ones are working getting internet or your network so discount all of
>>> those at first. Now look at the ones that are left. Close any log report
>>> you may be viewing now go to one of those wi-fi NICs you think AREN'T
>>> connected (did you say Playstation or something like that before? In any
>>> case, one of those) and turn it completely off so that it cant attempt
>>> to connect to anything. Go back to your logs and see if it is still
>>> attempting to connect. If not, then that was the problem and if more
>>> connect attempts are coming in, shut down the log viewing you have up,
>>> go to the next one while leaving the first off, turn IT off and come
>>> back and open the logs again. Is it fixed? Do this for every wi-fi
>>> device you have in range that you KNOW isn't connected. One thing to
>>> remember is that some routers don't do anything more than fill up the
>>> log page and don't put anything newer in the logs. If this is the case
>>> with yours, you may have to clear the logs after looking at them so more
>>> lines can be written.
>>>
>>> Another much simpler alternative is to go to where "DHCP" is in your
>>> router and turn it ON if it is currently off (which it sounds like it
>>> is) and see if the problem resolves itself. This DOES mean, though, that
>>> if someone outside your premises is trying to connect to you, they will
>>> if they know the WEP key or whatever you have set up for encryption.
>>>
>>> Did you manually assign IP and DNS to your computers that are OK on your
>>> router? If so, another way to fix this is to go to those kiddy consoles
>>> you mentioned and assign an IP to them within the range the router
>>> allows and of course set up encryption. If the problem goes away, you
>>> have fixed it.
>>>
>>> Other than that, if you are not seeing a connect by the other IP
>>> numbers, why is it a problem? They aren't actually doing anything of
>>> note if they cant connect.
>>>
>>>
>>
>>
>
>

Yeah. I'll need lots of luck then.

Thanks for all your help, though.

Don


"Dave" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> the 169... ip address means they are not getting addresses from your dhcp
> server and are picking those numbers for themselves. the router complains
> because those are not in the range of addresses it is expecting. so you
> have to figure out how to configure your router, the nim100 (whatever that
> is), or the stb's (whatever they may be), or all 3, in such a way that
> they all get proper ip addresses.
>
> "Don Naegele" <(E-Mail Removed)> wrote in message
> news:rY0xg.6658$yN3.2226@trnddc04...
>> Hi again.
>>
>> I did some testing.
>>
>> I kept the NIM100 connected, but then disconnected all 3 STBs. No
>> errors.
>>
>> I then reconnected the first STB and was getting one error with an IP
>> ending in .82.
>>
>> I then reconnected the second STB and was getting two errors. The first
>> with .82 and now the 2nd adds .146.
>>
>> I then reconnected the third STB and was getting three errors. This adds
>> .188 to my list of error IPs.
>>
>> So it appears that the STBs are causing the errors.
>>
>> I have alreading included the STBs in my MAC filter, and I have also
>> assigned all 3 STBs their own IP address in my DHCP Reservation List.
>>
>> Any further suggestions?
>>
>> Don
>>
>>
>>
>> "Don Naegele" <(E-Mail Removed)> wrote in message
>> news:4h0xg.8384$6G3.6121@trnddc05...
>>> Hi.
>>>
>>> Why does pulling the WIRED Motorola NIM100 from the system stop all
>>> errors then?
>>>
>>> I'm so lost.
>>>
>>> Everyone is saying it must a wireless device causing the problem.
>>>
>>> Is it possible that when I reconnect the NIM100 then the THREE Set Top
>>> Boxes are causing the problem? They are not 'hard wired' into my
>>> router, but one STB is connected COAX to the NIM100. And I'm get three
>>> errors with three IP addresses in the errors.
>>>
>>> Maybe I should disconnect all 3 STBS's one at a time and reboot and see
>>> if connecting them one at a time starting errors coming in one at a
>>> time?
>>>
>>> Thoughts?
>>>
>>> Don
>>>
>>>
>>> "Diamontina Cocktail" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>>
>>>> "Don Naegele" <(E-Mail Removed)> wrote in message
>>>> news:dgQwg.8092$6G3.4107@trnddc05...
>>>>> Hi.
>>>>>
>>>>> I have my DHCP IP Address Range set from 192.168.0.2 to .99. Is that
>>>>> what you're talking about? I'm so lost on this stuff.
>>>>>
>>>>> I'm not sure what you mean by 'which interface does the router say
>>>>> these are coming from'. This is all I get from the log:
>>>>>
>>>>> [INFO] Sun Jul 23 15:38:49 2006 Dropped packet from 169.254.1.82 to
>>>>> 169.254.1.255 that was received from the wrong network interface (IP
>>>>> address spoofing)
>>>>>
>>>>> I've not tried unplugging or turning off each device one at a time,
>>>>> but that's a good idea. Thanks for the suggestion.
>>>>>
>>>>
>>>> Just to clarify, this can NOT in ANY way, be a WIRED NIC in your case,
>>>> only wireless or wi-fi if you like.
>>>>
>>>> There is a NIC in range somewhere that is connecting to your SSID on
>>>> your router but not to Internet or your network. It is NOT being
>>>> supplied with an IP number from your DHCP server (assuming you have one
>>>> turned on) and is thus giving itself a standard number for a wi-fi NIC
>>>> that isn't being supplied a number.
>>>>
>>>> There is one simple way to check which NIC is causing it. You know
>>>> which ones are working getting internet or your network so discount all
>>>> of those at first. Now look at the ones that are left. Close any log
>>>> report you may be viewing now go to one of those wi-fi NICs you think
>>>> AREN'T connected (did you say Playstation or something like that
>>>> before? In any case, one of those) and turn it completely off so that
>>>> it cant attempt to connect to anything. Go back to your logs and see if
>>>> it is still attempting to connect. If not, then that was the problem
>>>> and if more connect attempts are coming in, shut down the log viewing
>>>> you have up, go to the next one while leaving the first off, turn IT
>>>> off and come back and open the logs again. Is it fixed? Do this for
>>>> every wi-fi device you have in range that you KNOW isn't connected. One
>>>> thing to remember is that some routers don't do anything more than fill
>>>> up the log page and don't put anything newer in the logs. If this is
>>>> the case with yours, you may have to clear the logs after looking at
>>>> them so more lines can be written.
>>>>
>>>> Another much simpler alternative is to go to where "DHCP" is in your
>>>> router and turn it ON if it is currently off (which it sounds like it
>>>> is) and see if the problem resolves itself. This DOES mean, though,
>>>> that if someone outside your premises is trying to connect to you, they
>>>> will if they know the WEP key or whatever you have set up for
>>>> encryption.
>>>>
>>>> Did you manually assign IP and DNS to your computers that are OK on
>>>> your router? If so, another way to fix this is to go to those kiddy
>>>> consoles you mentioned and assign an IP to them within the range the
>>>> router allows and of course set up encryption. If the problem goes
>>>> away, you have fixed it.
>>>>
>>>> Other than that, if you are not seeing a connect by the other IP
>>>> numbers, why is it a problem? They aren't actually doing anything of
>>>> note if they cant connect.
>>>>
>>>>
>>>
>>>
>>
>>
>
>