Sponsored Content
Special Forums IP Networking Same IP | Different port | Different MAC Post 302888642 by @dagio on Sunday 16th of February 2014 10:42:19 AM
Old 02-16-2014
Same IP | Different port | Different MAC

Hello all,

I meet a "strange" situation, at least for me, and i want your opinion.
I have a node used as SIP B2BUA (node A) and i have the following issue.
SIP messages does not reach a client node (node B) but ICMP do.
I see in the pcap that SIP and ICMP messages have different destination MAC address. Only ICMP messages have destination MAC address the MAC of node B.
OS: rhel 6.2
arp table show the MAC of node B.

Any idea?What should i check??

Thanks in advance!

Last edited by @dagio; 02-16-2014 at 11:54 AM..
 

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Sunblade shows 2 MAC address on same port

Please, can someone tell me why my SunBlade would be showing 2 different but similar MAC addresses on the same port on the Switch? The switch shows all other Workstations with 1 MAC on each port, but the SunBlade is showing 2. Thanks in advance for any insight.... (1 Reply)
Discussion started by: GoneCrazy
1 Replies

2. Solaris

How to enable Serial port on ILOM, when Network Port is enabled in parallel

Hi Everyone, In my environment, I have few T5220. On the iLOM Management Card, I have both Network and Serial port are cabled, I don't have any issues while I try to connect using Network Management port, but when I try to connect the serial port for the same server which is actually connected... (3 Replies)
Discussion started by: bobby320
3 Replies

3. IP Networking

Tcp ip port open but no such process (merged: Release A Port)

i want to kill a tcp connection by killing its pid with netstat -an i got the tcp ip connection on port 5914 but when i type ps -a or ps-e there is not such process running on port 5914 is it possible that because i do not log on with proper user account i can not see that process running? (30 Replies)
Discussion started by: alinamadchian
30 Replies

4. Solaris

Cabling and adapters to communicate to service processor serial port from Windows PC with USB port.

Hello, I have an unloaded T5140 machine and want to access the ILOM for the first time and subsequently the network port after that., and then load Solaris 10 the final January 2011 build. The first part is what confuses me -the cabling. I am coming from a Windows machine (w/appropriate... (5 Replies)
Discussion started by: joboy
5 Replies

5. Solaris

How to find port number wwn of particular port on dual port HBA,?

please find the below o/p for your reference bash-3.00# fcinfo hba-port HBA Port WWN: 21000024ff295a34 OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 375-3356-02 Firmware Version: 05.03.02 FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies

6. UNIX for Beginners Questions & Answers

Bash script, find the next closed (not in use) port from some port range.

hi, i would like to create a bash script that check which port in my Linux server are closed (not in use) from a specific range, port range (3000-3010). the print output need to be only 1 port, and it will be nice if the output will be saved as a variable or in same file. my code is: ... (2 Replies)
Discussion started by: yossi
2 Replies
Net::SIP::Dropper::ByIPPort(3pm)			User Contributed Perl Documentation			  Net::SIP::Dropper::ByIPPort(3pm)

NAME
Net::SIP::Dropper::ByIPPort - drops SIP messages based on senders IP and port SYNOPSIS
use Net::SIP::Dropper::ByIPPort; my $drop_by_ipport = Net::SIP::Dropper::ByIPPort->new( database => '/path/to/database.drop', methods => [ 'REGISTER', '...', '' ], attempts => 10, interval => 60, ); my $dropper = Net::SIP::Dropper->new( cb => $drop_by_ipport ); my $chain = Net::SIP::ReceiveChain->new([ $dropper, ... ]); DESCRIPTION
With "Net::SIP::Dropper::ByIPPort" one can drop packets, if too much packets are received from the same IP and port within a specific interval. This is to stop bad behaving clients. CONSTRUCTOR
new ( ARGS ) ARGS is a hash with the following keys: database Optional file name of database or callback for storing/retrieving the data. If it is a callback it will be called with "$callback->(\%data)" to retrieve the data (%data will be updated) and "$callback->(\%data,true)" to save the data. No return value will be expected from the callback. %data contains the number of attempts from a specific IP, port at a specific time in the following format: "$data{ip}{port}{time} = count" attempts After how many attempts within the specific interval the packet will be dropped. Argument is required. interval The interval for attempts. Argument is required. methods Optional argument to restrict dropping to specific methods. Is array reference of method names, if one of the names is empty also responses will be considered. If not given all packets will be checked. METHODS
run ( PACKET, LEG, FROM ) This method is called as a callback from the Net::SIP::Dropper object. It returns true if the packet should be dropped, e.g. if there are too much packets from the same ip,port within the given interval. expire This method is called from within "run" but can also be called by hand. It will expire all entries which are outside of the interval. savedb This method is called from "expire" and "run" for saving to the database after changes, but can be called by hand to, useful if you made manual changes using the "data" method. data This method gives access to the internal hash which stores the attempts. An attempt from a specific IP and port and a specific time (as int, like time() gives) will be added to "$self->data->{ip}{port}{time}". By manually manipulating the hash one can restrict a specific IP,port forever (just set time to a large value and add a high number of attempts) or even restrict access for the whole IP (all ports) until time by using a port number of 0. After changes to the data it is advised to call "savedb". perl v5.14.2 2012-06-26 Net::SIP::Dropper::ByIPPort(3pm)
All times are GMT -4. The time now is 11:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy