ARP Routing query

>From a remote wireless card, I get ARP requests:

who has 222.2.2.2, tell 192.168.2.2

(222.2.2.2 is a fictitious nameserver, 192.168.2.2 is the wificard's
address)

These requests are seen at the AP, which is connected to the local
192.168.0.0/24 network. This network has a default route for any
extraneous IP to the ppp0 internet connection (locally the network
functions).

I'm not clear what should happen:

1) Should ppp0 answer as an ARP proxy? (I tried setting proxy_arp to
1 on the ppp0)

2) A local request for a connection (ping in this case) to the
222.2.2.2 IP immediately connects.

3) Is this because the Gateway value in the AP must be programmed?

4) Is the firewall getting in the way? There is a rule that allows all
packets from the internal network out to the world.
I'd appreciate pointers...
John

(E-Mail Removed) wrote:
>>From a remote wireless card, I get ARP requests:
>
> who has 222.2.2.2, tell 192.168.2.2
>
> (222.2.2.2 is a fictitious nameserver, 192.168.2.2 is the wificard's
> address)
>
> These requests are seen at the AP, which is connected to the local
> 192.168.0.0/24 network. This network has a default route for any
> extraneous IP to the ppp0 internet connection (locally the network
> functions).
>
> I'm not clear what should happen:
>
> 1) Should ppp0 answer as an ARP proxy? (I tried setting proxy_arp to
> 1 on the ppp0)
>
> 2) A local request for a connection (ping in this case) to the
> 222.2.2.2 IP immediately connects.
>
> 3) Is this because the Gateway value in the AP must be programmed?
>
> 4) Is the firewall getting in the way? There is a rule that allows all
> packets from the internal network out to the world.
> I'd appreciate pointers...
> John

A machine should only arp for an address if it thinks the address is on
the local subnet, otherwise it arps for the router and gets the router
to forward the data. If your machine is arping for an address which is
not on its local subnet, then you've got it (probably your wireless
card) configured incorrectly.

Hello Allen.

Thanks for the hint. I've got it working - partly. There was a rather
stupid problem in the iptables commands which didn't let some of the
packets propagate. From the Client card I
can now enter the AP, then on to the through the ethernet to the host
and
out to the internet, all fine. Now I have to find out the reverse path.
Cheers,
John