At 11:42 AM 5/6/02 -0500, Michael D. Schleif wrote: [...] >OK, I have tried your suggestions -- without success. > >Please, refer to <http://www.helices.org/tmP/mcaI/mcai_isdn.txt> for the >details that you have requested. > >What do you think?
First, I think the Web link is a nice presentation of the data. Very readable. Second ... is there a typo in what you posted or do you have a simple gateway problem? (Or am I misreading what you posted?) The LEAF router's eth0 address is 192.168.11.254, but the client you are pinging from has a default gateway address of 192.168.11.252. At least that's how I read these lines from the Web stuff you posted: >7: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 > link/ether 00:10:4b:33:e7:a6 brd ff:ff:ff:ff:ff:ff > inet 192.168.11.254/24 brd 192.168.11.255 scope global eth0 ... and ... >Active Routes: >Network Destination Netmask Gateway Interface Metric > 0.0.0.0 0.0.0.0 192.168.11.252 192.168.11.10 [...] >Default Gateway: 192.168.11.252 This shouldn't interfere with the Windows client finding the ISDN router, since you also have a host route to it through 192.168.11.254 ... but it does make me wonder how (or even if) the client is using the LEAF router to reach the Internet. Third ... please forgive me if I'm repeating a question by coming into this discussion late, but ... can the client at 192.168.11.10 ping the relevant "foreign" interface address of the router (192.168.14.254)? Probably not, since its reported routing table does not include a route to that IP address. With that test unavailable, deciding if the problem is in the LEAF router or elsewhere becomes more difficult. So ... since the firewalling rules and the routing table on the LEAF router look OK ... I wonder if the routing tables on the two "clients" are configured correctly. I've already commented on oddities in the routing table you list for the Windows client. The most likely problem, though: does the ISDN router know that 192.168.14.254 is its route to 192.168.11.0/24? (Always handy to point the finger at a non-LEAF, non-Linux component, right?) If it does not, and you can't adjust its routing table, you may need to proxy-arp the 192.168.11.0/24 LAN on that interface of the LEAF router. One sure test of this guess -- temporarily put a Linux client on the eth1 LAN and see if it and the eth0 hosts can communicate. I am assuming here that the client at 192.168.11.10 *can* ping 192.168.11.254 with no trouble, since prior messages seem to say that the 192.168.11.0/24 LAN can reach the Internet via the T-1 route (though the routing table you reported does make me wonder how). If you do have a routing problem, fixing it won't necessarily solve the problem of making the ISDN link serve as a fallback route. But if you do have a "local" routing problem of the sort I'm suggesting, you can't even try to get alternate-route rules working until you fix it. -- ------------------------------------"Never tell me the odds!"--- Ray Olszewski -- Han Solo Palo Alto, CA [EMAIL PROTECTED] ---------------------------------------------------------------- _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
