mess-mate wrote: > Tom Eastep <[EMAIL PROTECTED]> wrote: > | Tom Eastep wrote: > | > Tom Eastep wrote: > | > > | >> I suspect that what you need to do is simply change the default gateway > to > | >> point to the IP address of the internal interface of the Shorewall > router. > | >> > | > > | > Groan -- that should have been "... to *point* to the IP ...". > | > | Hmmm -- I guess I need to get my eyes tested; the original said what I > wanted > | in the first place... > | > Ok, changing the modem didn't change anything :( So replaced with > the original (st510).
Your the one that decided to replace the modem. No one on this list suggested that the modem was the problem. > But..... had to reboot and when shorewall stopped and started the message ' > find_first_interface_address not found line 27 ' is still there ! I don't know what else I can do. I've asked for a trace that shows the problem and you keep sending me traces that don't show the problem. There is nothing more that I can do -- I can't come to France and look over your shoulder. > > 'Network is unreacheble' if changing the default gateway for the lan or dmz > machines. > I followed the 'three-interfaces' doc; see here on the shorewall > router : > ip route ls > 193.253.160.3 dev ppp0 proto kernel scope link src 86.207.39.186 > 192.168.20.0/24 dev eth2 proto kernel scope link src 192.168.20.254 > 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.1 > 192.168.10.0/24 dev eth1 proto kernel scope link src 192.168.10.254 > default dev ppp0 scope link I didn't suggest that routing on the Shorewall box is wrong. You have conclusively proved that when you try to access the web server using address 86.207.39.186 (I see that it has changed), that the connect request IS NOT REACHING THE SHOREWALL SYSTEM. No router in the world can route packets that are not sent to it. > > Please keep in mind that shorewall runs fine otherwise. The only > thing i can't do is accessing the dmz from the lan via the net, And you have proved that problem has nothing to do with Shorewall or the Shorewall system. and > that 'find_first_interface_address not found line 27'. > As i said that message is only there on a start or stop of > shorewall, not when shorewall is running and restarting it. And I can't help you with that unless you can trace it happening. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
