Mailinglist Archive: opensuse (4348 mails)

< Previous Next >
Re: [SLE] SuSEfirewall
  • From: Anders Johansson <andjoh@xxxxxxxxxxxxxxxxxxxxx>
  • Date: Wed, 2 Oct 2002 16:20:00 +0200
  • Message-id: <200210021620.00038.andjoh@xxxxxxxxxxxxxxxxxxxxx>
On Wednesday 02 October 2002 16.02, James Oakley wrote:
> On October 2, 2002 08:43 am, Brian Marr wrote:
> > Suse 8.0 Vmware 3.1
> > My SuSEfirewall configuration is progressing. I am on the net !
> > But am not sure what to make of this
> > Brian Marr
> >
> > Oct 2 21:11:03 Gringo kernel: SuSE-FW-UNAUTHORIZED-TARGET IN=vmnet1 OUT=
> > MAC=00:50:56:c0:00:01:00:50:56:c1:6c:f5:08:00 SRC=192.168.77.128
> > DST=192.168.77.1 LEN=40 TOS=0x00 PREC=0x00 TTL=128 ID=49945 DF PROTO=TCP
> > SPT=1025 DPT=139 WINDOW=8653 RES=0x00 ACK URGP=0
>
> IN=vmnet1 # The OS you're running under Vmware generated the packet
> DPT=139 # That's the destination port, which is Netbios
>
> Basically, Windows under Vmware is sending traffic (looking for other
> Windows boxes) and your SuSEfirewall is configured to reject and log
> packets on port 139.

No, the problem is that it isn't configured to accept packets from the vmnet1
interface on that ip address at all. I think he needs to set up class routing
in SuSEfirewall2

//Anders

< Previous Next >