Hi List, I am using the eigerstein2beta-pppoe by Kenneth Hadley (LRP image from http://lrp.steinkuehler.net/contrib_disk_images.htm) for about a year now, works fast and reliable, but I have one Problem with my seccond network. I will try to explain the situation I have: ________________ | World Wide Web | |________________| || PPPoE _______||________ | LRP-Box | | dynamic IP | | | | 192.168.1.254 | |_________________| || _____________________________ internal net __| | 100Mbit/switched --| Clients range .1.1 - .1.253 | 192.168.1.x |_____________________________| _______||______ | my Server | | 192.168.1.253 | | | | 192.168.1.254 | |_______________| || seccond internal net 10Mbit/BNC-Ethernet 192.168.0.x || _______||______ | Clients range | | .0.1 - .0.253 | |_______________|
Some words to the fancy stuff above: I have my LRP Box running as internal 192.168.1.254, external I have dynamic IPs. The LRP Box is connected to the "main" clients I have with 100Mbit Ethernet, including my server which has 192.168.1.253. In the server I have again 2 NICs, one 100Mbits for main Network and a 10Mbit for my "Terminal-Network" (Some old PCs netbootet which not always have any opportunity to be equipped with an 100Mbit card), those 2 networks have no physical connection, only meet at my server. So I turned on bridging on my server with the result that I can ping and do whatever between both networks. I added route add -net 192.168.0.0 netmask 255.255.255.0 gw 192.168.1.253 on my LSP Box so it knows what to do with the packages adressed to the .0.x-network. So far it works, but if i try to reach the www it fails. Running traceroute i can see that the ping goes from client to my server and from my server to my lrp box, but there it seems that it does not go any further. I think this is basical the same as trying to reach the www inside my 100Mbits net when changing IP to something else than 192.168.1.x, I think this has something to do with the IP-Chains-filters, but I don't know what I have to add/change that not only 192.168.1.x can use the router but 192.168.0.x can use it as well. If anyone got what I want, understood my problem or has a clue, please held ;) Claas Rathje ps: Sorry for my bad English, just a german teenager still going to school. ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ------------------------------------------------------------------------ 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
