Mailinglist Archive: opensuse-security (605 mails)

[christian.burri@xxxxxxxxxx]

hello list !

I upgraded two of my suse 7.2 boxen yesterdays with new patched 2.2.19
kernel. First box is a
shellserver and runs w/o probs.

The other box however is a firewall and started acting mega-weird this
morning...

There are 3 interfaces: Internet, DMZ and LAN. The ipchains script did work
fine
for more than a year and it hasnt changed since the kernel update.

Now, this morning all of a sudden everything here at our site looses
connectivity.
first it appeared to be one of our ISPs routers, but soon it appeared as
nothing
would work anymore. I could not even connect to the router infront of the
FW
(at the ISP side), all I got was "no route to host".

So I started poking at the firewall. After rebooting and doing rcnetwork
start/stop
a few times and rcroute, too, I managed to get connectivity from LAN to
Internet
back. Connectivity from Internet or LAN to DMZ was nonexistent tho.

I looked closer at the firewall scripts but they were indeed unchanged.

I then loaded iptraf on the machine and launched a ping from a remote
station. I could observe that the pings were reaching the firewall
and that they were travelling thru, going out on the dmz interface.
The DMZ server must have seen the pings, because it sent an echo reply
bacl, which the FW accepted on the DMZ interface.

>From there on, the echo_replies vanished tho, inside the firewall.
And no, the FW doesnt block pings, btw :-]

While trying some commands like ifconfig, ipchains -L -n and
netstat -s, all of a sudden connectivity DMZ->Inet came back.
It is now working again.

I have no idea what's going on, heh.

Anyone experience similar problems with patched 2.2.19 kernel?

Greets
Chr. Burri

    .-.
    /v\    L   I   N   U   X
   // \\   >I know KungFu!!<
  /(   )\
   ^^-^^