dan/liminix
1
0
Fork 5
Code
c6918fec00
liminix/tests/pppoe/getaddress.expect

47 lines
1.2 KiB
Plaintext
Raw Normal View History

automated test for pppoe
2022-09-26 09:47:29 +00:00
set timeout 60
turn run-qemu.sh script into mips-vm buildEnv command
2023-02-08 22:16:39 +00:00
spawn socat unix-connect:vm/console -
check firewall zones in pppoe test
2025-02-25 23:32:05 +00:00
expect "s6-linux-init"
automated test for pppoe
2022-09-26 09:47:29 +00:00
send "\r\n"
pppoe test: update to expect change in root's PS1
2023-03-18 19:16:27 +00:00
expect "#"
check firewall zones in pppoe test
2025-02-25 23:32:05 +00:00
send "PS1=\$(echo 'I1JFQURZIyA=' | base64 -d); stty -echo\n"
expect "#READY#"
automated test for pppoe
2022-09-26 09:47:29 +00:00
set FINISHED 0
set EXIT "1"
firewall: use extraText for zone set contents * the lua necessary is quite wordy, but it's less of a hack than post-processing the rules file with pseudo-sed to get rid of `elements = { }` lines * also switch from stop/starting the firewall service to using a signal, so that we don't go briefly offline every time a new interface appears
2025-03-09 20:42:02 +00:00
while { $FINISHED < 20 } {
check firewall zones in pppoe test
2025-02-25 23:32:05 +00:00
send "ip address show dev ppp0 | grep ppp0\n"
automated test for pppoe
2022-09-26 09:47:29 +00:00
expect {
firewall: use extraText for zone set contents * the lua necessary is quite wordy, but it's less of a hack than post-processing the rules file with pseudo-sed to get rid of `elements = { }` lines * also switch from stop/starting the firewall service to using a signal, so that we don't go briefly offline every time a new interface appears
2025-03-09 20:42:02 +00:00
"192.168.100.1" { set FINISHED 200; set EXIT 0; }
check firewall zones in pppoe test
2025-02-25 23:32:05 +00:00
"can't find device" { send_user "waiting ..." ; sleep 3 }
"DOWN" { send_user "waiting ..." ; sleep 3 }
automated test for pppoe
2022-09-26 09:47:29 +00:00
}
set FINISHED [ expr $FINISHED + 1 ]
}
firewall: use watch-outputs to track changes in zone->interface map includes a horrible hack to work around (claimed (by me)) deficiencies in the nftables parser
2025-02-28 00:43:20 +00:00
expect "#READY#"
firewall: use extraText for zone set contents * the lua necessary is quite wordy, but it's less of a hack than post-processing the rules file with pseudo-sed to get rid of `elements = { }` lines * also switch from stop/starting the firewall service to using a signal, so that we don't go briefly offline every time a new interface appears
2025-03-09 20:42:02 +00:00
send "s6-svwait -U /run/service/wan.link.pppoe\n"
expect "#READY#"
set timeout 30
send "nft list set ip table-ip lan || touch /non/existent\n"
check firewall zones in pppoe test
2025-02-25 23:32:05 +00:00
expect {
firewall: use extraText for zone set contents * the lua necessary is quite wordy, but it's less of a hack than post-processing the rules file with pseudo-sed to get rid of `elements = { }` lines * also switch from stop/starting the firewall service to using a signal, so that we don't go briefly offline every time a new interface appears
2025-03-09 20:42:02 +00:00
"lan" { puts "lan found" }
check firewall zones in pppoe test
2025-02-25 23:32:05 +00:00
"{ }" { puts "missing ifname"; exit 1 }
"No such file or directory" { exit 1 }
}
firewall: use extraText for zone set contents * the lua necessary is quite wordy, but it's less of a hack than post-processing the rules file with pseudo-sed to get rid of `elements = { }` lines * also switch from stop/starting the firewall service to using a signal, so that we don't go briefly offline every time a new interface appears
2025-03-09 20:42:02 +00:00
check firewall zones in pppoe test
2025-02-25 23:32:05 +00:00
expect "#READY#"
automated test for pppoe
2022-09-26 09:47:29 +00:00
firewall: use extraText for zone set contents * the lua necessary is quite wordy, but it's less of a hack than post-processing the rules file with pseudo-sed to get rid of `elements = { }` lines * also switch from stop/starting the firewall service to using a signal, so that we don't go briefly offline every time a new interface appears
2025-03-09 20:42:02 +00:00
# if the test fails for no apparent reason, it is quite likely because
# the firewall hasn't had time to reload after the new interface
# appears and you just have to make this sleep longer. Ew, yes
send "sleep 10; nft list set ip table-ip wan || touch /non/existent\n"
check firewall zones in pppoe test
2025-02-25 23:32:05 +00:00
expect {
firewall: use extraText for zone set contents * the lua necessary is quite wordy, but it's less of a hack than post-processing the rules file with pseudo-sed to get rid of `elements = { }` lines * also switch from stop/starting the firewall service to using a signal, so that we don't go briefly offline every time a new interface appears
2025-03-09 20:42:02 +00:00
"ppp0" { puts "ppp0 found " }
check firewall zones in pppoe test
2025-02-25 23:32:05 +00:00
"{ }" { puts "missing ifname"; exit 1 }
"No such file or directory" { exit 1 }
firewall: use extraText for zone set contents * the lua necessary is quite wordy, but it's less of a hack than post-processing the rules file with pseudo-sed to get rid of `elements = { }` lines * also switch from stop/starting the firewall service to using a signal, so that we don't go briefly offline every time a new interface appears
2025-03-09 20:42:02 +00:00
timeout { exit 1 }
check firewall zones in pppoe test
2025-02-25 23:32:05 +00:00
}
expect "#READY#"
firewall: use extraText for zone set contents * the lua necessary is quite wordy, but it's less of a hack than post-processing the rules file with pseudo-sed to get rid of `elements = { }` lines * also switch from stop/starting the firewall service to using a signal, so that we don't go briefly offline every time a new interface appears
2025-03-09 20:42:02 +00:00
automated test for pppoe
2022-09-26 09:47:29 +00:00
exit $EXIT
Copy Permalink