I do not understand the warnings that I found on my warn log about what appears to be a dysfunction when using my wlan. Since they are jamming quite a bit my warn log, I would like to find out what is the error:
Mar 3 15:10:31 argo kernel: [17875.034507] martian source 255.255.255.255 from 192.168.178.21, on dev wlan0
Mar 3 15:10:31 argo kernel: [17875.034511] ll header: ff:ff:ff:ff:ff:ff:00:0b:3b:d1:30:4f:08:00
This repeats on a long long row.
I would like to know if anyone knows what goes wrong.
This is a modified 11.1 evergreen with a custom 3.2.8 kernel on a Lenovo X201.
Thanks.
Potent****ial Solutions
**Multiple NICs on the same subnet:**Multiple NICs on the same subnet is the most common cause. If you must have multiple NICs on the same subnet, use a managed switch. This can be tested by off-lining all but one NIC cards; if the messages go away, then you can assume that the multiple NICs are the cause. Another solution would be to bond the NICs together. Generally speaking a properly configured network should not require multiple NICs to be on the same subnet, except in the case of bonding.
Thank you for your reply. My network knowledge is limited. I will be grateful if somebody can help me to set it up correctly.
My current devices are as follows:
I have a Gobi 2000 Umts card in this computer.
I have a Wlan-n card on this computer.
I have to connect on a regular basis with an external umts-cellphone in tethering too.
of course there is a eth-0 card that I use at times.
This computer had chronic problem with routing and DNS because of the incapacity to handle external umts devices (I guess that but I am by no means sure).
Could someone help me to set up correctly my devices and my dns / route?
This would be helpful for any computer, the fact is, as the main part of the how-to are written they expect you to be already proficient in what you are doing…while obviously you are not.
BTW, the bluetooth is activated in the kernel, the module loaded but since the KDE3 bluetooth is broken I do not use it currently. I do not think however that this is the problem.
Question:
normally, if I am using ONLY the WLAN to connect, I should not have this message, right? This even if I have multiple NIC on the same subnet…
O.K. maybe I found the origin of extraterrestrial life.
I had two dns servers defined, and also for the sound server (pulse) the Avahi. Now where I am right now we have a udp capable router from AMV that apparently caused the issue. Or was it the dns server… Still, having left only one dns server address defined, and having shutdown avahi, up to now this does not reproduce. Nor do I have martian sources in the logs while on other networks in the past 14 days to a month.
So I think that was it.
Thanks for the links.
Well, I was suddenly not able to connect to the Internet any more. So I checked
cat /var/log/warn
where you get:
Mar 6 11:29:42 argo kernel: 3455.139408] iwlwifi 0000:02:00.0: Queue 2 stuck for 2000 ms.
Mar 6 11:29:42 argo kernel: 3455.139416] iwlwifi 0000:02:00.0: Current read_ptr 0 write_ptr 1
Mar 6 11:29:42 argo kernel: 3455.139421] iwlwifi 0000:02:00.0: On demand firmware reload
Mar 6 11:29:44 argo kernel: 3457.293563] martian source 255.255.255.255 from 192.168.178.21, on dev wlan0
Mar 6 11:29:44 argo kernel: 3457.293568] ll header: ff:ff:ff:ff:ff:ff:00:0b:3b:d1:30:4f:08:00
Mar 6 11:29:45 argo kernel: 3458.289485] martian source 255.255.255.255 from 192.168.178.21, on dev wlan0
Mar 6 11:29:45 argo kernel: 3458.289490] ll header: ff:ff:ff:ff:ff:ff:00:0b:3b:d1:30:4f:08:00
Mar 6 11:29:46 argo kernel: 3459.287782] martian source 255.255.255.255 from 192.168.178.21, on dev wlan0
There was once a bug in 11.1 I believe, but I am by no means sure.
Is this system being compromised? Is it my network setting? Is it my router. I really would appreciate help on how to diagnose this issue. Thanks whoever is network efficient to get me some help.
Before I got also this (don’t know if that helps):
Mar 6 10:34:13 argo kernel: 131.903121] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
Mar 6 10:38:04 argo gnome-keyring-daemon[3921]: couldn't write 232 bytes to client: Pipe rotta
Mar 6 10:38:19 argo pulseaudio[4495]: pid.c: Daemon already running.
Mar 6 10:38:34 argo kernel: 392.547596] martian source 255.255.255.255 from 192.168.178.21, on dev wlan0
Mar 6 10:38:34 argo kernel: 392.547600] ll header: ff:ff:ff:ff:ff:ff:00:0b:3b:d1:30:4f:08:00
Mar 6 10:38:35 argo kernel: 393.540957] martian source 255.255.255.255 from 192.168.178.21, on dev wlan0
Mar 6 10:38:35 argo kernel: 393.540960] ll header: ff:ff:ff:ff:ff:ff:00:0b:3b:d1:30:4f:08:00
Mar 6 10:38:37 argo nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.
Mar 6 10:38:37 argo nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/nfs' exited with error status 2.
Mar 6 11:26:03 argo nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.
I continue not to understand what pulseaudio has to do with this. Autofx and nfs are not used (for what I know) by me, so maybe this is still the router (UDP), I will try to switch off UDP to see whether this helps.