Proxy ARP comes to use when other devices on one side of your server have to
big netmasks. Take the following situation:
a machine connected to your eth0 side has ip-address 192.168.155.2 netmask
255.255.255.0
That means that it will try to directly connect to all ip-addresses in the
range 192.168.155.0 to 192.168.255.255. Since that includes the range that
is on your eth1 side, it will not work. You either have to change the
netmask on the machine, or make your server do proxy arp to make the machine
think it is talking directly to the machine on the eth1 side.
right now your interfaces are:
eth0:192.168.155.0 netmask 255.255.255.0
eth1:192.168.1.177 netmask 255.255.0.0
eth1 consideres eth0 to be in the same range, but eth0 considers eth1 out of
range, so it probably will not proxy-arp. change the mask on eth0.
serge.
-----Original Message-----
From: Javier Castillo [mailto:[EMAIL PROTECTED]]
Sent: vrijdag 23 juni 2000 11:24
To: Serge Maandag
Cc: [EMAIL PROTECTED]
Subject: Re: Proxy ARP
Hello Serge,
why?, is mandatory in order proxy arp works?.
Javier.
Serge Maandag wrote:
>
> Javier,
>
> The netmask set on eth0 should be 255.255.0.0
>
> Serge.
>
> -----Original Message-----
> From: Javier Castillo [mailto:[EMAIL PROTECTED]]
> Sent: vrijdag 23 juni 2000 10:40
> To: Glynn Clements
> Cc: [EMAIL PROTECTED]
> Subject: Re: Proxy ARP
>
> Thanks Glynn for help me:
>
> alhmngsrv:~# ifconfig
> eth0 Link encap:Ethernet HWaddr 00:A0:C9:9C:C6:B6
> inet addr:192.168.155.1 Bcast:192.168.155.255
> Mask:255.255.255.0
> inet6 addr: fe80::2a0:c9ff:fe9c:c6b6/10 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:857 errors:0 dropped:0 overruns:857 carrier:0
> collisions:0 txqueuelen:100
> Interrupt:5 Base address:0x3000
>
> eth1 Link encap:Ethernet HWaddr 00:A0:24:4D:7B:03
> inet addr:192.168.1.177 Bcast:192.168.255.255
> Mask:255.255.0.0
> inet6 addr: fe80::2a0:24ff:fe4d:7b03/10 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:17942779 errors:26 dropped:0 overruns:0 frame:37
> TX packets:18017325 errors:0 dropped:0 overruns:0 carrier:1332
> collisions:8087 txqueuelen:100
> Interrupt:12 Base address:0xb400
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:3924 Metric:1
> RX packets:844515 errors:0 dropped:0 overruns:0 frame:0
> TX packets:844515 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
>
> alhmngsrv:~# route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.155.0 0.0.0.0 255.255.255.0 U 0 0 0
> eth0
> 10.15.1.0 192.168.1.207 255.255.255.0 UG 0 0 0
> eth1
> 192.168.0.0 0.0.0.0 255.255.0.0 U 0 0 0
> eth1
> 0.0.0.0 192.168.1.180 0.0.0.0 UG 0 0 0
> eth1
>
> alhmngsrv:~# cat /proc/sys/net/ipv4/conf/all/proxy_arp
> 1
> alhmngsrv:~# cat /proc/sys/net/ipv4/conf/all/rp_filter
> 1
> alhmngsrv:~# cat /proc/sys/net/ipv4/ip_forward
> 1
>
> Perhaps my kernel config causes an strange behavior??.
>
> Glynn Clements wrote:
> >
> > Javier Castillo wrote:
> >
> > > > > I read that linux 2.2 can do automatix proxy arp, so if I
have
> two
> > > > > interfaces in my linux box:
> > > > >
> > > > > eth0: 192.168.0.1/16
> > > > > eth1: 192.168.1.1/24
> > > > >
> > > > > if for example, 192.168.0.25(a windows which is configurated
> with a
> > > > > 16bits netmask) tries to ping to
> > > > > 192.168.1.10, my linux box will reply to arp request from my
> windows??.
> > > >
> > > > Yes.
> > > >
> > > If so, why my linux box does not answer that arp request.
> > >
> > > Do I have to setup some "/proc/sys/net...." before??. I did
think
> that
> > > /proc/sys/net/ipv4/all/proxy_arp = 1 was enought :(
> >
> > For me, it was.
> >
> > What do "ifconfig" and "route -n" show?
> >
> > --
> > Glynn Clements <[EMAIL PROTECTED]>
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-net" in
> > the body of a message to [EMAIL PROTECTED]
>
> --
> Javier Castillo Alc�bar. [EMAIL PROTECTED]
> Alhambra Systems, S.A. http://www.alhsys.es
> Telf: 34 - 1 - 91 304 18 00
> Fax: 34 - 1 - 91 327 31 31
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to [EMAIL PROTECTED]
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to [EMAIL PROTECTED]
--
Javier Castillo Alc�bar. [EMAIL PROTECTED]
Alhambra Systems, S.A. http://www.alhsys.es
Telf: 34 - 1 - 91 304 18 00
Fax: 34 - 1 - 91 327 31 31
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
