5:37 p.m.
I am receiving The following error messages every 30 seconds in
/var/log/messages:
avahi-daemon[1029]: Received response from host 192.168.7.1 with invalid
source port 32783 on interface 'eth0.0'
I looked on the internet and found a blog with the same problem:
http://homecommunity.cisco.com/t5/Wireless-Routers/Received-response-from...
I went to CISCO to determine what the resolution was.
1. Live Chat support informed me that Linksys was only supported under
Windows and that I could call live support at 1-800-326-7114.
2. Live support made be perform rather silly tests under Windows. Then
passed me to a supervisor.
3. The Supervisor could not find the above email thread on their own site!
Linksys does not have an email address for support. And the people I
spoke to were not savvy enough to understand the problem as described in
the above thread.
Is Linksys a known problem for Linux systems? Should it be?
Are there any suggestions on how to bound the size of my message files
other that editing avhi so that it does not issue these warning messages?
I was online or on the phone to Linksys for over 3 hours. I do not know
where they are located, but I could barely understand their english. It
was one of the worst support experiences in my 35 years of system
involvement!
Don
7:24 p.m.
Cisco won't support Linux? Maybe we could crowdsource a response that would change
their minds?
But for a solution: is your router otherwise working? Because if so, one quick iptables
statement will block the nasty packet. I'm not at my desk, or I'd suggest one --
any iptables types reading this?
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
7:27 p.m.
On Sat, Feb 4, 2012 at 4:37 PM, don fisher <hdf3(a)comcast.net> wrote:
I am receiving The following error messages every 30 seconds in
/var/log/messages:
avahi-daemon[1029]: Received response from host 192.168.7.1 with invalid
source port 32783 on interface 'eth0.0'
I looked on the internet and found a blog with the same problem:
http://homecommunity.cisco.com/t5/Wireless-Routers/Received-response-from...
I went to CISCO to determine what the resolution was.
1. Live Chat support informed me that Linksys was only supported under
Windows and that I could call live support at 1-800-326-7114.
2. Live support made be perform rather silly tests under Windows. Then
passed me to a supervisor.
3. The Supervisor could not find the above email thread on their own site!
Linksys does not have an email address for support. And the people I spoke
to were not savvy enough to understand the problem as described in the above
thread.
Is Linksys a known problem for Linux systems? Should it be?
Are there any suggestions on how to bound the size of my message files other
that editing avhi so that it does not issue these warning messages?
To stop Avahi from spamming syslog, copy
/lib/systemd/system/avahi-daemon.service to /etc/systemd/system. Then
edit the newly copied /etc/systemd/system/avahi-daemon.service and add
"StandardOutput=null" to the [Service] section. Finally, run
`systemctl daemon-reload && systemctl restart avahi-daemon.service` to
make the change take effect immediately.
I was online or on the phone to Linksys for over 3 hours. I do not
know
where they are located, but I could barely understand their english. It was
one of the worst support experiences in my 35 years of system involvement!
Don
-T.C.
7:10 p.m.
On 02/04/12 17:47, pringler01(a)gmail.com wrote:
i use wrt120n and i dont experiencia any problem. In this model
wrt-dd
dosent works.
ps Sorry for not following etiquette, i have only a Mobile at hand.
On Feb 4, 2012 9:25 PM, "John Wendel" <jwendel10(a)comcast.net
<mailto:jwendel10@comcast.net>> wrote:
On 02/04/2012 04:11 PM, don fisher wrote:
On 02/04/12 17:07, Paul Allen Newell wrote:
On 2/4/2012 4:04 PM, don fisher wrote:
Paul,
It is an E4200. Sorry for not mentioning it. It is
described in detail
in the link I referenced.
Don
Don:
Hopefully someone will report a success with 'N' ... or at
least a
confirm that there is something not behaving in the E4200
Paul
Paul,
Did you look at stream of emails I referenced? I took that as
confirmation of the problem. Was that a bad move? Not sure of
the etiquette here.
Don
Do you really need to use avahi? I always disable it myself, one
less thing to break.
Regards,
John
--
users mailing list
users(a)lists.fedoraproject.org <mailto:users@lists.fedoraproject.org>
To unsubscribe or change subscription options:
https://admin.fedoraproject.__org/mailman/listinfo/users
<https://admin.fedoraproject.org/mailman/listinfo/users>
Guidelines: http://fedoraproject.org/wiki/__Mailing_list_guidelines
<http://fedoraproject.org/wiki/Mailing_list_guidelines>
Have a question? Ask away: http://ask.fedoraproject.org
The problem must be specific to the E4200 or sum other subset of Linksys
routers. I was still distressed by the Windows only response from CISCO
support. On Amazon, the wrt120n is $43.95. The E4200 is $140.99. I guess
you don't get what you pay for:-)
Don
7:52 p.m.
On 02/04/12 18:27, T.C. Hollingsworth wrote:
On Sat, Feb 4, 2012 at 4:37 PM, don fisher<hdf3(a)comcast.net>
wrote:
> I am receiving The following error messages every 30 seconds in
> /var/log/messages:
>
> avahi-daemon[1029]: Received response from host 192.168.7.1 with invalid
> source port 32783 on interface 'eth0.0'
>
> I looked on the internet and found a blog with the same problem:
>
>
http://homecommunity.cisco.com/t5/Wireless-Routers/Received-response-from...
>
> I went to CISCO to determine what the resolution was.
> 1. Live Chat support informed me that Linksys was only supported under
> Windows and that I could call live support at 1-800-326-7114.
> 2. Live support made be perform rather silly tests under Windows. Then
> passed me to a supervisor.
> 3. The Supervisor could not find the above email thread on their own site!
>
> Linksys does not have an email address for support. And the people I spoke
> to were not savvy enough to understand the problem as described in the above
> thread.
>
> Is Linksys a known problem for Linux systems? Should it be?
>
> Are there any suggestions on how to bound the size of my message files other
> that editing avhi so that it does not issue these warning messages?
To stop Avahi from spamming syslog, copy
/lib/systemd/system/avahi-daemon.service to /etc/systemd/system. Then
edit the newly copied /etc/systemd/system/avahi-daemon.service and add
"StandardOutput=null" to the [Service] section. Finally, run
`systemctl daemon-reload&& systemctl restart avahi-daemon.service` to
make the change take effect immediately.
> I was online or on the phone to Linksys for over 3 hours. I do not know
> where they are located, but I could barely understand their english. It was
> one of the worst support experiences in my 35 years of system involvement!
>
> Don
-T.C.
T.C.
I think I made the changes you described. I still get the invalid source
port messages. The output from /var/log/messages and the file from
/etc/systemd/system/avahi-daemon.service are included in the attached
file. Any suggestions?
Thanks for your inputs.
Don
--
-----------------------------------------------------------------
| Don Fisher hdf3(a)comcast.net |
| 865 W. Cresta Loma Dr. VOICE: (520)888-7613 |
| Tucson, AZ. 85704-3705 |
-----------------------------------------------------------------
2:42 p.m.
On 02/06/12 12:11, T.C. Hollingsworth wrote:
On Sun, Feb 5, 2012 at 6:52 PM, don fisher<hdf3(a)comcast.net>
wrote:
> T.C.
> I think I made the changes you described. I still get the invalid source
> port messages. The output from /var/log/messages and the file from
> /etc/systemd/system/avahi-daemon.service are included in the attached file.
> Any suggestions?
Sorry, looks like Avahi writes to syslog on its own rather than using
systemd's stdout->syslog bridge. You can disable it by removing the
-s paramater from the end of the ExecStart line. Leave the
StandardOutput=null section, as Avahi will log to stdout/stderr when
-s is removed, and systemd will send that along to syslog if that line
is not present.
-T.C.
Thanks !!!!
I just rebooted and removing the -s appears to have worked:-)
Thanks again.
Don
1:11 p.m.
On Sun, Feb 5, 2012 at 6:52 PM, don fisher <hdf3(a)comcast.net> wrote:
T.C.
I think I made the changes you described. I still get the invalid source
port messages. The output from /var/log/messages and the file from
/etc/systemd/system/avahi-daemon.service are included in the attached file.
Any suggestions?
Sorry, looks like Avahi writes to syslog on its own rather than using
systemd's stdout->syslog bridge. You can disable it by removing the
-s paramater from the end of the ExecStart line. Leave the
StandardOutput=null section, as Avahi will log to stdout/stderr when
-s is removed, and systemd will send that along to syslog if that line
is not present.
-T.C.
7:40 p.m.
On 02/04/2012 07:10 PM, don fisher wrote:
The problem must be specific to the E4200 or sum other subset of
Linksys routers. I was still distressed by the Windows only response
from CISCO support. On Amazon, the wrt120n is $43.95. The E4200 is
$140.99. I guess you don't get what you pay for:-)
Don
While Cisco does own Linksys now, I wouldn't classify Linksys support as
Cisco Support. They are far from it. Cisco's support is actually pretty good
--
Larry Brower, CCENT
Fedora Ambassador - North America
Fedora Quality Assurance
lbrower(a)fedoraproject.org
http://www.fedoraproject.org/
6:47 p.m.
i use wrt120n and i dont experiencia any problem. In this model wrt-dd
dosent works.
ps Sorry for not following etiquette, i have only a Mobile at hand.
On Feb 4, 2012 9:25 PM, "John Wendel" <jwendel10(a)comcast.net> wrote:
On 02/04/2012 04:11 PM, don fisher wrote:
> On 02/04/12 17:07, Paul Allen Newell wrote:
>
>> On 2/4/2012 4:04 PM, don fisher wrote:
>>
>>> Paul,
>>>
>>> It is an E4200. Sorry for not mentioning it. It is described in detail
>>> in the link I referenced.
>>>
>>> Don
>>>
>>>
>> Don:
>>
>> Hopefully someone will report a success with 'N' ... or at least a
>> confirm that there is something not behaving in the E4200
>>
>> Paul
>>
> Paul,
>
> Did you look at stream of emails I referenced? I took that as
> confirmation of the problem. Was that a bad move? Not sure of the etiquette
> here.
>
> Don
>
>
Do you really need to use avahi? I always disable it myself, one less
thing to break.
Regards,
John
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.**org/mailman/listinfo/users<https://admin...
Guidelines:
http://fedoraproject.org/wiki/**Mailing_list_guidelines<http://fedorap...
Have a question? Ask away: http://ask.fedoraproject.org
6:25 p.m.
On 02/04/2012 04:11 PM, don fisher wrote:
On 02/04/12 17:07, Paul Allen Newell wrote:
> On 2/4/2012 4:04 PM, don fisher wrote:
>> Paul,
>>
>> It is an E4200. Sorry for not mentioning it. It is described in detail
>> in the link I referenced.
>>
>> Don
>>
>
> Don:
>
> Hopefully someone will report a success with 'N' ... or at least a
> confirm that there is something not behaving in the E4200
>
> Paul
Paul,
Did you look at stream of emails I referenced? I took that as
confirmation of the problem. Was that a bad move? Not sure of the
etiquette here.
Don
Do you really need to use avahi? I always disable it myself, one less
thing to break.
Regards,
John
6:22 p.m.
Am 05.02.2012 01:17, schrieb Paul Allen Newell:
Scanned them all. I would be inclined to agree there is a problem
based on the contents. But since Linksys takes
the stand that Linux is not part of their world, I would still hope that someone on the
list can provide a "Linux
confirm"
the linksys firmwares are crap and working mostly only with windows
i have one of this idiotic devices which needed MSIE6 and only MSEI6 for one
firmware-update and after that the WebUI worked ONLY with MSIE >=7 and no
longer with MSIE6 -> thank god virtual machines!
i would recommend HP for neraly all including network devices and
at best use BUSINESS hardware from HP not the customer crap, often
it is cheaper at all and works
6:17 p.m.
On 2/4/2012 4:11 PM, don fisher wrote:
On 02/04/12 17:07, Paul Allen Newell wrote:
> On 2/4/2012 4:04 PM, don fisher wrote:
>> Paul,
>>
>> It is an E4200. Sorry for not mentioning it. It is described in detail
>> in the link I referenced.
>>
>> Don
>>
>
> Don:
>
> Hopefully someone will report a success with 'N' ... or at least a
> confirm that there is something not behaving in the E4200
>
> Paul
Paul,
Did you look at stream of emails I referenced? I took that as
confirmation of the problem. Was that a bad move? Not sure of the
etiquette here.
Don
Don:
Scanned them all. I would be inclined to agree there is a problem based
on the contents. But since Linksys takes the stand that Linux is not
part of their world, I would still hope that someone on the list can
provide a "Linux confirm" (either "works" or "doesn't
work"). Don't
think it was a "bad move" and I certain see no etiquette issue.
It might be that particular model rather the Linksys 'N' series in general?
I do remember when dealing with Linksys that I had to lie about what I
was running and/or duplicate on a Windows box.
Paul
6:11 p.m.
On 02/04/12 17:07, Paul Allen Newell wrote:
On 2/4/2012 4:04 PM, don fisher wrote:
> Paul,
>
> It is an E4200. Sorry for not mentioning it. It is described in detail
> in the link I referenced.
>
> Don
>
Don:
Hopefully someone will report a success with 'N' ... or at least a
confirm that there is something not behaving in the E4200
Paul
Paul,
Did you look at stream of emails I referenced? I took that as
confirmation of the problem. Was that a bad move? Not sure of the
etiquette here.
Don
6:04 p.m.
On 02/04/12 17:02, Paul Allen Newell wrote:
On 2/4/2012 3:53 PM, Dave Stevens wrote:
> Quoting Larry <larry-lists(a)maxqe.com>:
>
>> On 02/04/2012 05:37 PM, don fisher wrote:
>>> I am receiving The following error messages every 30 seconds in
>>> /var/log/messages:
>
> I've used wrt56g routers from linksys for all OS combos for years with
> great success.
>
> Dave
>
No problem with network using 2 WRT54GL and 1 WAP54G. I have not tried
'N' routers from Linksys, which I gather is what you are using from the
contents of the link you enclosed.
Paul
Paul,
It is an E4200. Sorry for not mentioning it. It is described in detail
in the link I referenced.
Don
5:53 p.m.
Quoting Larry <larry-lists(a)maxqe.com>:
On 02/04/2012 05:37 PM, don fisher wrote:
> I am receiving The following error messages every 30 seconds in
> /var/log/messages:
I've used wrt56g routers from linksys for all OS combos for years with
great success.
Dave
>
> avahi-daemon[1029]: Received response from host 192.168.7.1 with
> invalid source port 32783 on interface 'eth0.0'
>
6:03 p.m.
Quoting don fisher <hdf3(a)comcast.net>:
On 02/04/12 16:53, Dave Stevens wrote:
> Quoting Larry <larry-lists(a)maxqe.com>:
>
>> On 02/04/2012 05:37 PM, don fisher wrote:
>>> I am receiving The following error messages every 30 seconds in
>>> /var/log/messages:
>
> I've used wrt56g routers from linksys for all OS combos for years with
> great success.
>
> Dave
>
>>>
>>> avahi-daemon[1029]: Received response from host 192.168.7.1 with
>>> invalid source port 32783 on interface 'eth0.0'
>>>
>
>
Dave,
That has been my experience also. I have three of them, but old
enough to slow down the link to my internet link supplied by
Comcast. So I upgraded and found the errors and the link described
in the first email. I lost it when I was told it was for Windows
only. I thought we were past that.
Don
OK, I don't have a great suggestion for you, I agree Linksys should be
prime actor. But what about dd-wrt or openwrt? More work but more
control...
No free lunch I guess. Sometimes no lunch even if you pay...
D
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
--
It is told that such are the aerodynamics and wing loading of the
bumblebee that, in principle, it cannot fly...if all this be
true...life among bumblebees must bear a remarkable resemblance to
life in the United States.
-- John Kenneth Galbraith, in American Capitalism: The Concept of
Countervailing Power
6:02 p.m.
On 2/4/2012 3:53 PM, Dave Stevens wrote:
Quoting Larry <larry-lists(a)maxqe.com>:
> On 02/04/2012 05:37 PM, don fisher wrote:
>> I am receiving The following error messages every 30 seconds in
>> /var/log/messages:
I've used wrt56g routers from linksys for all OS combos for years with
great success.
Dave
No problem with network using 2 WRT54GL and 1 WAP54G. I have not tried
'N' routers from Linksys, which I gather is what you are using from the
contents of the link you enclosed.
Paul
6 p.m.
On 02/04/12 16:53, Dave Stevens wrote:
Quoting Larry <larry-lists(a)maxqe.com>:
> On 02/04/2012 05:37 PM, don fisher wrote:
>> I am receiving The following error messages every 30 seconds in
>> /var/log/messages:
I've used wrt56g routers from linksys for all OS combos for years with
great success.
Dave
>>
>> avahi-daemon[1029]: Received response from host 192.168.7.1 with
>> invalid source port 32783 on interface 'eth0.0'
>>
Dave,
That has been my experience also. I have three of them, but old enough
to slow down the link to my internet link supplied by Comcast. So I
upgraded and found the errors and the link described in the first email.
I lost it when I was told it was for Windows only. I thought we were
past that.
Don
5:55 p.m.
On 02/04/12 16:48, Larry wrote:
On 02/04/2012 05:37 PM, don fisher wrote:
> I am receiving The following error messages every 30 seconds in
> /var/log/messages:
>
> avahi-daemon[1029]: Received response from host 192.168.7.1 with
> invalid source port 32783 on interface 'eth0.0'
>
> I looked on the internet and found a blog with the same problem:
>
>
http://homecommunity.cisco.com/t5/Wireless-Routers/Received-response-from...
>
>
> I went to CISCO to determine what the resolution was.
> 1. Live Chat support informed me that Linksys was only supported under
> Windows and that I could call live support at 1-800-326-7114.
> 2. Live support made be perform rather silly tests under Windows. Then
> passed me to a supervisor.
> 3. The Supervisor could not find the above email thread on their own
> site!
>
> Linksys does not have an email address for support. And the people I
> spoke to were not savvy enough to understand the problem as described
> in the above thread.
>
> Is Linksys a known problem for Linux systems? Should it be?
>
> Are there any suggestions on how to bound the size of my message files
> other that editing avhi so that it does not issue these warning messages?
>
> I was online or on the phone to Linksys for over 3 hours. I do not
> know where they are located, but I could barely understand their
> english. It was one of the worst support experiences in my 35 years of
> system involvement!
>
> Don
Have you tried updating the firmware on the Linksys? Perhaps it is a bug
that has been fixed.
Larry,
Yes. The firmware is the current version and build number.
Thanks,
Don
5:48 p.m.
On 02/04/2012 05:37 PM, don fisher wrote:
I am receiving The following error messages every 30 seconds in
/var/log/messages:
avahi-daemon[1029]: Received response from host 192.168.7.1 with
invalid source port 32783 on interface 'eth0.0'
I looked on the internet and found a blog with the same problem:
http://homecommunity.cisco.com/t5/Wireless-Routers/Received-response-from...
I went to CISCO to determine what the resolution was.
1. Live Chat support informed me that Linksys was only supported under
Windows and that I could call live support at 1-800-326-7114.
2. Live support made be perform rather silly tests under Windows. Then
passed me to a supervisor.
3. The Supervisor could not find the above email thread on their own
site!
Linksys does not have an email address for support. And the people I
spoke to were not savvy enough to understand the problem as described
in the above thread.
Is Linksys a known problem for Linux systems? Should it be?
Are there any suggestions on how to bound the size of my message files
other that editing avhi so that it does not issue these warning messages?
I was online or on the phone to Linksys for over 3 hours. I do not
know where they are located, but I could barely understand their
english. It was one of the worst support experiences in my 35 years of
system involvement!
Don
Have you tried updating the firmware on the Linksys? Perhaps it is a bug
that has been fixed.
--
Larry Brower, CCENT
Fedora Ambassador - North America
Fedora Quality Assurance
lbrower(a)fedoraproject.org
http://www.fedoraproject.org/
7:58 p.m.
On 02/04/2012 06:37 PM, don fisher wrote:
I am receiving The following error messages every 30 seconds in
/var/log/messages:
avahi-daemon[1029]: Received response from host 192.168.7.1 with
invalid source port 32783 on interface 'eth0.0'
I looked on the internet and found a blog with the same problem:
http://homecommunity.cisco.com/t5/Wireless-Routers/Received-response-from...
As already defined, it's multicast DNS (mDNS). You can shut down
the avahi-daemon service if you're not using it. I've disabled it on my
linux boxes because it's just more background radiation on my network.
You could also look at your router config to see if you can turn off
mDNS (if you don't want to disable your avahi-daemon).
Shane
I went to CISCO to determine what the resolution was.
1. Live Chat support informed me that Linksys was only supported under
Windows and that I could call live support at 1-800-326-7114.
2. Live support made be perform rather silly tests under Windows. Then
passed me to a supervisor.
3. The Supervisor could not find the above email thread on their own
site!
Linksys does not have an email address for support. And the people I
spoke to were not savvy enough to understand the problem as described
in the above thread.
Is Linksys a known problem for Linux systems? Should it be?
Are there any suggestions on how to bound the size of my message files
other that editing avhi so that it does not issue these warning messages?
I was online or on the phone to Linksys for over 3 hours. I do not
know where they are located, but I could barely understand their
english. It was one of the worst support experiences in my 35 years of
system involvement!
Don
6:07 p.m.
On 2/4/2012 4:04 PM, don fisher wrote:
Paul,
It is an E4200. Sorry for not mentioning it. It is described in detail
in the link I referenced.
Don
Don:
Hopefully someone will report a success with 'N' ... or at least a
confirm that there is something not behaving in the E4200
Paul
4473
days inactive
4475
days old
22 comments
10 participants
participants (10)
-
Dave Stevens -
don fisher -
John Wendel -
Larry -
Paul Allen Newell -
pringler01＠gmail.com -
Reindl Harald -
Scott Doty -
Shane -
T.C. Hollingsworth