{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":709587207,"defaultBranch":"main","name":"vwifi","ownerLogin":"vax-r","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2023-10-25T01:41:04.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/57989092?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1706777845.0","currentOid":""},"activityList":{"items":[{"before":"952a2e9b53448bd95b3f416e9c7f41c6fb6fbfe8","after":"13841a164f91dbca04dc11ad8900628c95ebba87","ref":"refs/heads/main","pushedAt":"2024-03-13T16:08:18.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Fix typo","shortMessageHtmlLink":"Fix typo"}},{"before":"baf4714217e774e3f9a34902451ca339fd5d3954","after":"952a2e9b53448bd95b3f416e9c7f41c6fb6fbfe8","ref":"refs/heads/main","pushedAt":"2024-03-02T14:59:05.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"CI: Bump action:checkout version","shortMessageHtmlLink":"CI: Bump action:checkout version"}},{"before":"baf4534cc7977ec5e9565bb72e27c2aea84bb003","after":"e386d1075289ed3938d89209a5ec64aab74be788","ref":"refs/heads/Interface_index","pushedAt":"2024-02-01T08:59:50.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Modify indexing for function vwifi_interface_add\n\nSince we implement a counter for wiphy in our project, which is\nvwifi_wiphy_counter. The relationship between virtual interfaces and\nwiphy is always one-to-one, so the indexing for virtual interfaces can\nbe the same as wiphy.\n\nOriginally, the index for virtual interface is passed as a function\nparameters into the function vwifi_interface_add(). Now we modify the\nfunction, instead of using parameters as index for virtual interface,\nwe use the value of vwifi_wiphy_counter to keep a better consistency.","shortMessageHtmlLink":"Modify indexing for function vwifi_interface_add"}},{"before":null,"after":"baf4534cc7977ec5e9565bb72e27c2aea84bb003","ref":"refs/heads/Interface_index","pushedAt":"2024-02-01T08:57:25.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Modify indexing for function vwifi_interface_add\n\nSince we implement a counter for wiphy in our project, which is\nvwifi_wiphy_counter. The relationship between virtual interfaces and\nwiphy is always one-to-one, so the indexing for virtual interfaces can\nbe the same as wiphy.\n\nOriginally, the index for virtual interface is passed as a function\nparameters into the function vwifi_interface_add(). Now we modify the\nfunction, instead of using parameters as index for virtual interface,\nwe use the value of vwifi_wiphy_counter to keep a better consistency.","shortMessageHtmlLink":"Modify indexing for function vwifi_interface_add"}},{"before":"ff5f9e4fe610aea0ea6a668541918def4d9cf022","after":"baf4714217e774e3f9a34902451ca339fd5d3954","ref":"refs/heads/main","pushedAt":"2024-02-01T07:47:52.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Customize naming scheme for wiphy (#57)\n\nThe default phy%d naming for wiphy in linux kernel depends on the value\r\n of a static variable wiphy_counter. Since they never attempts to\r\n decrease the value of wiphy_counter even a wiphy is unregistered or\r\n freed, this behavior ensures the naming and indexing for wiphy will\r\n be absolutely unique.\r\n\r\nHowever, the kernel might have other projects also utilize wiphy\r\nstructure, which will cause some confusion of wiphy's index and naming\r\nwhen using `struct wiphy`. We implement a custom-made name vw_phy%d\r\nfor wiphy in our project, in order to separate the naming and indexing\r\nfor 'struct wiphy'.\r\n\r\nClose #54","shortMessageHtmlLink":"Customize naming scheme for wiphy (<a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2084380085\" data-permission-text=\"Title is private\" data-url=\"https://github.com/sysprog21/vwifi/issues/57\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/sysprog21/vwifi/pull/57/hovercard\" href=\"https://github.com/sysprog21/vwifi/pull/57\">sysprog21#57</a>)"}},{"before":"14d755b1d2b20c77a348bd2f93bcf35fb0a09eb9","after":"53ef19442c7cbf84c7a452205b071d7401b766cf","ref":"refs/heads/Wiphy_naming","pushedAt":"2024-01-30T07:35:34.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Implement customized naming for wiphy\n\nThe default phy%d naming for wiphy in linux kernel depends on the value\n of a static variable wiphy_counter. Since they never attempts to\n decrease the value of wiphy_counter even a wiphy is unregistered or\n freed, this behavior ensures the naming and indexing for wiphy will\n be absolutely unique.\n\nHowever, the kernel might have other projects also utilize wiphy\nstructure, which will cause some confusion of wiphy's index and naming\nwhen using `struct wiphy`. We implement a custom-made name \"vw_phy%d\"\nfor wiphy in our project, in order to seperate the naming and indexing\nfor `struct wiphy` in our project.\n\nAs for the troublesome behavior causing by the never-decreasing index of\nwiphy structure as decribed in #54, we suggest to make some changes when\ndoing manual testing by finding the wiphy index of the interface first,\nand use the index to query the actual wiphy's name for the interface as\ndescribe in the changes of README.md.\n\nClose #54","shortMessageHtmlLink":"Implement customized naming for wiphy"}},{"before":"4c45815f36849d922589a31d4c7b077bd61b764c","after":"14d755b1d2b20c77a348bd2f93bcf35fb0a09eb9","ref":"refs/heads/Wiphy_naming","pushedAt":"2024-01-30T06:39:59.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Implement customized naming for wiphy\n\nThe default phy%d naming for wiphy in linux kernel depends on the value\n of a static variable wiphy_counter. Since they never attempts to\n decrease the value of wiphy_counter even a wiphy is unregistered or\n freed, this behavior ensures the naming and indexing for wiphy will\n be absolutely unique.\n\nHowever, the kernel might have other projects also utilize wiphy\nstructure, which will cause some confusion of wiphy's index and naming\nwhen using `struct wiphy`. We implement a custom-made name \"vw_phy%d\"\nfor wiphy in our project, in order to seperate the naming and indexing\nfor `struct wiphy` in our project.\n\nAs for the troublesome behavior causing by the never-decreasing index of\nwiphy structure as decribed in #54, we suggest to make some changes when\ndoing manual testing by finding the wiphy index of the interface first,\nand use the index to query the actual wiphy's name for the interface as\ndescribe in the changes of README.md.\n\nClose #54","shortMessageHtmlLink":"Implement customized naming for wiphy"}},{"before":"fd771e3899cf603b085af44e6d50101a14444074","after":"4c45815f36849d922589a31d4c7b077bd61b764c","ref":"refs/heads/Wiphy_naming","pushedAt":"2024-01-28T14:48:35.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Implement customized naming for wiphy\n\nThe default phy%d naming for wiphy in linux kernel depends on the value\n of a static variable wiphy_counter. Since they never attempts to\n decrease the value of wiphy_counter even a wiphy is unregistered or\n freed, this behavior ensures the naming and indexing for wiphy will\n be absolutely unique.\n\nHowever, the kernel might have other projects also utilize wiphy\nstructure, which will cause some confusion of wiphy's index and naming\nwhen using `struct wiphy`. We implement a custom-made name \"vw_phy%d\"\nfor wiphy in our project, in order to seperate the naming and indexing\nfor `struct wiphy` in our project.\n\nAs for the troublesome behavior causing by the never-decreasing index of\nwiphy structure as decribed in #54, we suggest to make some changes when\ndoing manual testing by finding the wiphy index of the interface first,\nand use the index to query the actual wiphy's name for the interface as\ndescribe in the changes of README.md.\n\nClose #54","shortMessageHtmlLink":"Implement customized naming for wiphy"}},{"before":"f5230a9de5d71e5e941b01f2b4bc220cf9f17981","after":"fd771e3899cf603b085af44e6d50101a14444074","ref":"refs/heads/Wiphy_naming","pushedAt":"2024-01-28T14:43:04.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Implement customized naming for wiphy\n\nThe default phy%d naming for wiphy in linux kernel depends on the value\n of a static variable wiphy_counter. Since they never attempts to\n decrease the value of wiphy_counter even a wiphy is unregistered or\n freed, this behavior ensures the naming and indexing for wiphy will\n be absolutely unique.\n\nHowever, the kernel might have other projects also utilize wiphy\nstructure, which will cause some confusion of wiphy's index and naming\nwhen using `struct wiphy`. We implement a custom-made name \"vw_phy%d\"\nfor wiphy in our project, in order to seperate the naming and indexing\nfor `struct wiphy` in our project.\n\nAs for the troublesome behavior causing by the never-decreasing index of\nwiphy structure as decribed in #54, we suggest to make some changes when\ndoing manual testing by finding the wiphy index of the interface first,\nand use the index to query the actual wiphy's name for the interface as\ndescribe in the changes of README.md.\n\nClose #54","shortMessageHtmlLink":"Implement customized naming for wiphy"}},{"before":"b23aa06315b92522145519cb9f0523597fd3b8d0","after":"f5230a9de5d71e5e941b01f2b4bc220cf9f17981","ref":"refs/heads/Wiphy_naming","pushedAt":"2024-01-16T16:21:07.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Implement customized naming for wiphy\n\nThe default phy%d naming for wiphy in linux kernel depends on the value\n of a static variable wiphy_counter. Since they never attempts to\n decrease the value of wiphy_counter even a wiphy is unregistered or\n freed, the value of wiphy_counter will continue to increase and cause\n troublesome bevior mentioned in #54.\n\nWe implement a customized naming for wiphy in vwifi, using\n `vwifi_wiphy_counter` to keep track of the number of wiphy in vwifi.\nWith `vwifi_wiphy_counter` acting in concert with our customized naming\n, the name of wiphy in vwifi will be in the form of \"vwifi_phy%d\".\n\nWe'll submit a patch to linux kernel community to fix the problem of\nthe never-decreasing variable `wiphy_counter`. We may change back to\n use the default phy%d naming if the patch can be accepted.\n\nClose #54","shortMessageHtmlLink":"Implement customized naming for wiphy"}},{"before":null,"after":"b23aa06315b92522145519cb9f0523597fd3b8d0","ref":"refs/heads/Wiphy_naming","pushedAt":"2024-01-16T16:16:57.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Implement customized naming for wiphy\n\nThe default phy%d naming for wiphy in linux kernel depends on the value\n of a static variable wiphy_counter. Since they never attempts to\n decrease the value of wiphy_counter even a wiphy is unregistered or\n freed, the value of wiphy_counter will continue to increase and cause\n troublesome bevior mentioned in #54.\n\nWe implement a customized naming for wiphy in vwifi, using\n `vwifi_wiphy_counter` to keep track of the number of wiphy in vwifi.\nWith `vwifi_wiphy_counter` acting in concert with our customized naming\n, the name of wiphy in vwifi will be in the form of \"vwifi_phy%d\".","shortMessageHtmlLink":"Implement customized naming for wiphy"}},{"before":"f1f4b656e26ecfc44c26bcdf2f26c53e70cd92ed","after":"ff5f9e4fe610aea0ea6a668541918def4d9cf022","ref":"refs/heads/main","pushedAt":"2024-01-15T05:31:28.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Merge pull request #56 from vax-r/Enforce_Naming\n\nEnforce consistent naming scheme","shortMessageHtmlLink":"Merge pull request <a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2073499308\" data-permission-text=\"Title is private\" data-url=\"https://github.com/sysprog21/vwifi/issues/56\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/sysprog21/vwifi/pull/56/hovercard\" href=\"https://github.com/sysprog21/vwifi/pull/56\">sysprog21#56</a> from vax-r/Enforce_Naming"}},{"before":"88936a6524cdba93e5dd37e0a2d140caf1fb1f65","after":"21a60d00367af0b8129d7efcbd2dbe399d046068","ref":"refs/heads/Enforce_Naming","pushedAt":"2024-01-10T09:09:45.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Enforce consistent naming scheme\n\nChanges are made to the prefix of functions, variables and related\n symbols from \"owl\" to \"vwifi\", just like the name of this project.\nAt the same time, the prefix of the name for virtual interfaces are\nchanged, too. Virtual interfaces used \"owl\" as the prefix of their\nname but now they use \"vw\" for the prefix of their name.\nFor example \"owl0\" are changed to \"vw0\".\n\nClose #52","shortMessageHtmlLink":"Enforce consistent naming scheme"}},{"before":"0fe0b069b37cbe1c0a4ec1b84fdeb73228d4edfb","after":"88936a6524cdba93e5dd37e0a2d140caf1fb1f65","ref":"refs/heads/Enforce_Naming","pushedAt":"2024-01-10T07:55:52.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Enforce vwifi consistent naming\n\nChanges are made to the prefix of functions, variables and related\n symbols from \"owl\" to \"vwifi\", just like the name of this project.\nAt the same time, the prefix of the name for virtual interfaces are\nchanged, too. Virtual interfaces used \"owl\" as the prefix of their\nname but now they use \"vw\" for the prefix of their name.\nFor example \"owl0\" are changed to \"vw0\".\n\nClose #52","shortMessageHtmlLink":"Enforce vwifi consistent naming"}},{"before":null,"after":"0fe0b069b37cbe1c0a4ec1b84fdeb73228d4edfb","ref":"refs/heads/Enforce_Naming","pushedAt":"2024-01-10T03:03:26.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Enforce vwifi consistent naming\n\nChange prefix of functions, variables and related symbols from 'owl'\n to 'vwifi', and change prefix of interface name from 'owl' to 'vw'.\n\nClose #52","shortMessageHtmlLink":"Enforce vwifi consistent naming"}},{"before":"7814d59e38cc4839c167a179742342ab4ef030bf","after":"f1f4b656e26ecfc44c26bcdf2f26c53e70cd92ed","ref":"refs/heads/main","pushedAt":"2024-01-04T05:50:59.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Fix typo (#55)","shortMessageHtmlLink":"Fix typo (<a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2065047594\" data-permission-text=\"Title is private\" data-url=\"https://github.com/sysprog21/vwifi/issues/55\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/sysprog21/vwifi/pull/55/hovercard\" href=\"https://github.com/sysprog21/vwifi/pull/55\">sysprog21#55</a>)"}},{"before":"067ad32dd6d3077e6e7e4709822b97411dc373ab","after":"d9083f7ff85b620246c5e493804b40a8e5b8c0c5","ref":"refs/heads/Fix_typo","pushedAt":"2024-01-04T05:47:27.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Fix typos in verify.sh\n\nCorrect 'sucess' to 'success' in verify.sh.","shortMessageHtmlLink":"Fix typos in verify.sh"}},{"before":null,"after":"067ad32dd6d3077e6e7e4709822b97411dc373ab","ref":"refs/heads/Fix_typo","pushedAt":"2024-01-04T05:43:52.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Fix typos in verify.sh\n\nCorrect 'sucess' to 'success' in verify.sh.","shortMessageHtmlLink":"Fix typos in verify.sh"}},{"before":"20d4a42ff659aa93701cf88a518b3847f508ab89","after":"7814d59e38cc4839c167a179742342ab4ef030bf","ref":"refs/heads/main","pushedAt":"2023-12-27T12:20:15.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Introduce a userspace tool (#53)\n\nThis commit introduces a userspace tool, vwifi-tool, which can\r\ndisplay the status of the driver and allows users to specify a\r\nblocklist.\r\n\r\nThis tool will show the status of the vwifi driver by reading\r\nfrom /sys/module/vwifi/initstate. Users can only set a blocklist\r\nfor the vwifi driver when it is loaded.\r\n\r\nUsers can run vwifi-tool with command-line options, parsed by\r\ngetopt(), to set or unset a user-specific blocklist pair. The\r\nblocklist will be copied and sent to the vwifi driver via a\r\nnetlink socket.\r\n\r\nClose #48","shortMessageHtmlLink":"Introduce a userspace tool (<a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2032831630\" data-permission-text=\"Title is private\" data-url=\"https://github.com/sysprog21/vwifi/issues/53\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/sysprog21/vwifi/pull/53/hovercard\" href=\"https://github.com/sysprog21/vwifi/pull/53\">sysprog21#53</a>)"}},{"before":"c7fc45b91c5eee864e8d4c83c515070528bf4524","after":"54b19ec64cc06997fb50f2c0320a852738f3935f","ref":"refs/heads/Blacklist_feature","pushedAt":"2023-12-27T12:02:18.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Implement userspace tool : vwifi-tool\n\nAn userspace tool vwifi-tool which can display the status of driver\n and allow users to specify blocklist.\n\nAccording to #48, we want a tool which can configure user-specific\nblocklist to filter unwanted packets from certain interfaces.\n\nThis tool will show the status of vwifi driver by reading from\n`/sys/module/vwifi/initstate`, users can only set blocklist for vwifi\ndriver when it's loaded.\n\nUsers can use vwifi-tool with command line options which is enabled by\n `getopt()` to set or unset user-specific blocklist pair. The blocklist\n will be coppied and sent to the vwifi driver via netlink socket.\n\nResolves: #48","shortMessageHtmlLink":"Implement userspace tool : vwifi-tool"}},{"before":"1829eded1f4a951c6740cdcd5ee03bdf3b535817","after":"c7fc45b91c5eee864e8d4c83c515070528bf4524","ref":"refs/heads/Blacklist_feature","pushedAt":"2023-12-27T05:09:26.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Implement userspace tool : vwifi-tool\n\nIn order to filter unwanted network packets, we implement an userspace tool called vwifi-tool which can display the\nstauts of driver and allow users to specify or unset their own blocklist.\n\nResolves: #48","shortMessageHtmlLink":"Implement userspace tool : vwifi-tool"}},{"before":"4e3948f99d181b66cbf523045f7a03ed90eefed1","after":"1829eded1f4a951c6740cdcd5ee03bdf3b535817","ref":"refs/heads/Blacklist_feature","pushedAt":"2023-12-27T01:25:14.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Implementation of vwifi-tool\n\nImplement a userspace tool called vwifi-tool to provide more flexibility\nand customization for users.\nCurrently supporting features:\n* Display the status of vwifi driver\n* Configure user-specific blocklist\n\nWe let vwifi-tool check on vwifi driver's status before user can specify\nany action on it by reading from `/sys/module/vwifi/initstate` to get\nthe status of vwifi driver status.\n\nSupport user-specific blocklist in vwifi kernel module, used as interfaces pair such\nas \"owl2 blocks owl1\", allow maximum blocklist size to be 1024 bytes\nnow and maintained as global content within struct owl_content.\nWhen we detect the packet's source interface and destination interface\nis in the blocklist, we discard the packet.\n\nUsers can use vwifi-tool with command line options to specify their own blocklist pair, then vwifi-tool will copy their destination and source interfaces pair into a message buffer, and use netlink socket to communicate with kernel to allow the ability to dynamically alter the blocklist maintaining in vwifi kernel module.\n\nAccording to #48, we implement a tool `vwifi-tool` to set blocklist in order to filter packet which is\nunwanted and discard it when AP is forwarding the package also it can\ndisplay the status of vwifi driver. So far the discarded package are simply being ignored by the program, we may need\nfuture improvement to delete them thoroughly.\n\nResolves: #48","shortMessageHtmlLink":"Implementation of vwifi-tool"}},{"before":"295fb4b068c3dfa403b56d0d5c4457d85498bea4","after":"4e3948f99d181b66cbf523045f7a03ed90eefed1","ref":"refs/heads/Blacklist_feature","pushedAt":"2023-12-26T04:28:16.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Support blocklist in vwifi\n\nUse vwifi-tool to display the status of vwifi and provide ability to use blocklist to block packets from specified\ninterface.\n\nSupport blocklist in vwifi kernel module, used as interfaces pair such\nas \"owl2 blocks owl1\", allow maximum blocklist size to be 1024 bytes\nnow and maintained as global content within struct owl_content.\nWhen we detect the packet's source interface and destination interface\nis in the blocklist, we discard the packet.\n\nUsing userspace program with netlink to communicate with kernel and allow the ability to dynamically alter the blocklist maintaining\nin vwifi kernel module.\n\nAccording to #48, we set blocklist in order to filter packet which is\nunwanted and discard it when AP is forwarding the package. So far the\ndiscarded package are simply being ignored by the program, we may need\nfuture improvement to delete them thoroughly.\n\nResolves: #48","shortMessageHtmlLink":"Support blocklist in vwifi"}},{"before":"f84e0405ad333db06e6470bee21dde181f9426b4","after":"295fb4b068c3dfa403b56d0d5c4457d85498bea4","ref":"refs/heads/Blacklist_feature","pushedAt":"2023-12-26T04:15:16.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Support blocklist in vwifi\n\nUse vwifi-tool to display the status of vwifi and provide ability to use blocklist to block packets from specified\ninterface.\n\nSupport blocklist in vwifi kernel module, used as interfaces pair such\nas \"owl2 blocks owl1\", allow maximum blocklist size to be 1024 bytes\nnow and maintained as global content within struct owl_content.\nWhen we detect the packet's source interface and destination interface\nis in the blocklist, we discard the packet.\n\nUsing userspace program with netlink to communicate with kernel and allow the ability to dynamically alter the blocklist maintaining\nin vwifi kernel module.\n\nAccording to #48, we set blocklist in order to filter packet which is\nunwanted and discard it when AP is forwarding the package. So far the\ndiscarded package are simply being ignored by the program, we may need\nfuture improvement to delete them thoroughly.\n\nResolves: #48","shortMessageHtmlLink":"Support blocklist in vwifi"}},{"before":"b32140f984a0a7ab618a05c59ac87357b7e33169","after":"f84e0405ad333db06e6470bee21dde181f9426b4","ref":"refs/heads/Blacklist_feature","pushedAt":"2023-12-25T16:00:33.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Support blocklist in vwifi\n\nUse vwifi-tool to display the status of vwifi and provide ability to use blocklist to block packets from specified\ninterface.\n\nSupport blocklist in vwifi kernel module, used as interfaces pair such\nas \"owl2 blocks owl1\", allow maximum blocklist size to be 1024 bytes\nnow and maintained as global content within struct owl_content.\nWhen we detect the packet's source interface and destination interface\nis in the blocklist, we discard the packet.\n\nUsing userspace program with netlink to communicate with kernel and allow the ability to dynamically alter the blocklist maintaining\nin vwifi kernel module.\n\nAccording to #48, we set blocklist in order to filter packet which is\nunwanted and discard it when AP is forwarding the package. So far the\ndiscarded package are simply being ignored by the program, we may need\nfuture improvement to delete them thoroughly.\n\nResolves: #48","shortMessageHtmlLink":"Support blocklist in vwifi"}},{"before":"caa4e881f33a6dc94612dcc4f4e7c3e0a2fd8f23","after":"b32140f984a0a7ab618a05c59ac87357b7e33169","ref":"refs/heads/Blacklist_feature","pushedAt":"2023-12-23T08:19:57.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Support blocklist in vwifi\n\nUse vwifi-tool to display the status of vwifi and provide ability to use blocklist to block packets from specified\ninterface.\n\nSupport blocklist in vwifi kernel module, used as interfaces pair such\nas \"owl2 blocks owl1\", allow maximum blocklist size to be 1024 bytes\nnow and maintained as global content within struct owl_content.\nWhen we detect the packet's source interface and destination interface\nis in the blocklist, we discard the packet.\n\nUsing userspace program with netlink to communicate with kernel and allow the ability to dynamically alter the blocklist maintaining\nin vwifi kernel module.\n\nAccording to #48, we set blocklist in order to filter packet which is\nunwanted and discard it when AP is forwarding the package. So far the\ndiscarded package are simply being ignored by the program, we may need\nfuture improvement to delete them thoroughly.\n\nResolves: #48","shortMessageHtmlLink":"Support blocklist in vwifi"}},{"before":"d061a60cf3be7f54f88b64b036f560fb995d5999","after":"caa4e881f33a6dc94612dcc4f4e7c3e0a2fd8f23","ref":"refs/heads/Blacklist_feature","pushedAt":"2023-12-20T01:18:49.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Support blocklist in vwifi\n\nEnable ability to use blocklist to block packets from specified\ninterface.\n\nSupport blocklist in vwifi kernel module, used as interfaces pair such\nas \"owl2 blocks owl1\", allow maximum blocklist size to be 1024 bytes\nnow and maintained as global content within struct owl_content.\nWhen we detect the packet's source interface and destination interface\nis in the blocklist, we discard the packet.\n\nUsing userspace program with netlink to communicate with kernel and allow the ability to dynamically alter the blocklist maintaining\nin vwifi kernel module.\n\nAccording to #48, we set blocklist in order to filter packet which is\nunwanted and discard it when AP is forwarding the package. So far the\ndiscarded package are simply being ignored by the program, we may need\nfuture improvement to delete them thoroughly.\n\nResolves: #48","shortMessageHtmlLink":"Support blocklist in vwifi"}},{"before":"adc6373d81f83e98a1069c36d4d9b185752f710b","after":"d061a60cf3be7f54f88b64b036f560fb995d5999","ref":"refs/heads/Blacklist_feature","pushedAt":"2023-12-20T01:14:42.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Support blocklist in vwifi\n\nEnable ability to use blocklist to block packets from specified\ninterface.\n\nSupport blocklist in vwifi kernel module, used as interfaces pair such\nas \"owl2 blocks owl1\", allow maximum blocklist size to be 1024 bytes\nnow and maintained as global content within struct owl_content.\nWhen we detect the packet's source interface and destination interface\nis in the blocklist, we discard the packet.\n\nUsing userspace program with netlink to communicate with kernel and allow the ability to dynamically alter the blocklist maintaining\nin vwifi kernel module.\n\nAccording to #48, we set blocklist in order to filter packet which is\nunwanted and discard it when AP is forwarding the package. So far the\ndiscarded package are simply being ignored by the program, we may need\nfuture improvement to delete them thoroughly.\n\nResolves: #48","shortMessageHtmlLink":"Support blocklist in vwifi"}},{"before":"2842a474efc1c3757ed0d3dd68800ec0932914ef","after":"adc6373d81f83e98a1069c36d4d9b185752f710b","ref":"refs/heads/Blacklist_feature","pushedAt":"2023-12-19T08:19:21.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Support blocklist in vwifi\n\nEnable ability to use blocklist to block packets from specified\ninterface.\n\nSupport blocklist in vwifi kernel module, used as interfaces pair such\nas \"owl2 blocks owl1\", allow maximum blocklist size to be 1024 bytes\nnow and maintained as global content within struct owl_content.\nWhen we detect the packet's source interface and destination interface\nis in the blocklist, we discard the packet.\n\nUsing userspace program with netlink to communicate with kernel and allow the ability to dynamically alter the blocklist maintaining\nin vwifi kernel module.\n\nAccording to #48, we set blocklist in order to filter packet which is\nunwanted and discard it when AP is forwarding the package. So far the\ndiscarded package are simply being ignored by the program, we may need\nfuture improvement to delete them thoroughly.\n\nResolves: #48","shortMessageHtmlLink":"Support blocklist in vwifi"}},{"before":"a55f88c17d2cf1c49ae48a35a3e3360f3cae097f","after":"2842a474efc1c3757ed0d3dd68800ec0932914ef","ref":"refs/heads/Blacklist_feature","pushedAt":"2023-12-19T08:11:56.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vax-r","name":"I-Hsin Cheng","path":"/vax-r","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57989092?s=80&v=4"},"commit":{"message":"Support blocklist in vwifi\n\nEnable ability to use blocklist to block packets from specified\ninterface.\n\nSupport blocklist in vwifi kernel module, used as interfaces pair such\nas \"owl2 blocks owl1\", allow maximum blocklist size to be 1024 bytes\nnow and maintained as global content within struct owl_content.\nWhen we detect the packet's source interface and destination interface\nis in the blocklist, we discard the packet.\n\nUsing userspace program with netlink to communicate with kernel and allow the ability to dynamically alter the blocklist maintaining\nin vwifi kernel module.\n\nAccording to #48, we set blocklist in order to filter packet which is\nunwanted and discard it when AP is forwarding the package. So far the\ndiscarded package are simply being ignored by the program, we may need\nfuture improvement to delete them thoroughly.\n\nResolves: #48","shortMessageHtmlLink":"Support blocklist in vwifi"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"startCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wMy0xM1QxNjowODoxOC4wMDAwMDBazwAAAAQUr7JY","endCursor":"Y3Vyc29yOnYyOpK7MjAyMy0xMi0xOVQwODoxMTo1Ni4wMDAwMDBazwAAAAPNlI8L"}},"title":"Activity · vax-r/vwifi"}