I get the following in my VPS logs
Neither the SRC nor the DST are mine. After googling around I found this explanation here and came to know that port 17500 has to do with dropbox's broadcasting and that I can get rid of it by disabling LANSync in the application or uninstalling it altogether. Still, I'm getting the error in my log file. Any ideas on this would be appreciated.
ajax20ajax20
2 Answers
You can't 'get rid of' these so easily. Diference between estimate and repair order. You're seeing this because other customers of your VPS provider are running Dropbox LAN sync.
Personally I just drop traffic from other nodes in the same subnet without bothering to log it. For example, if your VPS's IP address is 203.0.113.148 and prefix 24:
Michael Hampton♦Michael Hampton181k2828 gold badges337337 silver badges668668 bronze badges
As to remove them from you'r log (and drop/reject/accept them) :
SvennDSvennD
Not the answer you're looking for? Browse other questions tagged vpslog-files or ask your own question.
Ben Pfaff blp at nicira.com
Thu Jan 22 16:54:38 UTC 2015
Previous message: [ovs-discuss] Flow Matching with port ranges.
Next message: [ovs-discuss] ovs installation - debian
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Jan 22, 2015 at 05:34:15PM +0530, nitish nagesh wrote:
Thu Jan 22 16:54:38 UTC 2015
Previous message: [ovs-discuss] Flow Matching with port ranges.
Next message: [ovs-discuss] ovs installation - debian
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Jan 22, 2015 at 05:34:15PM +0530, nitish nagesh wrote:
I am trying to add L4 port range matching capability to our switch
(internally uses OVS code). I have used experimenter match fields in the
Flow Mod to get these. Once i receive them, after parsing the experimenter
OXM's, i store them in the 'flow' structure. I have added new fields to
store them, something like this:
(internally uses OVS code). I have used experimenter match fields in the
Flow Mod to get these. Once i receive them, after parsing the experimenter
OXM's, i store them in the 'flow' structure. I have added new fields to
store them, something like this:
Udp Dst Port 0 Call
struct flow {
.
.
.
struct port_range pr;
.
.
};
.
.
.
struct port_range pr;
.
.
};
struct port_range
{
ovs_be16 begin;
ovs_be16 end;
};
{
ovs_be16 begin;
ovs_be16 end;
};
Note that when i receive a port range in the flow-mod, i would NOT
populate the tp_src or tp_dst fields.
populate the tp_src or tp_dst fields.
Udp Dst Port 0 Device
However i am facing issues when it comes to matching packets to this rule.
As my understanding goes, OVS creates a hash of all the field values in the
'flow' structure as received in the flow-mod and stores them in the
classifier. A network packet would never match this rule, as it doesnt have
a port-range and hence the hash would always fail.
As my understanding goes, OVS creates a hash of all the field values in the
'flow' structure as received in the flow-mod and stores them in the
classifier. A network packet would never match this rule, as it doesnt have
a port-range and hence the hash would always fail.
I was thinking if there's an easy way to achieve this with minimal
changes to the code. My knowledge about OVS code is limited, hence
requesting for help. Please comment.
changes to the code. My knowledge about OVS code is limited, hence
requesting for help. Please comment.
Implementing port ranges this way is kind of an uphill battle. I'd
suggest using multiple flows that bitwise match on the tp_src or tp_dst
fields, as described in ovs-ofctl(8):
suggest using multiple flows that bitwise match on the tp_src or tp_dst
fields, as described in ovs-ofctl(8):
I have a system that is running on windows. I have in that system a process that waits for another process on the same machine for a udp message. The message itself is not important (garbage), but the important thing is that I got the event of the message itself.
The problem is that it seems that I get from another local program a UDP message and I don't know from where. I added information about the sender in the recieved UDP message. I see that I get message from valid local port but also from the addres 0.0.0.0 .
I can't understand the 0.0.0.0 . Does anyone has an idea ?
skaffman349k8888 gold badges745745 silver badges730730 bronze badges
Boris RaznikovBoris Raznikov1,04088 gold badges2525 silver badges4949 bronze badges
2 Answers
A computer without an assigned IP address could send such packet, even across the network - see e.g. a similar mechanism in DHCP, where the DHCP discovery packet is sent with source address of 0.0.0.0
On a local computer, could this be that the packet is sent (and received) on an interface that is up but without an IP address?
Also, this can mean 'broadcast' - if this article on e2 is correct, it is a deprecated method of making a broadcast packet, but apparently it was never removed.
PiskvorPiskvor73.3k4141 gold badges159159 silver badges210210 bronze badges
Because it is a udp message and using async type, when reading messages that arrive from the other program I can't know when stop reading, when I get reading the message and I get 0.0.0.0 it means I read everything from the UDP buffer from OS.
Boris RaznikovBoris Raznikov1,04088 gold badges2525 silver badges4949 bronze badges