search for: kurkiewicz

Still not working I really have to change 21 port on 80 port, my friend has only www and mail on his netwok. He has rigorous admin. I have done : !! in proftpd.cof : # Port 21 is the standard FTP port. Port 80 !! in /etc/shorewall/modules: loadmodule ip_conntrack_ftp ports=21,80 loadmodule ip_nat_ftp ports=21,80 AFTER THAT AND RESTARTTING PROFTP AND

I want to talk with my friend with microfon with program speak freally. He has firewall (shorewall) on his linux serwer and has other computer as a client and I have the same network connected winh internet. This program use port 2074 to communicate. We have done something like this : DNAT net local:192.168.1.6 tcp 2074 DNAT net local:192.168.1.6 udp 2074 on linux serwer with shorewall (rules

> Yes -- just leave the setting of MACLIST_DISPOSITION=REJECT and any request > from interfaces with the ''maclist'' option will be rejected if there isn''t a > match found in the maclist file. I have wrote some IP''s and MAC''s from my network, for example : #INTERFACE MAC IP ADDRESSES (Optional)

It is working very good :) Thank You. I only need to write Interface etho in maclist file. My MAC addresses don''t neet the ~ in front of. Thanks ! Maciek -- ---- Oferta jakiej jeszcze nie by³o! Serwer www 60 MB za 99 z³ rocznie Szczegó³y: www.oferta.alpha.pl ----

I want to reject all ports to 217.17.41.0/24 for one IP 192.168.1.6 and give only WWW from 217.17.41.87 to client computer 192.168.1.6. Please help me ... I have done it in rules file : REJECT net:217.17.41.0/24 local:192.168.1.6 tcp REJECT local:192.168.1.6 net:217.17.41.0/24 tcp REJECT net:217.17.41.0/24 local:192.168.1.6 udp REJECT local:192.168.1.6 net:217.17.41.0/24 udp ACCEPT

I have blocked all high ports used by kazza but new kazza is going also now. It is going on 80 port, it is possible in shorewall to block kazza ? Mayby I should write some rules for 80 port ? Maciek -- ---- Oferta jakiej jeszcze nie by³o! Serwer www 60 MB za 99 z³ rocznie Szczegó³y: www.oferta.alpha.pl ----

I have changed my port in poftpd on 80 because I have to. But after proftpd restart and shorewall restart ftp serwer not working on 80 (on 21 also not - I chave changed port numer in proftpd.conf). I think that I have also change in my shorewall configuration ? -- ---- Oferta jakiej jeszcze nie by³o! Serwer www 60 MB za 99 z³ rocznie Szczegó³y: www.oferta.alpha.pl ----

I hae 30 computers on my nerwork, I have shorewall, I want to link each IP number with MAC address ... my friend did it in itpables, I have shorewall and I don''t know where I can do it and how do it ... best wishes from Poland Maciek p.s. AND VERY IMPORTANT - after "linking" IP with MAC I want to reject all other IP''s -- ---- Oferta jakiej jeszcze nie by³o! Serwer

Setting up MAC Verification on eth0... Error: Interface eth0 must be up before Shorewall can start my : /etc/shorewall/shorewall.conf: MACLIST_DISPOSITION=REJECT MACLIST_LOG_LEVEL=info interfaces: #ZONE INTERFACE BROADCAST OPTIONS net ppp0 217.96.90.242 noping loc eth0 255.255.255.0 routestopped,maclistmaclist: maclist: #INTERFACE MAC IP

Hello, I have a local network with gateway (192.168.1.1) to internet, it is computer with slackware and shorewall. I have ftp serwer on my gateway computer, serwer is on 21 port and it is accesable for external and internal computers ( from internet and local network ). Today I have installed Serwer on my local machine (192.168.1.6) on port 22019. The serwer is accesable from loal computers in

Hello I have DSL 2000 (2048 kbit/s download and 256 kbit/s upload) I have ping to fast sites very high: 64 bytes from w2.rc.vip.scd.yahoo.com (66.94.234.13): icmp_seq=3 ttl=50 time=2185 ms 64 bytes from w2.rc.vip.scd.yahoo.com (66.94.234.13): icmp_seq=4 ttl=50 time=1983 ms 64 bytes from w2.rc.vip.scd.yahoo.com (66.94.234.13): icmp_seq=5 ttl=50 time=1826 ms and I know why. I have 2 interfaces:

root@hades:/mnt/big/dane# shorewall reset Processing /etc/shorewall/params ... Processing /etc/shorewall/shorewall.conf... lockfile: Sorry, giving up on "/var/lib/shorewall/lock" Shorewall Counters Reset After shorewall restart it is staying long time and giving after that such info "Sorry, giving ... " Why ? I have 1.4.5 shorewall -- ---- Serwery www od 7 zl m-c

Version? 1.4.2 >>>> shorewall don''t start. "unknown protocol >>>> `net'' specified >>And you put that in your rules file? yes, a put it earlier, but I have in policy file : fw net ACCEPT so from rules file it wasn''t working : REJECT fw net tcp 901 REJECT fw net udp 901 -- ---- Oferta jakiej jeszcze nie bylo!