Masquerade: route sent us somewhere else.
Hello!!!
I finished my firewall settings yesterday. Basically copied some (about 140) lines from other Iptables files and changed them to suit my needs. I created a script and putted it in the rc.local file for it to start automatically and looks like itīs working fine... :-) But sometimes this message appears on the screen: Masquerade: route sent us somewhere else. Could anybody help me with what is triggering this message? The second thing is that when I start my Firewall before the connection (mine is adsl) is up, I get this message on screen: Iptables v1.2.11: host/network īlogin.icq.comī not found. Try īiptables -hī or īiptables --helpīfor more information. And when I start my PPP connection before the Firewall I donīt get the message. The question is: should any firewall start after the connection is up? For me that is more of an idealistic concept because it happens just one second after the connection is up. By the way, login.icq.com is the login page (destination) for ICQ, and I blocked it. Thanks a lot!!! Palula Brasil |
Re: Masquerade: route sent us somewhere else.
Quote:
Quote:
Firewall should rather start before your connection, but there are limitations, as you see above. |
Sorry for the delay in replying your message.
The only line I have on all my firewall regarding MASQUERADE is this one: /sbin/iptables -t nat -A POSTROUTING -s $lanip -j MASQUERADE (Where $lanip represents my LAN IP range) The message doesnīt appear often. It appears sometimes only. My internet connection looks fine on my windows clients, but even still itīs always annoying to know that something is going wrong with your config right? So I just want it to work 100% (as possible). Hope anyone can help me!! :-) Thanks a lot guys. |
Do you have login.icq.com anywhere in the script (not only in the masquerading line)?
|
Yep. I still have it on my firewall script.
But I will change it to the regular IP number. |
I changed it and the message still goes on appearing.
Something weird is that I just got my DHCP (with dhcpd) woking this afternoon and the Masquerade message seems to be appearing a bit more oftenly. But I can surf on the web normally still yet, and the DHCP is assigning adresses normally too. But anyway, Iīd really like to correct this problem. It reminds me of how I suck!!! :-) Thank in advance! Palula Brasil Here is my route table: Code:
Tabela de Roteamento IP do Kernel |
My opinion is that it's all because this entry:
169.254.0.0 * 255.255.0.0 U 0 0 0 eth1 169.254.x.x is global address space, still it's redirected to local network. If you connect to any server from that range of IPs, there's a problem that may result in the message you get. Is it possible to remove this entry or there's a reason why you have it? |
I donīt know how that entry has been generated.
I looked for everything regarding that IP adress (169.254.0.0) in my firewall rules and I didnīt find anything. How is an entry generated? And another thing. Could you give an explanation of how the route command can be read? I saw it and tried to understand, but for example I couldnīt even detect that this IP adress (169.254.0.0) shouldnīt be there... By the way. My network only comprehends adresses beetween 192.168.100.1 (server) and 192.168.100.2 - 192.168.100.255 (clients) so I really think I donīt need that IP (169.254.0.0). And theres something else I forgot too. As I said before, I configured a DHCP server on my Linux machine (DHCPD) itīs working fine (at least I think). The thing is: When I typed ifconfig, 3 interfaces were shown. eht0, eth1 and lo. Now 4 interfaces are shown eth0, eth1, lo and another wich I canīt remember because Iīm not in my machine, but Iīm pretty sure it has the letter "s". Is that normal, should it happen? Thanks a lot! :-) |
Ok!
I did a little research and tried hard to understand how this thing works and came up with this line to exclude this route from my routing table. Code:
route del -net 169.254.0.0 netmask 255.255.0.0 dev eth0 Thank You!!! :-) |
Quote:
Quote:
Routing table analysis is easy. You need to know which interfaces you have and what are their IPs and netmasks. Every interface should have an entry with its network. Default means..well...default (usually Internet connection). Quote:
Quote:
|
It didnīt work.
Every time I boot up, there it is again on the route table. Can anybody help me with this? Thank you! :-) |
Thereīs something else I forgot to tell.
In my Linux a service starts up at boot time called mDNSResponder. And it boots properly (doesnīt fail). But it gives two messages when I run the shutdown command (when itīs time for this service to unload). If the ppp0 connection is up at shutdown time: mDNSResponder: 17 messages supressed. MASQUERADE: route sent us somewhere else. If the ppp0 connection is down: mDNSResponder: No route. Rustyīs brain broke. Thanks in advance!!! Palula Brasil. |
The question is what's setting the entry up. It may be mDNSResponder.
To find *all* files with 169.254.0.0 run the following command (big warning: it can take even 10 minutes): cd /; grep -R 169.254.0.0 * How does the result look like? |
I couldnīt do that search because at some point my FC3 halted and putted a message regarding that the fd0 couldnīt be read... But it really shouldnīt be because the drive was not mounted and neither was I intrested in using the drive at that moment.
Anyway, unloading the mDNSResponder service took care of the route message. And it doesnīt show anymore messages regarding that route problem... But still there is that route (169.254.0.0) at the route table. And because of that Grep problem, I wasnīt unable to see which files has anything regarding that IP adress. How can I correct that problem? Thanks in advance. |
Quote:
cd /etc; grep -R 169.254.0.0 * Quote:
|
All times are GMT -5. The time now is 05:30 PM. |