Skip to main content

Untitled

• Aug 27, 2024 •vercetti322
Loading...

More Plaintext Posts

Untitled

• Oct 8, 2025 •AustinLeath

0 likes • 1 view

root@pm3:~# ping -M do -s 1366 172.31.40.218
PING 172.31.40.218 (172.31.40.218) 1366(1394) bytes of data.
1374 bytes from 172.31.40.218: icmp_seq=1 ttl=124 time=64.4 ms
1374 bytes from 172.31.40.218: icmp_seq=2 ttl=124 time=62.8 ms
1374 bytes from 172.31.40.218: icmp_seq=3 ttl=124 time=62.8 ms

--- 172.31.40.218 ping statistics ---
3 packets transmitted, 3 received, +1 errors, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 62.755/63.295/64.358/0.751 ms

------------------------------------------------------------------------------------------

root@pm3:~# ping -M do -s 1370 172.31.40.218
PING 172.31.40.218 (172.31.40.218) 1370(1398) bytes of data.
1378 bytes from 172.31.40.218: icmp_seq=1 ttl=124 time=64.0 ms
1378 bytes from 172.31.40.218: icmp_seq=2 ttl=124 time=62.8 ms
1378 bytes from 172.31.40.218: icmp_seq=3 ttl=124 time=62.7 ms

--- 172.31.40.218 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 62.675/63.150/63.983/0.590 ms

------------------------------------------------------------------------------------------

root@pm3:~# ping -M do -s 1372 172.31.40.218
PING 172.31.40.218 (172.31.40.218) 1372(1400) bytes of data.
1380 bytes from 172.31.40.218: icmp_seq=1 ttl=124 time=63.9 ms
1380 bytes from 172.31.40.218: icmp_seq=2 ttl=124 time=62.7 ms
1380 bytes from 172.31.40.218: icmp_seq=3 ttl=124 time=62.5 ms

--- 172.31.40.218 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 62.501/63.030/63.936/0.643 ms

------------------------------------------------------------------------------------------

root@pm3:~# ping -M do -s 1373 172.31.40.218
PING 172.31.40.218 (172.31.40.218) 1373(1401) bytes of data.
ping: sendmsg: Message too long
ping: sendmsg: Message too long
ping: sendmsg: Message too long

--- 172.31.40.218 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2076ms

default netplan

• Nov 18, 2022 •AustinLeath

0 likes • 0 views

# This is the network config written by 'subiquity'
network:
  ethernets:
    enp0s3:
      dhcp4: yes
      nameservers:
          addresses: [8.8.8.8,8.8.4.4]
  version: 2

Untitled

• Aug 17, 2025 •shekhar771

0 likes • 8 views

dzdzvcsd,

Untitled

• Jun 1, 2025 •abeRodrz99

0 likes • 3 views

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Document</title>
</head>
<body>
    
</body>
</html>

x86 MASM C Linking

• Jun 30, 2021 •LeifMessinger

0 likes • 2 views

;Main.asm
.386
.model small,c		;This bit is important, I think.
.stack 1000h

.data
	hello db "Hello world!",0

.code
	;includelib libucrt.lib						;All this shit is already here if you have a C object file
	includelib legacy_stdio_definitions.lib		;Except for this. Basically printf, puts etc
	;includelib libcmt.lib
	;includelib libvcruntime.lib ;Visual Studio exception handling and type checking. Not needed otherwise

extrn printf:near ;Extern everything you are gonna use from the c obj files
extrn plusTwo:near
extrn exit:near

public plusOne ;Have to declare it public for the linker to see it. In NASM, it's .globl or global
plusOne proc ;Our int plusOne(int) function.
	pop eax ;Parameters are stored on the stack.
	add eax, 1
	ret ;eax is whatever is returned from functions. Also why you can only return one thing.
plusOne endp

public main
main proc
	push offset hello
	call printf
	push	1
	call	plusTwo
	push 0
	call exit
main endp

end		;End of file, not program

//bruh.c
//#include <stdio.h>					Has to be included with "includelib legacy_stdio_definitions.lib" in the asm file for some reason.
//int printf(const char* format, ...);

extern int plusOne(int); //Extern everything you are gonna use from the asm obj files

int plusTwo(int num) {
	return plusOne(plusOne(num)); //Plus one is defined in the assembly.
}

Untitled

• Oct 20, 2025 •a.povolotskiy-279a

0 likes • 1 view

var obj = {
    prop: 1,
    getProp: function(){
         return function() { console.log(this.prop) };
    },
};

obj.getProp()();