Greetings -- I have an interesting problem with a masqueraded losedows box. Originally it came with an Intel 100 Mbps ethernet, but later I added Intel PRO/1000 cards both to it and my SuSE server. I've turned on jumbo packages on Windows side, and everything works fine between them via Samba. E.g., a 4.7 GB file flies in a moment. :) But after switching to the gigabit, the *dows box stopped getting through to the internet! Previously it was on my wired subnetwork 192.168.0.0/24, I also have a wireless 192.168.3.0/24, eth0 goes to my hardware firewall as 192.168.2.0/24, and I assigned the gigabit as 192.168.1.0/24. Here's what I'm getting from SuSEfirewall2 3.1.22: Mar 9 21:42:04 angle kernel: SuSE-FW-DROP-DEFAULT IN=eth3 OUT=eth0 SRC=192.168.1.2 DST=216.239.53.101 LEN=48 TOS=0x08 PREC=0x00 TTL=127 ID=47354 DF PROTO=TCP SPT=1056 DPT=80 WINDOW=64296 RES=0x00 SYN URGP=0 OPT (020405B401010402) Mar 9 21:42:07 angle kernel: SuSE-FW-DROP-DEFAULT IN=eth3 OUT=eth0 SRC=192.168.1.2 DST=216.239.53.101 LEN=48 TOS=0x08 PREC=0x00 TTL=127 ID=47356 DF PROTO=TCP SPT=1056 DPT=80 WINDOW=64296 RES=0x00 SYN URGP=0 OPT (020405B401010402) I attach the result of grep -v \^# /etc/rc.config.d/firewall2.rc.config below. What is befuddling is that I'm treating eth3 exactly like other subnetworks in it, but the packets from the gigabit link are droppped! No matter which rules I comment out in the firewall script, they stop at some. Is there something wrong with the packets? -- Cheers, Alexy Khrabrov :: www.setup.org :: Age Quod Agis