#netgraph — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #netgraph, aggregated by home.social.
-
Just updated my Netgraph VIewer for safer use. Make sure to bypass doas password in doas.conf. Now, normal users can run these scripts without root directly
Codeberg: https://codeberg.org/maulanahirzan/Netgraph-Viewer
Brew BSDCafe: https://brew.bsd.cafe/maulanahirzan/Netgraph-Viewer!!! Run these script with extra precaution. I am not responsible for any broken system or data lost. You have been warned !!!
-
Just updated my Netgraph VIewer for safer use. Make sure to bypass doas password in doas.conf. Now, normal users can run these scripts without root directly
Codeberg: https://codeberg.org/maulanahirzan/Netgraph-Viewer
Brew BSDCafe: https://brew.bsd.cafe/maulanahirzan/Netgraph-Viewer!!! Run these script with extra precaution. I am not responsible for any broken system or data lost. You have been warned !!!
-
Just updated my Netgraph VIewer for safer use. Make sure to bypass doas password in doas.conf. Now, normal users can run these scripts without root directly
Codeberg: https://codeberg.org/maulanahirzan/Netgraph-Viewer
Brew BSDCafe: https://brew.bsd.cafe/maulanahirzan/Netgraph-Viewer!!! Run these script with extra precaution. I am not responsible for any broken system or data lost. You have been warned !!!
-
Just updated my Netgraph VIewer for safer use. Make sure to bypass doas password in doas.conf. Now, normal users can run these scripts without root directly
Codeberg: https://codeberg.org/maulanahirzan/Netgraph-Viewer
Brew BSDCafe: https://brew.bsd.cafe/maulanahirzan/Netgraph-Viewer!!! Run these script with extra precaution. I am not responsible for any broken system or data lost. You have been warned !!!
-
Just updated my Netgraph VIewer for safer use. Make sure to bypass doas password in doas.conf. Now, normal users can run these scripts without root directly
Codeberg: https://codeberg.org/maulanahirzan/Netgraph-Viewer
Brew BSDCafe: https://brew.bsd.cafe/maulanahirzan/Netgraph-Viewer!!! Run these script with extra precaution. I am not responsible for any broken system or data lost. You have been warned !!!
-
I wrote shell and python scripts as a wrapper for ngctl dot (netgraph Graphviz export) and dot (Graphviz dot to png). Available through my repository :
a. Coideberg: https://codeberg.org/maulanahirzan/Netgraph-Viewer
b. Brew : https://brew.bsd.cafe/maulanahirzan/Netgraph-ViewerThese scripts requires root to run so: choose sh version for less external dependencies (more secure), or python version bundled with tkinter image viewer.
!!! Run these script with extra precaution. I am not responsible for any broken system or data lost. You have been warned !!!
-
I wrote shell and python scripts as a wrapper for ngctl dot (netgraph Graphviz export) and dot (Graphviz dot to png). Available through my repository :
a. Coideberg: https://codeberg.org/maulanahirzan/Netgraph-Viewer
b. Brew : https://brew.bsd.cafe/maulanahirzan/Netgraph-ViewerThese scripts requires root to run so: choose sh version for less external dependencies (more secure), or python version bundled with tkinter image viewer.
!!! Run these script with extra precaution. I am not responsible for any broken system or data lost. You have been warned !!!
-
I wrote shell and python scripts as a wrapper for ngctl dot (netgraph Graphviz export) and dot (Graphviz dot to png). Available through my repository :
a. Coideberg: https://codeberg.org/maulanahirzan/Netgraph-Viewer
b. Brew : https://brew.bsd.cafe/maulanahirzan/Netgraph-ViewerThese scripts requires root to run so: choose sh version for less external dependencies (more secure), or python version bundled with tkinter image viewer.
!!! Run these script with extra precaution. I am not responsible for any broken system or data lost. You have been warned !!!
-
I wrote shell and python scripts as a wrapper for ngctl dot (netgraph Graphviz export) and dot (Graphviz dot to png). Available through my repository :
a. Coideberg: https://codeberg.org/maulanahirzan/Netgraph-Viewer
b. Brew : https://brew.bsd.cafe/maulanahirzan/Netgraph-ViewerThese scripts requires root to run so: choose sh version for less external dependencies (more secure), or python version bundled with tkinter image viewer.
!!! Run these script with extra precaution. I am not responsible for any broken system or data lost. You have been warned !!!
-
I wrote shell and python scripts as a wrapper for ngctl dot (netgraph Graphviz export) and dot (Graphviz dot to png). Available through my repository :
a. Coideberg: https://codeberg.org/maulanahirzan/Netgraph-Viewer
b. Brew : https://brew.bsd.cafe/maulanahirzan/Netgraph-ViewerThese scripts requires root to run so: choose sh version for less external dependencies (more secure), or python version bundled with tkinter image viewer.
!!! Run these script with extra precaution. I am not responsible for any broken system or data lost. You have been warned !!!
-
I need help troubleshooting my network simulation. This simulation simulates simple network with a router and a client (both are jails). The router provides internet to client 1 through netgraph.
Setup:
1. Host-Router (Epair)
2. Router-Bridge-Client1 (NetGraph)What are working:
1. Router can ping 1.1.1.1 (Internet Access)
2. Router can ping host gateway (192.168.200.1)
3. Router can ping client 1 (192.168.150.10)
4. Client 1 can ping the router (192.168.150.1)What are not working:
1. Client 1 cannot ping 192.168.200.1
2. Client 1 cannot ping 1.1.1.1What I have done:
1. Enabled gateway_enable in rc.conf
2. Configured all forwarding in sysctl
3. Create default route to 192.168.200.1 -
I need help troubleshooting my network simulation. This simulation simulates simple network with a router and a client (both are jails). The router provides internet to client 1 through netgraph.
Setup:
1. Host-Router (Epair)
2. Router-Bridge-Client1 (NetGraph)What are working:
1. Router can ping 1.1.1.1 (Internet Access)
2. Router can ping host gateway (192.168.200.1)
3. Router can ping client 1 (192.168.150.10)
4. Client 1 can ping the router (192.168.150.1)What are not working:
1. Client 1 cannot ping 192.168.200.1
2. Client 1 cannot ping 1.1.1.1What I have done:
1. Enabled gateway_enable in rc.conf
2. Configured all forwarding in sysctl
3. Create default route to 192.168.200.1 -
I need help troubleshooting my network simulation. This simulation simulates simple network with a router and a client (both are jails). The router provides internet to client 1 through netgraph.
Setup:
1. Host-Router (Epair)
2. Router-Bridge-Client1 (NetGraph)What are working:
1. Router can ping 1.1.1.1 (Internet Access)
2. Router can ping host gateway (192.168.200.1)
3. Router can ping client 1 (192.168.150.10)
4. Client 1 can ping the router (192.168.150.1)What are not working:
1. Client 1 cannot ping 192.168.200.1
2. Client 1 cannot ping 1.1.1.1What I have done:
1. Enabled gateway_enable in rc.conf
2. Configured all forwarding in sysctl
3. Create default route to 192.168.200.1 -
I need help troubleshooting my network simulation. This simulation simulates simple network with a router and a client (both are jails). The router provides internet to client 1 through netgraph.
Setup:
1. Host-Router (Epair)
2. Router-Bridge-Client1 (NetGraph)What were working:
1. Router can ping 1.1.1.1 (Internet Access)
2. Router can ping host gateway (192.168.200.1)
3. Router can ping client 1 (192.168.150.10)
4. Client 1 can ping the router (192.168.150.1)What were not working:
1. Client 1 cannot ping 192.168.200.1
2. Client 1 cannot ping 1.1.1.1What I have done:
1. Enabled gateway_enable in rc.conf
2. Configured all forwarding in sysctl
3. Create default route to 192.168.200.1 -
I need help troubleshooting my network simulation. This simulation simulates simple network with a router and a client (both are jails). The router provides internet to client 1 through netgraph.
Setup:
1. Host-Router (Epair)
2. Router-Bridge-Client1 (NetGraph)What were working:
1. Router can ping 1.1.1.1 (Internet Access)
2. Router can ping host gateway (192.168.200.1)
3. Router can ping client 1 (192.168.150.10)
4. Client 1 can ping the router (192.168.150.1)What were not working:
1. Client 1 cannot ping 192.168.200.1
2. Client 1 cannot ping 1.1.1.1What I have done:
1. Enabled gateway_enable in rc.conf
2. Configured all forwarding in sysctl
3. Create default route to 192.168.200.1 -
This screenshot is a proscrationation project with Netgraph: a small script that exports Netgraph's dot file and converts it to an image. I can preview my current Netgraph progress using an image viewer (with a live update like Risretto) every 5 seconds.
-
This screenshot is a proscrationation project with Netgraph: a small script that exports Netgraph's dot file and converts it to an image. I can preview my current Netgraph progress using an image viewer (with a live update like Risretto) every 5 seconds.
-
This screenshot is a proscrationation project with Netgraph: a small script that exports Netgraph's dot file and converts it to an image. I can preview my current Netgraph progress using an image viewer (with a live update like Risretto) every 5 seconds.
-
Productive procrastination with Netgraph. I have successfully deployed a simple peer-to-peer connection with traffic mirroring capability that is suitable for Wireshark sniffing. What makes Netgraph great is that no additional software is required at all. I will note these personal discoveries into my notes (and eventually, turn it into an ebook?)
-
Productive procrastination with Netgraph. I have successfully deployed a simple peer-to-peer connection with traffic mirroring capability that is suitable for Wireshark sniffing. What makes Netgraph great is that no additional software is required at all. I will note these personal discoveries into my notes (and eventually, turn it into an ebook?)
-
Productive procrastination with Netgraph. I have successfully deployed a simple peer-to-peer connection with traffic mirroring capability that is suitable for Wireshark sniffing. What makes Netgraph great is that no additional software is required at all. I will note these personal discoveries into my notes (and eventually, turn it into an ebook?)
-
Productive procrastination with Netgraph. I have successfully deployed a simple peer-to-peer connection with traffic mirroring capability that is suitable for Wireshark sniffing. What makes Netgraph great is that no additional software is required at all. I will note these personal discoveries into my notes (and eventually, turn it into an ebook?)
-
Productive procrastination with Netgraph. I have successfully deployed a simple peer-to-peer connection with traffic mirroring capability that is suitable for Wireshark sniffing. What makes Netgraph great is that no additional software is required at all. I will note these personal discoveries into my notes (and eventually, turn it into an ebook?)
-
Studying in the morning is the best way to learn. I have successfully deployed Client1-Router-Client2 with netgraph and vnet. Screenshot 1 is the deployment result, and Screenshot 2 dot image produced by netgraph with some editing (my first time hacking Graphviz dot file, and so confusing. But actually quite simple).
My last objectives are to route the traffic between client 1 and client 2, and automate the netgraph process
-
Studying in the morning is the best way to learn. I have successfully deployed Client1-Router-Client2 with netgraph and vnet. Screenshot 1 is the deployment result, and Screenshot 2 dot image produced by netgraph with some editing (my first time hacking Graphviz dot file, and so confusing. But actually quite simple).
My last objectives are to route the traffic between client 1 and client 2, and automate the netgraph process
-
Studying in the morning is the best way to learn. I have successfully deployed Client1-Router-Client2 with netgraph and vnet. Screenshot 1 is the deployment result, and Screenshot 2 dot image produced by netgraph with some editing (my first time hacking Graphviz dot file, and so confusing. But actually quite simple).
My last objectives are to route the traffic between client 1 and client 2, and automate the netgraph process
-
Studying at the morning is the best way to learn. I have successfully deployed Client1-Router-Client2 with netgraph and vnet. Screenshot 1 is the deployment result, and Screenshot 2 dot image produced by netgraph with some editing (my first time hacking Graphviz dot file, and so confusing. But actually quite simple).
My last objectives are to route the traffic between client 1 and client 2, and automate the netgraph process
-
Studying at the morning is the best way to learn. I have successfully deployed Client1-Router-Client2 with netgraph and vnet. Screenshot 1 is the deployment result, and Screenshot 2 dot image produced by netgraph with some editing (my first time hacking Graphviz dot file, and so confusing. But actually quite simple).
My last objectives are to route the traffic between client 1 and client 2, and automate the netgraph process
-
The recording of the July 11th, 2024 #bhyve Production User Call is up:
We discussed the newly-posted @EuroBSDCon schedule, the weekly #FreeBSD snapshots that might include 9pfs improvements, changes to the FreeBSD release schedule, the urgent need for live migration on FreeBSD, the #TrueNAS 13.3 VNC issue and its causes, WebVNC/NoVNC in general, the #Netgraph "retry" issue, bhyve "quiz" user process functionality, and more!
"Don't forget to slam those Like and Subscribe buttons."
-
The recording of the July 11th, 2024 #bhyve Production User Call is up:
We discussed the newly-posted @EuroBSDCon schedule, the weekly #FreeBSD snapshots that might include 9pfs improvements, changes to the FreeBSD release schedule, the urgent need for live migration on FreeBSD, the #TrueNAS 13.3 VNC issue and its causes, WebVNC/NoVNC in general, the #Netgraph "retry" issue, bhyve "quiz" user process functionality, and more!
"Don't forget to slam those Like and Subscribe buttons."
-
The recording of the July 11th, 2024 #bhyve Production User Call is up:
We discussed the newly-posted @EuroBSDCon schedule, the weekly #FreeBSD snapshots that might include 9pfs improvements, changes to the FreeBSD release schedule, the urgent need for live migration on FreeBSD, the #TrueNAS 13.3 VNC issue and its causes, WebVNC/NoVNC in general, the #Netgraph "retry" issue, bhyve "quiz" user process functionality, and more!
"Don't forget to slam those Like and Subscribe buttons."
-
The recording of the July 11th, 2024 #bhyve Production User Call is up:
We discussed the newly-posted @EuroBSDCon schedule, the weekly #FreeBSD snapshots that might include 9pfs improvements, changes to the FreeBSD release schedule, the urgent need for live migration on FreeBSD, the #TrueNAS 13.3 VNC issue and its causes, WebVNC/NoVNC in general, the #Netgraph "retry" issue, bhyve "quiz" user process functionality, and more!
"Don't forget to slam those Like and Subscribe buttons."
-
The recording of the July 11th, 2024 #bhyve Production User Call is up:
We discussed the newly-posted @EuroBSDCon schedule, the weekly #FreeBSD snapshots that might include 9pfs improvements, changes to the FreeBSD release schedule, the urgent need for live migration on FreeBSD, the #TrueNAS 13.3 VNC issue and its causes, WebVNC/NoVNC in general, the #Netgraph "retry" issue, bhyve "quiz" user process functionality, and more!
"Don't forget to slam those Like and Subscribe buttons."
-
The July 9th, 2024 Jail/Zones Production User Call is up:
We got an update from DCH about his jail-based CI system, discussed Jan's proposal to port #OpenBSD's sendsyslog(2) and syslog_r(3) to #FreeBSD for finer-grained logging, revisited Antranig's #Netgraph "retry" issue, and more!
"Don't forget to slam those Like and Subscribe buttons."
-
The July 9th, 2024 Jail/Zones Production User Call is up:
We got an update from DCH about his jail-based CI system, discussed Jan's proposal to port #OpenBSD's sendsyslog(2) and syslog_r(3) to #FreeBSD for finer-grained logging, revisited Antranig's #Netgraph "retry" issue, and more!
"Don't forget to slam those Like and Subscribe buttons."
-
The July 9th, 2024 Jail/Zones Production User Call is up:
We got an update from DCH about his jail-based CI system, discussed Jan's proposal to port #OpenBSD's sendsyslog(2) and syslog_r(3) to #FreeBSD for finer-grained logging, revisited Antranig's #Netgraph "retry" issue, and more!
"Don't forget to slam those Like and Subscribe buttons."
-
The July 9th, 2024 Jail/Zones Production User Call is up:
We got an update from DCH about his jail-based CI system, discussed Jan's proposal to port #OpenBSD's sendsyslog(2) and syslog_r(3) to #FreeBSD for finer-grained logging, revisited Antranig's #Netgraph "retry" issue, and more!
"Don't forget to slam those Like and Subscribe buttons."
-
The July 9th, 2024 Jail/Zones Production User Call is up:
We got an update from DCH about his jail-based CI system, discussed Jan's proposal to port #OpenBSD's sendsyslog(2) and syslog_r(3) to #FreeBSD for finer-grained logging, revisited Antranig's #Netgraph "retry" issue, and more!
"Don't forget to slam those Like and Subscribe buttons."
-
The recording of the July 4th, 2024 #bhyve Production User Call is up:
We discussed the bhyve UART in illumos, bsdinstall #OpenZFS feature flag compatibility option in #bsdinstall, native encryption on a USB drive, Rob N's quiz development VMs, wifibox process supervision and grammar, the need for bhyve live migration, a solution to last week's Jails #NetGraph retry issue, MAC address remapping, #SNMP, and more!
"Don't forget to slam those Like and Subscribe buttons."
-
The recording of the July 4th, 2024 #bhyve Production User Call is up:
We discussed the bhyve UART in illumos, bsdinstall #OpenZFS feature flag compatibility option in #bsdinstall, native encryption on a USB drive, Rob N's quiz development VMs, wifibox process supervision and grammar, the need for bhyve live migration, a solution to last week's Jails #NetGraph retry issue, MAC address remapping, #SNMP, and more!
"Don't forget to slam those Like and Subscribe buttons."
-
The recording of the July 4th, 2024 #bhyve Production User Call is up:
We discussed the bhyve UART in illumos, bsdinstall #OpenZFS feature flag compatibility option in #bsdinstall, native encryption on a USB drive, Rob N's quiz development VMs, wifibox process supervision and grammar, the need for bhyve live migration, a solution to last week's Jails #NetGraph retry issue, MAC address remapping, #SNMP, and more!
"Don't forget to slam those Like and Subscribe buttons."
-
The recording of the July 4th, 2024 #bhyve Production User Call is up:
We discussed the bhyve UART in illumos, bsdinstall #OpenZFS feature flag compatibility option in #bsdinstall, native encryption on a USB drive, Rob N's quiz development VMs, wifibox process supervision and grammar, the need for bhyve live migration, a solution to last week's Jails #NetGraph retry issue, MAC address remapping, #SNMP, and more!
"Don't forget to slam those Like and Subscribe buttons."
-
The recording of the July 4th, 2024 #bhyve Production User Call is up:
We discussed the bhyve UART in illumos, bsdinstall #OpenZFS feature flag compatibility option in #bsdinstall, native encryption on a USB drive, Rob N's quiz development VMs, wifibox process supervision and grammar, the need for bhyve live migration, a solution to last week's Jails #NetGraph retry issue, MAC address remapping, #SNMP, and more!
"Don't forget to slam those Like and Subscribe buttons."
-
The June 25th, 2024 Jail/Zones Production User Call is up:
We had a long, in-depth #NetGraph performance debugging session and more!
"Don't forget to slam those Like and Subscribe buttons."
-
The June 25th, 2024 Jail/Zones Production User Call is up:
We had a long, in-depth #NetGraph performance debugging session and more!
"Don't forget to slam those Like and Subscribe buttons."