gsoc/mails/20210820-Re_GSoC Port Forwarding-1111.html

33 lines
2.8 KiB
HTML
Raw Normal View History

2021-10-19 18:22:56 +02:00
<html>
<head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>Re: GSoC Port Forwarding</title>
<link rel="important stylesheet" href="">
<style>div.headerdisplayname {font-weight:bold;}
</style></head>
<body>
<table border=0 cellspacing=0 cellpadding=0 width="100%" class="header-part1"><tr><td><div class="headerdisplayname" style="display:inline;">Oggetto: </div>Re: GSoC Port Forwarding</td></tr><tr><td><div class="headerdisplayname" style="display:inline;">Mittente: </div>Giulio <giulio@gmx.com></td></tr><tr><td><div class="headerdisplayname" style="display:inline;">Data: </div>20/08/2021, 03:20</td></tr></table><table border=0 cellspacing=0 cellpadding=0 width="100%" class="header-part2"><tr><td><div class="headerdisplayname" style="display:inline;">A: </div>Marek Marczykowski-Górecki &lt;marmarek@invisiblethingslab.com&gt;</td></tr><tr><td><div class="headerdisplayname" style="display:inline;">CC: </div>Frédéric Pierret &lt;frederic.pierret@qubes-os.org&gt;</td></tr></table><br>
<div class="moz-text-flowed" style="font-family: -moz-fixed; font-size: 14px;" lang="x-unicode">Hi,
<br>I have made a lot of changes in the core-agent-linux code in order to
fix minor bugs which emerged during manual testing as well as improve
the overall logic robustness.
<br>Unfortunately, I am still having some troubles in debugging why the
incoming packes in sys-net are not reaching the next hop (sys-firewall,
10.137.0.6). Tcpdump and nft trace monitor are totally silent in
sys-firewall, which I guess confirms the 0 counter as shown in the
"rules" screenshot (which is of sys-net). Tracing the packets seems to
show a succesful opeartion:
<br>1) The incoming packet is accepted
<br>2) The packet is forwarded to the vif72.0 interface succesfully
<br>
<br>The trace is the result of the "ssh <a class="moz-txt-link-abbreviated" href="mailto:test@192.168.137.128">test@192.168.137.128</a>" command, which
is the ip of ens6 in sys-net
<br>
<br>I will continue to try to debug the problem tomorrow, but still I am not
really sure what to check more...
<br>
<br>
<br>Cheers
<br>Giulio
<br></div><BR><DIV CLASS="moz-attached-image-container"><IMG CLASS="moz-attached-image" shrinktofit="yes" SRC="EmbeddedImages-1/0.jpg"></DIV><BR><DIV CLASS="moz-attached-image-container"><IMG CLASS="moz-attached-image" shrinktofit="yes" SRC="EmbeddedImages-1/1.jpg"></DIV><br><hr><br><div style="font-size:12px;color:black;"><img src="data:image/gif;base64,R0lGODdhDwAPAOMAAP///zEwYmJlzQAAAPr6+vv7+/7+/vb29pyZ//39/YOBg////////////////////ywAAAAADwAPAAAESRDISUG4lQYr+s5bIEwDUWictA2GdBjhaAGDrKZzjYq3PgUw2co24+VGLYAAAesRLQklxoeiUDUI0qSj6EoH4Iuoq6B0PQJyJQIAOw==">
<ul><li><a href="Attachments-1/trace.JPG">Attachments-1/trace.JPG</li></a><li><a href="Attachments-1/rules.JPG">Attachments-1/rules.JPG</li></a></ul></div><div class='' ></div></body>
</html>