MétaCan
Menu
Back to cohort
Record W2157381862 · doi:10.1109/ccece.2011.6030538

Design a hardware network firewall on FPGA

2011· article· en· W2157381862 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicNetwork Packet Processing and Optimization
Canadian institutionsUniversity of Saskatchewan
Fundersnot available
KeywordsFirewall (physics)Computer scienceHeaderApplication firewallField-programmable gate arrayInternet securityComputer networkNetwork packetNetwork securityStateful firewallEmbedded systemNetwork processorDMZContext-based access controlComputer hardwareOperating systemComputer securityInformation securitySecurity service

Abstract

fetched live from OpenAlex

Catastrophe events can happen when a computer or a computer network is exposed to the Internet without any security protection. The security issues can be mitigated by setting up a firewall between the inside network and the outside world. This paper describes a design of a highly customizable hardware packet filtering firewall to be embedded on a network gateway. A packet filtering firewall controls the header field in each network data packet based on its configuration and permits or denies the data passing through the network. An Altera FPGA platform is used for implementing and evaluating the hardware network firewall. The hardware design provides much faster speed compared to traditional software applications.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.826
Threshold uncertainty score0.319

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.057
GPT teacher head0.226
Teacher spread0.168 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it