search for: anywhere

...tap0 vif2.0 virbr0 8000.000000000000 yes Iptables output: [root@moosen ~]# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT udp -- anywhere anywhere udp dpt:domain ACCEPT tcp -- anywhere anywhere tcp dpt:domain ACCEPT udp -- anywhere anywhere udp dpt:bootps ACCEPT tcp -- anywhere anywhere tcp dpt:bootps ACCEPT udp -- anyw...

...ic iptables setup. I opened up the standard samba ports. I've listed the output of 'iptables --list' below. Any ideas? TTIA /randoms/ 'iptables --list' output : Chain INPUT (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain FORWARD (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain RH-Firewall-1-INPUT (2 references) target...

Hi all, I have done some extensive searching, and drawn a blank so far... Nothing odd is reported in samba logs, or in the syslog file. However, if I try to play an avi straight off the samba server, on an XP client with MP10, it brings the whole deal to its knees after a few mins at the most. I have to hard reset the server. Other than this, all my other uses are flawless (game server,

This is a standard RedHat / CentOS firewall configuration, where I told it, through the standard RH setup GUI, that I want ssh and snmp allowed through. Chain INPUT (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain FORWARD (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination...

Hi, Can anybody tell me how to delete DSCP or TOS setting using iptable command. iptables --list OUTPUT --table mangle Chain OUTPUT (policy ACCEPT) target prot opt source destination DSCP tcp -- anywhere anywhere tcp spt:http DSCP s et 0x08 DSCP udp -- anywhere anywhere DSCP set 0x08 DSCP udp -- anywhere anywhere DSCP set 0x18 DSCP all -- anywhere anywhere...

...ytes 68642 pkts (dropped 0, overlimits 0) qdisc htb 1: r2q 10 default 99 direct_packets_stat 24 ver 3.16 Sent 7209229 bytes 137739 pkts (dropped 1, overlimits 364) # iptables -t mangle -L Chain PREROUTING (policy ACCEPT) target prot opt source destination IMQ all -- anywhere anywhere IMQ: todev 1 pretos all -- anywhere anywhere tcpre all -- anywhere anywhere Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source...

...as my best suspicion at first, but I now think looks ok (I've only a passable knowledge of iptables): *************************************************** [root@hoth samba]# iptables -L Chain INPUT (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT all -- 10.0.0.0/24 anywhere drop-and-log-it all -- 10.0.0.0/24 anywhere ACCEPT tcp -- anywhere anywhere tcp dpt:ftp-data ACCEPT tcp -- anywhere anywhere t...

...d it's not doing that. And when I try from another computer, I don't see anything in the logs, which made me think it was an IPTABLES issue (which it doesn't appear to be). Chain RH-Firewall-1-INPUT (2 references) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT icmp -- anywhere anywhere icmp any ACCEPT ipv6-crypt-- anywhere anywhere ACCEPT ipv6-auth-- anywhere anywhere ACCEPT udp -- anywhere 224.0.0.251 udp dpt:5353 ACCEPT udp -- anywh...

...poof rules go into the INPUT chain. Example with 1 bridge and 5 domains: ========================== [root@941e-4 ~]# ip Chain FORWARD (policy DROP 13 packets, 4302 bytes) pkts bytes target prot opt in out source destination 5329 445K ACCEPT all -- any any anywhere anywhere PHYSDEV match --physdev-in peth0 1593 272K ACCEPT all -- any any anywhere anywhere PHYSDEV match --physdev-out peth0 2 1152 ACCEPT all -- any any anywhere anywhere PHYSDEV match --p...

...e. Does anyone agree.? Perhaps I'm not understanding it as well as I think I am.? Please give your thoughts on this. Cheers. Mark Sargent. [root at localhost racket]# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain FORWARD (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain RH-Firewall-1-INPUT (2 references) target...

I can't seem to register properly with broadvoice servers. Looking at tcpdump and log files I see registrations attemtps and traffic to broadvoice, but no traffic or error messages of any kind from broadvoice. Do my rules look ok ? ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere ACCEPT icmp -- anywhere anywhere icmp any ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED ACCEPT tcp -- anywhere anywhere state RELA...

...tall Mandrake Linux 9.0 and it use shorewall. My first impression are extremily positive. But I simply can''t ping outside my machine. I verify that my route table is ok. It just cant''t ping in the same network! :( Any sugestions? # iptables -L | grep icmp ACCEPT icmp -- anywhere anywhere state NEW,RELATED,ESTABLISHED ACCEPT icmp -- anywhere anywhere icmp echo-request icmpdef icmp -- anywhere anywhere ACCEPT icmp -- anywhere anywhere icmp echo-request ACCEPT icmp -- anywhere...

...PTABLES_SAVE_COUNTER="no" # Numeric status output # Value: yes|no, default: no #IPTABLES_STATUS_NUMERIC="no" ----------------------------------------- the command iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT all -- 200.55.135.8/29 anywhere ACCEPT all -- 172.16.0.0/24 valinor.mincex.org DROP icmp -- anywhere anywhere icmp echo-request DROP icmp -- anywhere anywhere icmp echo-request ACCEPT t...

...r, I decided to try out the suggestion Felipe sent about using system-config-securitylevel-tui to open up ports 513 and 514, but that doesn't seem to do the job, either. # iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain FORWARD (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain RH-Firewall-1-INPUT (2 references) target...

...4/ip_forward 0 [root at wcmisdlin02 ~]# /bin/echo 1 > /proc/sys/net/ipv4/ip_forward [root at wcmisdlin02 ~]# cat /proc/sys/net/ipv4/ip_forward 1 [root at wcmisdlin02 ~]# iptables --list Chain INPUT (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain FORWARD (policy ACCEPT) target prot opt source destination RH-Firewall-1-INPUT all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain RH-Firewall-1-INPUT (2 references) target...

...ifnum=0 netdev=eth0 bridge=xenbr0 "$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=xenbr1 IPTABLES (not modified by any action by me) [root at localdomain ~]# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT udp -- anywhere anywhere udp dpt:domain ACCEPT tcp -- anywhere anywhere tcp dpt:domain ACCEPT udp -- anywhere anywhere udp dpt:bootps ACCEPT tcp -- anywhere anywhere tcp dpt:bootps ACCEPT udp -- anyw...

...for password less access to both the nodes 4. I've opened ports 49152-49215 on the destination node i.e., n1. please see below. [user at n1 images]$ sudo iptables -L [sudo] password for user: Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT udp -- anywhere anywhere udp dpt:domain ACCEPT tcp -- anywhere anywhere tcp dpt:domain ACCEPT udp -- anywhere anywhere udp dpt:bootps ACCEPT tcp -- anywhere anywhere tcp dpt:bootps ACCEPT all -- anyw...

...for password less access on both the nodes 4. I've opened ports 49152-49215 on the destination node i.e., n1. please see below. [user at n1 images]$ sudo iptables -L [sudo] password for user: Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT udp -- anywhere anywhere udp dpt:domain ACCEPT tcp -- anywhere anywhere tcp dpt:domain ACCEPT udp -- anywhere anywhere udp dpt:bootps ACCEPT tcp -- anywhere anywhere tcp dpt:bootps ACCEPT all -- anyw...

...igration section of this FAQ) I managed to ssh physicalServer2 in virtualmachine1 shell. So the above red part did not explain my failure. I also open ports on physicalServer2, iptables -L shows following information: Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT udp -- anywhere anywhere udp dpt:domain ACCEPT tcp -- anywhere anywhere tcp dpt:domain ACCEPT udp -- anywhere anywhere udp dpt:bootps ACCEPT tcp -- anywhere anywhere tcp dpt:bootps ACCEPT udp -- anywhere anywhere udp dpt:domain ACCEPT tcp -- anywhere anywhere tcp dpt:domain ACCEPT udp -- anywhere anywhere udp dpt:...

I've got a test lab set up and im having problems connecting. The first problem is that it takes it a couple of tries before it actually connects the two machines. It complains about bogus data and after trying for a minute or so it connects. kill -USR1 shows that they are connected kill -USR2 only shows the local subnet, not the remote I've tried these versions without any luck: cvs