On 5/20/2015 3:30 PM, PGNd wrote: >>> What do I need to change that /params entry to in order to correctly grab >>> that ISP GW addr? >> Usually nothing. > I'll hope for that. > >> If Shorewall isn't able to detect the gateway, then you >> may have to use the 'findgw' extension script to dig it out of your DHCP >> client's files in /var. > Assuming that I've a running dhcp client on an accessible maching, with a > lease populated in its /var, that's clear. > > But, I do not. The dhcp client runs on the Uverse box. It's been suggested > to me that I'll not have access to that (ATT's boxes are rumored to have very > limited access). I'll of course be able to verify at the time I have one in > front of me ... > > Likely, there will need to be some digging around. >
No -- the gateway is 192.168.4.XXX (the IP address of the Uverse box). -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
