Sponsored Content
Full Discussion: iptables Local Lan Issues
Special Forums Cybersecurity iptables Local Lan Issues Post 302823717 by DGPickett on Wednesday 19th of June 2013 04:53:33 PM
Old 06-19-2013
Somewhere there should be a log you can tap or turn on to see what rule is stopping which packet.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

why i have local.profile, local.cshrc,local.login instead of .profile, .login ?

Hello again ! Thanks for response of my first question. there is my second quesiton why i have local.profile instead of .profile file ? my all files in pwd shoes local. before any file. is anybody can tell me about that ? Thanks Abid Malik (5 Replies)
Discussion started by: abidmalik
5 Replies

2. UNIX for Dummies Questions & Answers

Iptables, samba for bigger LAN

Hey! Iam going to set up a bigger LAN.Server have 4 network adapters. -----------*0---------- | | | | ----*1-----*2-----*3- Network adapret *0 will be for DSL, *1 for like 30 computers windows xp installed on,*1 will have to... (1 Reply)
Discussion started by: net555
1 Replies

3. Solaris

How to configure private LAN and coporate LAN on the same machine-Solaris10

Hi , I am trying to configure a private LAN and corporate LAN on the same machien on Solaris 10. How can I achieve this? Thanks (1 Reply)
Discussion started by: deedee
1 Replies

4. IP Networking

Local Lan, no-ip directed DNS forward, surf within lan

Hi, We have a website running on a local centos 5.4 surfer, static IP. The domain.com uses no-ip.com to take care of the DNS, it forwards all to my server. My router receives the port 80 call, routes it to my server and the world can see domain.com perfectly fine. However, we cannot see... (3 Replies)
Discussion started by: lawstudent
3 Replies

5. AIX

Do I need to configure my local windows to FTP files from local windows to a UNIX AIX server?

Hi Friends, I have this script for ftping files from AIX server to local windows xp. #!/bin/sh HOST='localsystem.net' USER='myid_onlocal' PASSWD='mypwd_onlocal' FILE='file.txt' ##This is a file on server(AIX) ftp -n $HOST <<END_SCRIPT quote USER $USER quote PASS $PASSWD put $FILE... (1 Reply)
Discussion started by: rajsharma
1 Replies

6. Red Hat

Different hostnames with reboot while lan cable, no lan cable

I am facing strange problem regarding hostname on my Linux(2.6.18-164.el5xen x86_64 GNU/Linux), the hostname changes if reboot with lan cable and with NO lan cable Reboot with lan cable: The hostname is ubunut Unable to connect Oracle database using sqlplus some times database is not... (2 Replies)
Discussion started by: LinuxLearner
2 Replies

7. UNIX for Dummies Questions & Answers

Routing issue - local vs LAN

hi guys suse 11 SP1 x64 I have a server (4 NIC ports 192.168.100.100-103) that connects point to point to a storage device (same thing 4 ports 192.168.110.100-113) but this server connects to normal LAN 10.6.100.x - gateway 10.6.100.1 the issue is when testing connectivity to the storage... (7 Replies)
Discussion started by: karlochacon
7 Replies

8. Shell Programming and Scripting

Block local and remote port with iptables - Script BASH

Hello I'm beginner in the linux scripting and i would like to get help. I want to create a script that can block one or more Port even see all the TCP port. The ports must be blocked even when starting my machine. Of course requires a second script which will allow the ports that you want to... (0 Replies)
Discussion started by: houstaf
0 Replies

9. Red Hat

iptables applied in local machine, can't ssh remote machine after chain changed to DROP

I want to SSH to 192.168.1.15 Server from my machine, my ip was 192.168.1.99 Source Destination was UP, with IP 192.168.1.15. This is LAN Network there are 30 Machine's Connected to the network and working fine, I'm Playing around the local machine's because I need to apply the same rules in... (2 Replies)
Discussion started by: babinlonston
2 Replies

10. IP Networking

Debugging NAT / prerouting issues (iptables)

Hello, Recently I discovered an issue with packet routing in the latest Android releases (4.4+ KitKat & Lollipop). It seems that the problem Android specific, but essentially it comes from the Linux kernel. I already filed a bug report to Google. You can see the details by searching for... (0 Replies)
Discussion started by: Vladislav
0 Replies
ipmon(1M)						  System Administration Commands						 ipmon(1M)

NAME
ipmon - monitors /dev/ipl for logged packets SYNOPSIS
ipmon [-abDFhnpstvxX] [-N device] [ [o] [NSI]] [-O [NSI]] [-P pidfile] [-S device] [-f device] [filename] DESCRIPTION
The ipmon command is part of a suite of commands associated with the Solaris IP Filter feature. See ipfilter(5). The ipmon command opens /dev/ipl for reading and awaits data to be saved from the packet filter. The binary data read from the device is reprinted in human readable form. However, IP addresses are not mapped back to hostnames, nor are ports mapped back to service names. The output goes to standard output, by default, or a filename, if specified on the command line. Should the -s option be used, output is sent instead to syslogd(1M). Messages sent by means of syslog have the day, month, and year removed from the message, but the time (including microseconds), as recorded in the log, is still included. Messages generated by ipmon consist of whitespace-separated fields. Fields common to all messages are: o The date of packet receipt. This is suppressed when the message is sent to syslog. o The time of packet receipt. This is in the form HH:MM:SS.F, for hours, minutes, seconds, and fractions of a second (which can be several digits long). o The name of the interface on which the packet was processed, for example, ib1. o The group and rule number of the rule, for example, @0:17. These can be viewed with ipfstat -in for input rules or ipfstat -in for output rules. See ipfstat(1M). o The action: p for passed, b for blocked, s for a short packet, n did not match any rules, or L for a log rule. o The addresses. This is actually three fields: the source address and port (separated by a comma), the symbol ->, and the desti- nation address and port. For example: 209.53.17.22,80 -> 198.73.220.17,1722. o PR followed by the protocol name or number, for example, PR tcp. o len followed by the header length and total length of the packet, for example, len 20 40. If the packet is a TCP packet, there will be an additional field starting with a hyphen followed by letters corresponding to any flags that were set. See ipf.conf(4) for a list of letters and their flags. If the packet is an ICMP packet, there will be two fields at the end, the first always being icmp, the next being the ICMP message and sub- message type, separated by a slash. For example, icmp 3/3 for a port unreachable message. OPTIONS
The following options are supported: -a Open all of the device logfiles for reading log entries. All entries are displayed to the same output device (stderr or syslog). -b For rules which log the body of a packet, generate hex output representing the packet contents after the headers. -D Cause ipmon to turn itself into a daemon. Using subshells or backgrounding of ipmon is not required to turn it into an orphan so it can run indefinitely. -f device Specify an alternative device/file from which to read the log information for normal IP Filter log records. -F Flush the current packet log buffer. The number of bytes flushed is displayed, even if the result is zero. -h Displays usage information. -n IP addresses and port numbers will be mapped, where possible, back into hostnames and service names. -N device Set the logfile to be opened for reading NAT log records from or to device. -o letter Specify which log files from which to actually read data. N, NAT logfile; S, state logfile; I, normal IP Filter logfile. The -a option is equivalent to using -o NSI. -O letter Specify which log files you do not wish to read from. This is most commonly used in conjunction with the -a. Letters available as parameters are the same as for -o. -p Cause the port number in log messages always to be printed as a number and never attempt to look it up. -P pidfile Write the PD of the ipmon process to a file. By default this is /var/run/ipmon.pid. -s Packet information read in will be sent through syslogd rather than saved to a file. The default facility when compiled and installed is local0. The following levels are used: LOG_INFO Packets logged using the log keyword as the action rather than pass or block. LOG_NOTICE Packets logged that are also passed. LOG_WARNING Packets logged that are also blocked. LOG_ERR Packets that have been logged and that can be considered "short". -S device Set the logfile to be opened for reading state log records from or to device. -t Read the input file/device in the way performed by tail(1). -v Show TCP window, ack, and sequence fields -x Show the packet data in hex. -X Show the log header record data in hex. FILES
o /dev/ipl o /dev/ipnat o /dev/ipstate ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWipfu | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ SEE ALSO
ipf(1M), ipfstat(1M), ipnat(1M), attributes(5), ipfilter(5) DIAGNOSTICS
ipmon expects data that it reads to be consistent with how it should be saved and aborts if it fails an assertion which detects an anomaly in the recorded data. SunOS 5.11 3 Apr 2008 ipmon(1M)
All times are GMT -4. The time now is 05:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy