logging problem with wvdial.dod
Hello, I now have the new fierwals package set up and working in combination with the wvdial.dod script from SuSE's web site. Please see another of my messages to this list that points to the changes I needed to make to wvdial.dod to get it working. I am still having one problem with the firewals script. I get *many* mesages like the following in /var/log/messages. There must be some mismatch between my Samba configuration and my rc.firewall configuration. I would appreciate it if someone would take a look at my smb.conf and rc.firewall which I have placed on my web site: http://paulsen.home.texas.net/smb.conf http://paulsen.home.texas.net/rc.firewall Here is a sample of the log messages: Dec 27 07:44:27 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=78 S=0x00 I=46162 F=0x0000 T=64 (#5) Dec 27 07:44:29 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=78 S=0x00 I=46163 F=0x0000 T=64 (#5) Dec 27 07:44:30 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=78 S=0x00 I=46164 F=0x0000 T=64 (#5) Dec 27 07:44:31 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=78 S=0x00 I=46165 F=0x0000 T=64 (#5) Dec 27 07:44:43 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:138 192.168.0.255:138 L=215 S=0x00 I=46168 F=0x0000 T=64 (#5) Dec 27 07:44:45 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:138 192.168.0.255:138 L=215 S=0x00 I=46169 F=0x0000 T=64 (#5) Dec 27 07:44:47 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:138 192.168.0.255:138 L=215 S=0x00 I=46170 F=0x0000 T=64 (#5) Dec 27 07:44:49 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:138 192.168.0.255:138 L=215 S=0x00 I=46173 F=0x0000 T=64 (#5) Dec 27 07:44:51 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:138 192.168.0.255:138 L=215 S=0x00 I=46174 F=0x0000 T=64 (#5) Dec 27 07:44:51 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=96 S=0x00 I=46175 F=0x0000 T=64 (#5) Dec 27 07:44:53 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=96 S=0x00 I=46176 F=0x0000 T=64 (#5) Dec 27 07:44:54 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=96 S=0x00 I=46177 F=0x0000 T=64 (#5) Dec 27 07:44:55 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=96 S=0x00 I=46178 F=0x0000 T=64 (#5) Dec 27 07:44:56 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=96 S=0x00 I=46179 F=0x0000 T=64 (#5) Dec 27 07:44:58 home kernel: Packet log: input DENY eth0 PROTO=17 192.168.0.1:137 192.168.0.255:137 L=96 S=0x00 I=46180 F=0x0000 T=64 (#5) -- ____________________________________________________________________ Robert Paulsen http://paulsen.home.texas.net
Hello,
I am still having one problem with the firewals script. I get *many* mesages like the following in /var/log/messages. There must be some mismatch between my Samba configuration and my rc.firewall configuration.
I asked the same question to Marc Heuse, and according to him one shouldn't install Samba and the firewall on the same machine. Samba tries to broadcast wich the firewall doesn't allow. If you want to allow Samba to broadcast, that would open several security holes. So the best solution is: put samba on another machine and install only a firewall on your gateway.
Robert Paulsen http://paulsen.home.texas.net
-- Frank Hart - mailto:frhart@home.nl SuSE Linux - Kernel 2.2.13 on a i586 100 Mhz with 24 Mb RAM -- History is curious stuff You'd think by now we had enough Yet the fact remains I fear They make more of it every year.
participants (2)
-
Frank Hart -
Robert C. Paulsen, Jr.