Re: Routing problem
- From: ibuprofin@xxxxxxxxxxxxxxxxxxxxxx (Moe Trin)
- Date: Fri, 30 Dec 2005 14:14:50 -0600
On 30 Dec 2005, in the Usenet newsgroup comp.os.linux.networking, in article
<1135945239.703183.206700@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, Ake L wrote:
>>So look at the packets on the wlan0 interface on ALGS-03. Are the packets
>>being sent to GATEKEEPER? Is GATEKEEPER responding?
>
>Yes, the packets reaches GATEKEEPER, but it is not responding. This
>indicates there is something fishy with the GATEKEEPER, no?
Yes - either it doesn't know where 192.168.1.0/8 is, or it has a firewall set
to ignore those addresses.
>I solved the problem temporarily by changing the net mask on
>GATEKEEPER:eth1 to 255.255.254.0.
That's highly unusual. That's telling GATEKEEPER that networks 192.168.0.0/24
and 192.168.1.0/24 are _directly_ attached.. Changing to 192.168.0.0/23 is
also going to change the broadcast address and those hosts with 192.168.0.0/24
will no longer detect this (192.168.1.255 is outside the range of 192.168.0.0
to 192.168.0.255). If ALGW-05 is actually receiving the packets from
GATEKEEPER, then ALGS-03 is "bridging" rather than routing - that is, it is
forwarding the packets even though they aren't addressed to it.
Old guy
.
- Follow-Ups:
- Re: Routing problem
- From: Ake L
- Re: Routing problem
- References:
- Routing problem
- From: Ake L
- Re: Routing problem
- From: Moe Trin
- Re: Routing problem
- From: Ake L
- Re: Routing problem
- From: Ake L
- Routing problem
- Prev by Date: Re: Question about blocking IP's
- Next by Date: Re: Question about blocking IP's
- Previous by thread: Re: Routing problem
- Next by thread: Re: Routing problem
- Index(es):