10-19-04 01:45 AM
In article <cl084j$5rk$1@ctb-nnrp2.saix.net>, Steven Hook wrote:
>OK, I just figured out I have to have a dialin connection for ppp0 to show:
>Old (Working):
>
>ppp0 Link encap:Point-to-Point Protocol
> inet addr:192.168.15.5 P-t-P:192.168.15.10 Mask:255.255.255.255
OK - big clue here. You have 192.168.15.5 on one end of the wire, and
192.168.15.10 on the other. But your Ethernet is 192.168.10.219, and
you're using a 255.255.255.0 mask, so these are different networks.
Proxyarp isn't going to be a big help here. Do the other clients on the
192.168.10.0 network know that to reach 192.168.15.x, they have to send
their packets to 192.168.10.219? Every host that's going to talk to
the 192.168.15.x hosts on the Ethernet has to have a routing entry like
this:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 95017 eth0
192.168.15.0 192.168.10.219 255.255.255.0 UG 0 0 240 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 420 lo
If they don't have that route, they won't know to send packets in this
direction. You may also have a route to the world using another gateway
like
0.0.0.0 192.168.10.254 0.0.0.0 UG 0 0 1520 eth0
and that means that some poor router is getting packets it doesn't know
what to do with.
>new:
>
>ppp0 Link encap:Point-to-Point Protocol
> inet addr:192.168.15.5 P-t-P:192.168.15.10 Mask:255.255.255.255
> UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
> RX packets:122 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:3
> RX bytes:9999 (9.7 Kb) TX bytes:32 (32.0 b)
Basically looks OK, except that the link is probably only seeing packets
from the dialin peer destined for some host on your LAN, and the LAN host
has _no_ idea where to sent the responses.
Old guy
[ Post a follow-up to this message ]
| 
