home.social

Search

181 results for “nextgraph”

  1. 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: codeberg.org/maulanahirzan/Net
    Brew BSDCafe: brew.bsd.cafe/maulanahirzan/Ne

    !!! Run these script with extra precaution. I am not responsible for any broken system or data lost. You have been warned !!!

    #freebsd #netgraph #script #viewer

  2. 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: codeberg.org/maulanahirzan/Net
    Brew BSDCafe: brew.bsd.cafe/maulanahirzan/Ne

    !!! Run these script with extra precaution. I am not responsible for any broken system or data lost. You have been warned !!!

    #freebsd #netgraph #script #viewer

  3. 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: codeberg.org/maulanahirzan/Net
    Brew BSDCafe: brew.bsd.cafe/maulanahirzan/Ne

    !!! Run these script with extra precaution. I am not responsible for any broken system or data lost. You have been warned !!!

    #freebsd #netgraph #script #viewer

  4. 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?)

    #freebsd #netgraph

  5. 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?)

    #freebsd #netgraph

  6. 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?)

    #freebsd #netgraph

  7. 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?)

    #freebsd #netgraph

  8. 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.

    #freebsd #netgraph

  9. 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.

    #freebsd #netgraph

  10. 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.

    #freebsd #netgraph

  11. 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: codeberg.org/maulanahirzan/Net
    b. Brew : brew.bsd.cafe/maulanahirzan/Ne

    These 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 !!!

    #freebsd #netgraph #viewer

  12. 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: codeberg.org/maulanahirzan/Net
    b. Brew : brew.bsd.cafe/maulanahirzan/Ne

    These 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 !!!

    #freebsd #netgraph #viewer

  13. 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: codeberg.org/maulanahirzan/Net
    b. Brew : brew.bsd.cafe/maulanahirzan/Ne

    These 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 !!!

    #freebsd #netgraph #viewer

  14. 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: codeberg.org/maulanahirzan/Net
    b. Brew : brew.bsd.cafe/maulanahirzan/Ne

    These 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 !!!

    #freebsd #netgraph #viewer

  15. 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: codeberg.org/maulanahirzan/Net
    b. Brew : brew.bsd.cafe/maulanahirzan/Ne

    These 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 !!!

    #freebsd #netgraph #viewer

  16. 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.1

    What 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

    #freebsd #netgraph #troubleshooting

  17. 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.1

    What 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

    #freebsd #netgraph #troubleshooting

  18. 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.1

    What 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

    #freebsd #netgraph #troubleshooting

  19. 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.1

    What 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

    #freebsd #netgraph #troubleshooting

  20. 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.1

    What 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

    #freebsd #netgraph #troubleshooting

  21. 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

    #freebsd #netgraph

  22. 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

    #freebsd #netgraph

  23. 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

    #freebsd #netgraph

  24. 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

    #freebsd #netgraph

  25. still learning how to operate ngctl command. It is easy to create simple graph with tee and cisco. But need more information to creata the rest nodes #freebsd #netgraph

  26. still learning how to operate ngctl command. It is easy to create simple graph with tee and cisco. But need more information to creata the rest nodes #freebsd #netgraph

  27. still learning how to operate ngctl command. It is easy to create simple graph with tee and cisco. But need more information to creata the rest nodes #freebsd #netgraph

  28. still learning how to operate ngctl command. It is easy to create simple graph with tee and cisco. But need more information to creata the rest nodes #freebsd #netgraph

  29. The recording of the July 4th, 2024 #bhyve Production User Call is up:

    youtu.be/rLW5gRuXuBE

    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."

  30. Railway planning friends! Say goodbye to drawing netgraphs with a graphic design software or Excel. One of my favorite internal tools at work is now available as open source software:

    ✏️ The Netgraph Editor

    Draw your timetable concepts or ideas and share it with the community worldwide. Try it out here:

    ➡️ nge.flatland.cloud/

    Made possible by #SBBCFFFFS, #GroupeSNCF and #OpenRailAssociation. Thanks Adrian, Martin and all the other colleagues involved! 🙏