rc.inet1, routes, default gateways
This post is directed to Eric (Alien Bob) because I think you played a significant role in writing the 10.2 version of the rc.inet1 script.
A default gateway is established in the new script. This probably is a reasonable approach for people running dedicated servers and gateways. However, I run my simple two-box network as peer-to-peer. I also still am stuck connecting with dialup.
In my case, I dial out with either box and that box then becomes the LAN gateway for that session.
However, the KPPP dialer and the PPP daemon will not override any default gateways. This is incorrectly designed IMO, but that's life. To overcome this default gateway hurdle, I had to write my own script to disable all default gateways and then reestablish a simpler static route for the LAN. This way I maintain LAN communications, but do not establish a default gateway. Then when I dial out, KPPP and PPPD have no problems connecting and can establish the ppp0 device as the default route.
In my script I run route add -net 192.168.1.0 netmask 255.255.255.0 gw 192.168.1.xx, where xx is the static NIC address of the opposite box.
I'm guessing that although peer-to-peer LANs are far outnumbered by client-server LANs, peer-to-peer LANs still exist in small business offices. I'm also guessing that like me, that any one or more of those boxes can dial out. Thus, they would be in a similar bind as me.
In conclusion, possibly could future versions of Slack be designed such that the rc.inet1 script works for both types of LANs? I'm no networking guru, but possibly another option in the rc.inet.conf file might be used to distinguish whether peer-to-peer or client-server is being used and whether the primary internet connection is by modem. Then based upon those elements, revising rc.inet1 gateway functions to configure the gateway as either static or default.