Here is the output from my trace. It looks like some output to the screen is
"leaking" and getting assigned to SW_ETH2_ADDRESS.
+ date +%b %d %T
+ timestamp=Jan 12 21:13:11
+ echo Jan 12 21:13:11 Processing /etc/shorewall/params ...
+ g_stopping=
+ [ -d /var/lib/shorewall ]
+ [ -n /var/log/shorewall-init.log ]
+ touch /var/log/shorewall-init.log
+ chmod 0600 /var/log/shorewall-init.log
+ [ 0 -eq 1 ]
+ finished=0
+ [ 0 -eq 0 -a 1 -gt 0 ]
+ option=restart
+ finished=1
+ [ 1 -eq 0 -a 1 -gt 0 ]
+ COMMAND=restart
+ [ 1 -ne 1 ]
+ shorewall_is_started
+ qt /sbin/iptables -L shorewall -n
+ /sbin/iptables -L shorewall -n
+ progress_message3 Restarting Shorewall....
+ local timestamp
+ timestamp=
+ [ 0 -ge 0 ]
+ [ -n ]
+ echo Restarting Shorewall....
+ [ 2 -ge 0 ]
+ date +%b %d %T
+ timestamp=Jan 12 21:13:11
+ echo Jan 12 21:13:11 Restarting Shorewall....
+ detect_configuration
+ find_first_interface_address_if_any eth2
+ grep inet .* global
+ head -n1
+ ip -f inet addr show eth2
+ addr= inet 24.229.49.194/24 scope global eth2
Jan 12 21:13:11 Restarting Shorewall...
+ [ -n inet 24.229.49.194/24 scope global eth2
Jan 12 21:13:11 Restarting Shorewall... ]
+ echo inet 24.229.49.194/24 scope global eth2 Jan 12 21:13:11 Restarting
Shorewall...
+ sed s/\s*inet //;s/\/.*//;s/ peer.*//
+ SW_ETH2_ADDRESS=Jan 12 21:13:11 Restarting Shorewall...24.229.49.194
+ find_first_interface_address_if_any eth0
+ grep inet .* global
+ head -n1
+ ip -f inet addr show eth0
+ addr= inet 66.109.227.106/29 scope global eth0
+ [ -n inet 66.109.227.106/29 scope
global eth0 ]
+ sed s/\s*inet //;s/\/.*//;s/ peer.*//
+ echo inet 66.109.227.106/29 scope global eth0
+ SW_ETH0_ADDRESS=66.109.227.106
+ SW_ETH0_IS_USABLE=
+ SW_ETH2_IS_USABLE=
On Wed, Jan 19, 2011 at 1:07 PM, Tom Eastep <teas...@shorewall.net> wrote:
> On 1/19/11 7:33 AM, marvin horst wrote:
> > I am having some issues with the shorewall module distributed with Bering
> > 4.0.
> >
> > Shorewall appears to NOT be using the perl version of the firewall by
> > default. Where do I change this? I'm having problems with the shell
> version.
> > See below...
> >
> > I had some issues with the shorewall scripts were the date command is
> used
> > with a format containing underscores (i.e. date +'%_b %_d %T').
> Apparently
> > the version of date on uClibc does not recognize the underscore. I
> changed
> > the date formats to not use the underscore, but I have another issue that
> > appears to be related to a timestamp variable. This is my output after a
> > shorewall restart
>
> KP -- I thought you had changed the Bering-uClibc 4.0 Shorewall package
> to correct that problem.
>
> >
> > Shorewall configuration compiled to /var/lib/shorewall/.restart
> > sh: Jan: invalid number
> > sh: 17:07:28: invalid number
> > Processing /etc/shorewall/params ...
> > Jan 12 17:07:28 Processing /etc/shorewall/params ..Usage:
> > /var/lib/shorewall/.restart [ options ] [
> > start|stop|clear|down|reset|refresh|restart|status|up|version ]
> >
> > I the ran a shorewall restart -f and get this output:
> >
> > fw# shorewall restart -f
> > sh: Jan: invalid number
> > sh: 17:07:39: invalid number
> > Processing /etc/shorewall/params ...
> > Jan 12 17:07:39 Processing /etc/shorewall/params ..Restarting
> Shorewall....
> > Jan 12 17:07:39 Restarting Shorewall...Initializing...
> > Jan 12 17:07:39 Initializing..Processing /etc/shorewall/init ...
> > Jan 12 17:07:40 Processing /etc/shorewall/init .. WARNING:
> > DISABLE_IPV6=Yes in shorewall.conf but this system does not appear to
> have
> > ip6tables
> > Setting up Route Filtering...
> > Jan 12 17:07:40 Setting up Route Filtering..Setting up Martian Logging...
> > Jan 12 17:07:40 Setting up Martian Logging..Setting up Proxy ARP...
> > Jan 12 17:07:40 Setting up Proxy ARP..Jan 12 17:07:40 Shorewall-generated
> > routing tables and routing rules removeAdding Providers...
> > Jan 12 17:07:40 Adding Providers..Jan 12 17:07:40 Provider WNDSTRM (1)
> > AddeError: an inet address is expected rather than "Jan".
> > ERROR: Command "ip -4 route replace 24.229.49.1 src Jan 12 17:07:39
> > Restarting Shorewall...24.229.49.194 dev eth2 table 2" Failed
> >
>
> Marvin,
>
> Given that you can reproduce this problem, please 'sh -x
> /var/lib/shorewall/.restart restart 2> trace' and examine the 'trace'
> file to see where this is happening.
>
> -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 \________________________________________________
>
>
>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> ------------------------------------------------------------------------
> leaf-user mailing list: leaf-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/leaf-user
> Support Request -- http://leaf-project.org/
>
>
--
Marvin Horst
IT Manager
Paul B Zimmerman Inc
(717) 738-7365 x824
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/
