Groups | Search | Server Info | Login | Register


Groups > comp.ai.shells > #300

Re: AI success story

Subject Re: AI success story
Newsgroups alt.computer.workshop, comp.ai.shells
References <m75pv3Fc894U3@mid.individual.net> <vuuhq4$m7pb$2@dont-email.me>
From % <pursent100@gmail.com>
Date 2025-04-30 19:27 -0700
Message-ID <43WdnZljzpOZQY_1nZ2dnZfqnPadnZ2d@giganews.com> (permalink)

Cross-posted to 2 groups.

Show all headers | View raw


vallor wrote:
> On 27 Apr 2025 04:26:11 GMT, Creon <creon@creon.earth> wrote in
> <m75pv3Fc894U3@mid.individual.net>:
> 
>> Actually had a success story with AI to share.
>>
>> Using ChatGPT, regarding Linux, I was able to give it my current output
>> of "ifconfig -a" and have it generate an accurate netplan yaml file for
>> network configuration -- which worked.
>>
>> Then I had it add some policy routing, which also worked.
>>
>> I did this to renumber three servers.  The only snag was when I went to
>> reconfigure the Red Hat-based server...it was so old, it didn't support
>> Red Hat's more modern network configuration scriptlets.  So I had
>> ChatGPT walk me through writing a script to do the configuration, then
>> set up a systemd unit file to run the script when the networking service
>> started.  All done.
>>
>> I was pleasantly surprised at how accurate ChatGPT was with its
>> configuration directives, scripting, and unit file setup.
> 
> Here is the netplan yaml file, with IP addresses anonymized:
> 
> network:
>    version: 2
>    renderer: networkd
> 
>    ethernets:
>      eth0:
>        match:
>          macaddress: 00:11:22:33:44:55
>        set-name: eth0
>        addresses:
>          - 192.0.2.10/29         # Source IP 1
>          - 198.51.100.10/28      # Source IP 2
>        dhcp4: no
>        dhcp6: no
>        ipv6-link-local: [auto]
> 
>        routing-policy:
>          - from: 192.0.2.10
>            table: 100
>          - from: 198.51.100.10
>            table: 200
> 
>        routes:
>          # Table 100 for 192.0.2.10
>          - to: 0.0.0.0/0
>            via: 192.0.2.1
>            table: 100
>            metric: 100
>          - to: 192.0.2.0/29
>            scope: link
>            table: 100
> 
>          # Table 200 for 198.51.100.10
>          - to: 0.0.0.0/0
>            via: 198.51.100.1
>            table: 200
>            metric: 200
>          - to: 198.51.100.0/28
>            scope: link
>            table: 200
> 
>          # Fallback default route
>          - to: 0.0.0.0/0
>            via: 198.51.100.1
>            metric: 500
> 
>      eth1:
>        match:
>          macaddress: 00:11:22:33:44:66
>        set-name: eth1
>        addresses:
>          - 10.0.0.10/24
>        dhcp4: no
>        dhcp6: no
>        routes:
>          - to: 10.0.0.0/24
>            scope: link
> 
troll

Back to comp.ai.shells | Previous | NextPrevious in thread | Find similar


Thread

AI success story Creon <creon@creon.earth> - 2025-04-27 04:26 +0000
  Re: AI success story Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-04-27 05:03 +0000
    Re: AI success story David <BoaterDave@hotmail.co.uk> - 2025-04-27 06:58 +0100
      Re: AI success story Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-04-27 15:32 +0000
        Re: AI success story % <pursent100@gmail.com> - 2025-04-27 08:34 -0700
          Re: AI success story Brock McNuggets <brock.mcnuggets@gmail.com> - 2025-04-27 16:06 +0000
  Re: AI success story % <pursent100@gmail.com> - 2025-04-27 07:59 -0700
  Re: AI success story vallor <vallor@cultnix.org> - 2025-05-01 01:12 +0000
    Re: AI success story % <pursent100@gmail.com> - 2025-04-30 19:27 -0700

csiph-web