Displaying 20 results from an estimated 24 matches for "dst_ip".
1997 Nov 14
0
Linux IP fragment overlap bug (fwd)
...10 sometimes... Experiment.
*/
void usage(u_char *);
u_long name_resolve(u_char *);
u_short in_cksum(u_short *, int);
void send_frags(int, u_long, u_long, u_short, u_short);
int main(int argc, char **argv)
{
int one = 1, count = 0, i, rip_sock;
u_long src_ip = 0, dst_ip = 0;
u_short src_prt = 0, dst_prt = 0;
struct in_addr addr;
fprintf(stderr, "teardrop route|daemon9\n\n");
if((rip_sock = socket(AF_INET, SOCK_RAW, IPPROTO_RAW)) < 0)
{
perror("raw socket");
exit(1);
}
if (setsockopt(rip_sock, I...
2006 Jan 02
1
routing- multiple net provider, tcp logging
Hi all,
Is any way to logs tcp connection (not packets)? something like this:
src_IP dst_Ip, srcPort, dst_port bytes_send bytes_received?
Any netfilter extension?
2 issue:
eth0------- connection 1
NET ---------gw (linux)
eth1--------connection 2
Real bandwitch on connection 1 and connection 2 is depend on different...
2023 Mar 18
1
[Bridge] [PATCH v2 net-next 6/6] selftests: forwarding: add dynamic FDB test
...(bridge_ageing_time_get br0)
+ tc qdisc add dev $swp2 clsact
+ ip link set dev br0 type bridge ageing_time $LOW_AGEING_TIME
+ bridge link set dev $swp1 learning on locked on
+
+ bridge fdb replace $mac dev $swp1 master dynamic
+ tc filter add dev $swp2 egress protocol ip pref 1 handle 1 flower \
+ dst_ip 192.0.2.2 ip_proto udp dst_port 12345 action pass
+
+ $MZ $swp1 -c 1 -p 128 -t udp "sp=54321,dp=12345" \
+ -a $mac -b `mac_get $h2` -A 192.0.2.1 -B 192.0.2.2 -q
+ tc_check_packets "dev $swp2 egress" 1 1
+ check_err $? "Packet not seen on egress after adding dynamic FDB&quo...
2023 May 09
5
[Bridge] [RFC PATCH net-next 0/5] Add layer 2 miss indication and filtering
tl;dr
=====
This patchset adds a single bit to the skb to indicate that a packet
encountered a layer 2 miss in the bridge and extends flower to match on
this metadata. This is required for non-DF (Designated Forwarder)
filtering in EVPN multi-homing which prevents decapsulated BUM packets
from being forwarded multiple times to the same multi-homed host.
Background
==========
In a typical EVPN
2023 May 18
5
[Bridge] [PATCH net-next 0/5] Add layer 2 miss indication and filtering
tl;dr
=====
This patchset adds a single bit to the skb to indicate that a packet
encountered a layer 2 miss in the bridge and extends flower to match on
this metadata. This is required for non-DF (Designated Forwarder)
filtering in EVPN multi-homing which prevents decapsulated BUM packets
from being forwarded multiple times to the same multi-homed host.
Background
==========
In a typical EVPN
2007 Jan 23
0
iptables rules disappearing!!!
Hi all.
I have got to see a strange thing. Some of my iptables'' rules are
disaprearing after several days!!!
I have many rules like:
# iptables -t mangle -A $MYCHAIN -s $SRC_IP -d $DST_IP -j MARK
--set-mark $MARK
for classifying traffic for shaping, total about 100 rules with
different 20 marks, and rules like
# iptables -A FORWARD -m mark --mark $MARK
for accounting shaping classes, total 20 rules (for all marks). The are
also many other filtering and nat rules.
Some of the mar...
2007 Mar 13
1
Problem
Hello.
I am trying to get multi paths running, i.e I want to specify 2 paths
from a particular node to another.
To test this, I am setting up the following scenario:
I create 2 tap devices
tap0 = 10.1.1.1/32 netmask 255.255.255.0
tap1 = 10.2.2.2/32 netmask 255.255.255.0
I then issue the route command:
ip route add 10.3.3.3/32 nexthop via 10.1.1.2 nexthop via 10.2.2.3
The route table
2005 Jul 05
1
Re: LARTC Digest, Vol 5, Issue 6
I''m not an expert, but I can tell you that when traffic shaping on a
router, you can just shape egress both ways and not mess with imq. My
script is at
http://www.stardotstar.org/?page_id=63
The basis are the following 2 lines where UPDEV is ppp0 and DOWNDEV is
eth0 in your case.
tc qdisc add dev ${UPDEV} root handle 1: htb default 100 r2q 1
tc qdisc add dev ${DOWNDEV} root handle 1:
2023 Mar 20
1
[Bridge] [PATCH v2 net-next 6/6] selftests: forwarding: add dynamic FDB test
...tc qdisc add dev $swp2 clsact
> + ip link set dev br0 type bridge ageing_time $LOW_AGEING_TIME
> + bridge link set dev $swp1 learning on locked on
> +
> + bridge fdb replace $mac dev $swp1 master dynamic
> + tc filter add dev $swp2 egress protocol ip pref 1 handle 1 flower \
> + dst_ip 192.0.2.2 ip_proto udp dst_port 12345 action pass
> +
> + $MZ $swp1 -c 1 -p 128 -t udp "sp=54321,dp=12345" \
> + -a $mac -b `mac_get $h2` -A 192.0.2.1 -B 192.0.2.2 -q
Packets should be injected via $h1, not $swp1. See other test cases in
this file.
> + tc_check_packets &quo...
2016 Jul 04
2
[PATCH] core/lwip: Avoid immediate reuse of UDP port numbers
...1 file changed, 33 insertions(+), 24 deletions(-)
diff --git a/core/lwip/src/core/udp.c b/core/lwip/src/core/udp.c
index 4596ba2..68e7f48 100644
--- a/core/lwip/src/core/udp.c
+++ b/core/lwip/src/core/udp.c
@@ -679,6 +679,37 @@ udp_sendto_if_chksum(struct udp_pcb *pcb, struct pbuf *p, ip_addr_t *dst_ip,
}
/**
+ * A nastly hack featuring 'goto' statements that allocates a
+ * new UDP local port. Based on equivalent code in tcp_new_port()
+ *
+ * @return a new (free) local UDP port number
+ */
+static u16_t
+udp_new_port(void)
+{
+ struct udp_pcb *pcb;
+#ifndef UDP_LOCAL_PORT_RANGE_ST...
2023 Mar 26
1
[Bridge] [PATCH v2 net-next 6/6] selftests: forwarding: add dynamic FDB test
On Mon, Mar 20, 2023 at 10:44, Ido Schimmel <idosch at nvidia.com> wrote:
>> + $MZ $swp1 -c 1 -p 128 -t udp "sp=54321,dp=12345" \
>> + -a $mac -b `mac_get $h2` -A 192.0.2.1 -B 192.0.2.2 -q
>> + tc_check_packets "dev $swp2 egress" 1 1
>> + check_fail $? "Dynamic FDB entry did not age out"
>
> Shouldn't this be check_err()? After
2023 Mar 28
2
[Bridge] [PATCH v2 net-next 6/6] selftests: forwarding: add dynamic FDB test
...K ]
TEST: Locked port dyn FDB [FAIL]
Packet not seen on egress after adding dynamic FDB
Fixed by:
```
@@ -336,7 +337,7 @@ locked_port_dyn_fdb()
tc filter add dev $swp2 egress protocol ip pref 1 handle 1 flower \
dst_ip 192.0.2.2 ip_proto udp dst_port 12345 action pass
- $MZ $swp1 -c 1 -p 128 -t udp "sp=54321,dp=12345" \
+ $MZ $h1 -c 1 -p 128 -t udp "sp=54321,dp=12345" \
-a $mac -b `mac_get $h2` -A 192.0.2.1 -B 192.0.2.2 -q
tc_check_packets "dev $swp2...
2007 Apr 18
33
[RFC PATCH 00/33] Xen i386 paravirtualization support
Unlike full virtualization in which the virtual machine provides
the same platform interface as running natively on the hardware,
paravirtualization requires modification to the guest operating system
to work with the platform interface provided by the hypervisor.
Xen was designed with performance in mind. Calls to the hypervisor
are minimized, batched if necessary, and non-critical codepaths
2007 Apr 18
24
[patch 00/24] Xen-paravirt_ops: Xen guest implementation for paravirt_ops interface
Hi Andi,
This patch series implements the Linux Xen guest as a paravirt_ops
backend. The features in implemented this patch series are:
* domU only
* UP only (most code is SMP-safe, but there's no way to create a new vcpu)
* writable pagetables, with late pinning/early unpinning
(no shadow pagetable support)
* supports both PAE and non-PAE modes
* xen hvc console (console=hvc0)
*
2007 Apr 18
24
[patch 00/24] Xen-paravirt_ops: Xen guest implementation for paravirt_ops interface
Hi Andi,
This patch series implements the Linux Xen guest as a paravirt_ops
backend. The features in implemented this patch series are:
* domU only
* UP only (most code is SMP-safe, but there's no way to create a new vcpu)
* writable pagetables, with late pinning/early unpinning
(no shadow pagetable support)
* supports both PAE and non-PAE modes
* xen hvc console (console=hvc0)
*
2007 Apr 18
24
[patch 00/24] Xen-paravirt_ops: Xen guest implementation for paravirt_ops interface
Hi Andi,
This patch series implements the Linux Xen guest as a paravirt_ops
backend. The features in implemented this patch series are:
* domU only
* UP only (most code is SMP-safe, but there's no way to create a new vcpu)
* writable pagetables, with late pinning/early unpinning
(no shadow pagetable support)
* supports both PAE and non-PAE modes
* xen hvc console (console=hvc0)
*
2007 Apr 18
25
[patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface
Hi Andi,
This patch series implements the Linux Xen guest in terms of the
paravirt-ops interface. The features in implemented this patch series
are:
* domU only
* UP only (most code is SMP-safe, but there's no way to create a new vcpu)
* writable pagetables, with late pinning/early unpinning
(no shadow pagetable support)
* supports both PAE and non-PAE modes
* xen console
* virtual
2007 Apr 18
25
[patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface
Hi Andi,
This patch series implements the Linux Xen guest in terms of the
paravirt-ops interface. The features in implemented this patch series
are:
* domU only
* UP only (most code is SMP-safe, but there's no way to create a new vcpu)
* writable pagetables, with late pinning/early unpinning
(no shadow pagetable support)
* supports both PAE and non-PAE modes
* xen console
* virtual
2007 Apr 18
25
[patch 00/21] Xen-paravirt: Xen guest implementation for paravirt_ops interface
Hi Andi,
This patch series implements the Linux Xen guest in terms of the
paravirt-ops interface. The features in implemented this patch series
are:
* domU only
* UP only (most code is SMP-safe, but there's no way to create a new vcpu)
* writable pagetables, with late pinning/early unpinning
(no shadow pagetable support)
* supports both PAE and non-PAE modes
* xen console
* virtual
2007 Apr 18
48
[RFC PATCH 00/35] Xen i386 paravirtualization support
Unlike full virtualization in which the virtual machine provides
the same platform interface as running natively on the hardware,
paravirtualization requires modification to the guest operating system
to work with the platform interface provided by the hypervisor.
Xen was designed with performance in mind. Calls to the hypervisor
are minimized, batched if necessary, and non-critical codepaths