Re: [PLUG] Set up default gateway in kernel routing table [FIXED]
On Thu, 27 Sep 2018, Rich Shepard wrote: In slackware's rc.inet1.conf interface configuration file the default gateway is set on 192.168.55.4. Using this command: Louis, Tomas, Russell, et al.: Fixed the issue. The reason is that this motherboard does not find the eth0 interface, only eth1. I'll probably never learn why, and this is the first time in > 20 years of linux I've seen this. So, while I configured eth1 in /etc/rc.d/rc.inet1.conf, I did not realize that I needed to make the inet1 daemon aware of the different default interface. Running '/etc/rc.d/rc.inet1 eth1_start' made the software happy and I can now access the external world as well as other LAN hosts from the new desktop host. Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Set up default gateway in kernel routing table
I'd imagine that Rich is not using DHCP because he would like to be able to identify the hosts on his network and doesn't feel like doing local DNS/DHCP pair. If my hunch is right, I would suggest using centralized DHCP IPv4 and general network configuration for all hosts + let DHCP assign some defined IPs based on their MAC. That way, the user should see and manage the whole network configuration for all hosts in one place and avoid annoyances like this one AND still have stable/defined IPv4s. This is just a suggestion to consider, given that this recurring type of problem on the forum. Tomas On Thu, Sep 27, 2018, 12:07 PM Russell Senior wrote: > Just a fwiw, DHCP. Static network configuration works too, if you know what > you are doing. However, the empirical evidence suggests you would benefit > from DHCP. > > On Thu, Sep 27, 2018, 09:47 Rich Shepard wrote: > > >Having been a while since I last set routes I've lost a step when > > setting > > the default gateway. > > > >The routing table has both loopback and LAN routes. Now I need to set > > the > > default gateway and the kernel tells me there's a SIOCADDRT (address) > > error. > > > >In slackware's rc.inet1.conf interface configuration file the default > > gateway is set on 192.168.55.4. Using this command: > > > > route add default gw 192.168.55.4 > > > > returns the above error that the network is unreachable. > > > >The route man page example has a host name for the gateway and I've > > tried > > that, too, with the same result. > > > >What have I missed here? > > > >On a curious, somewhat related issue, while there's only one Ethernet > > port > > on the motherboard ifconfig sees it as eth1 rather than eth0. > > > > Rich > > ___ > > PLUG mailing list > > PLUG@pdxlinux.org > > http://lists.pdxlinux.org/mailman/listinfo/plug > > > ___ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Set up default gateway in kernel routing table
On Sep 27, 2018, at 1:26 PM, Rich Shepard wrote: > > On Thu, 27 Sep 2018, Louis Kowolowski wrote: > >> The IP 192.168.55.7 is NOT in the network 192.168.0.0/24 (mask of >> 255.255.255.0) The only valid IPs in 192.168.0.0/24 are 192.168.0.1-255 >> (don't try to allocate .255, its used). > > Louis, > > Mea culpa for not noticing this! Thanks for pointing out the obvious to > me. > > How do I delete the 192.168.0.0 route? Typing 'route del network > 192.168.0.0 eth1' returns 'network: host name lookup failure'. > I would expect something like: route delete -net 192.168.x.y/z where x is the 3rd octet, y is the 4th, and z is the subnet mask if there is no risk to running things, you may also be able to issue a route flush this will remove all route entries. be careful. -- Louis Kowolowskilou...@cryptomonkeys.org Cryptomonkeys: http://www.cryptomonkeys.com/ Making life more interesting for people since 1977 ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Set up default gateway in kernel routing table
Just a fwiw, DHCP. Static network configuration works too, if you know what you are doing. However, the empirical evidence suggests you would benefit from DHCP. On Thu, Sep 27, 2018, 09:47 Rich Shepard wrote: >Having been a while since I last set routes I've lost a step when > setting > the default gateway. > >The routing table has both loopback and LAN routes. Now I need to set > the > default gateway and the kernel tells me there's a SIOCADDRT (address) > error. > >In slackware's rc.inet1.conf interface configuration file the default > gateway is set on 192.168.55.4. Using this command: > > route add default gw 192.168.55.4 > > returns the above error that the network is unreachable. > >The route man page example has a host name for the gateway and I've > tried > that, too, with the same result. > >What have I missed here? > >On a curious, somewhat related issue, while there's only one Ethernet > port > on the motherboard ifconfig sees it as eth1 rather than eth0. > > Rich > ___ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Set up default gateway in kernel routing table [CLOSE]
On Thu, 27 Sep 2018, Rich Shepard wrote: I'll close this thread and move it to the slackware forum on LQ. The system took awhile to delete the incorrect default route. Just now I looked at the kernel routing table and found only the loopback route. Adding route add -net 192.168.55.0 netmask 255.255.255.0 route add default gw 192.168.55.4 looks like it fixed this issue. But, it still has no inet address, only an inet6 one. Sigh. Thanks to both of you, Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Set up default gateway in kernel routing table [CLOSE]
On Thu, 27 Sep 2018, Rich Shepard wrote: Part of the problem, or the entire problem, seems to be that eth1 has no inet(4) address, only an inet6 address. I don't know where this originates as /etc/rc.d/rc.inet1.conf has eth1 configured for 192.168.55.7 netmask 255.255.255.0, and the default gateway is 192.168.55.4. I'll close this thread and move it to the slackware forum on LQ. Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Set up default gateway in kernel routing table
On Thu, 27 Sep 2018, Rich Shepard wrote: How do I delete the 192.168.0.0 route? Typing 'route del network 192.168.0.0 eth1' returns 'network: host name lookup failure'. Part of the problem, or the entire problem, seems to be that eth1 has no inet(4) address, only an inet6 address. I don't know where this originates as /etc/rc.d/rc.inet1.conf has eth1 configured for 192.168.55.7 netmask 255.255.255.0, and the default gateway is 192.168.55.4. Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Set up default gateway in kernel routing table
On Thu, 27 Sep 2018, Louis Kowolowski wrote: The IP 192.168.55.7 is NOT in the network 192.168.0.0/24 (mask of 255.255.255.0) The only valid IPs in 192.168.0.0/24 are 192.168.0.1-255 (don't try to allocate .255, its used). Louis, Mea culpa for not noticing this! Thanks for pointing out the obvious to me. How do I delete the 192.168.0.0 route? Typing 'route del network 192.168.0.0 eth1' returns 'network: host name lookup failure'. Regards, Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Set up default gateway in kernel routing table
On Sep 27, 2018, at 12:51 PM, Rich Shepard wrote: > > On Thu, 27 Sep 2018, Louis Kowolowski wrote: > >> The gateway has to relate to an subnet that is configured on an interface. >> If you want to make the default route 192.168.55.4, one interface >> (physical, or logical) must be on the 192.168.xxx.xxx subnet, where >> 192.168.55.4 is included. For example, if the subnet is 192.168.55.0/24, >> then your interface would need also be in the 192.168.55.0/24 block. If >> the gateway is .4, and there are no other hosts/devices, your computer's >> interface could be configured with any IP between 192.168.55.1-3, >> 192.168.55.5-254. > > Thought I wrote this. The network is 192.168.0.0. This host is > 192.168.55.7, and the netmask is 255.255.255.0. > The IP 192.168.55.7 is NOT in the network 192.168.0.0/24 (mask of 255.255.255.0) The only valid IPs in 192.168.0.0/24 are 192.168.0.1-255 (don't try to allocate .255, its used). > The kernel routing table on my current desktop is: > > # route > Kernel IP routing table > Destination Gateway Genmask Flags Metric RefUse Iface > default router1.appl-ec 0.0.0.0 UG1 00 eth0 > loopback* 255.0.0.0 U 0 00 lo > 192.168.0.0 * 255.255.0.0 U 0 00 eth0 > > I'm trying to set the default gateway on the new desktop which already has > the loopback and network routes as above (except on that host the interface > is eth1). > > Rich > ___ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug -- Louis Kowolowskilou...@cryptomonkeys.org Cryptomonkeys: http://www.cryptomonkeys.com/ Making life more interesting for people since 1977 ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Set up default gateway in kernel routing table
On Thu, 27 Sep 2018, Louis Kowolowski wrote: The gateway has to relate to an subnet that is configured on an interface. If you want to make the default route 192.168.55.4, one interface (physical, or logical) must be on the 192.168.xxx.xxx subnet, where 192.168.55.4 is included. For example, if the subnet is 192.168.55.0/24, then your interface would need also be in the 192.168.55.0/24 block. If the gateway is .4, and there are no other hosts/devices, your computer's interface could be configured with any IP between 192.168.55.1-3, 192.168.55.5-254. Thought I wrote this. The network is 192.168.0.0. This host is 192.168.55.7, and the netmask is 255.255.255.0. The kernel routing table on my current desktop is: # route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface default router1.appl-ec 0.0.0.0 UG1 00 eth0 loopback* 255.0.0.0 U 0 00 lo 192.168.0.0 * 255.255.0.0 U 0 00 eth0 I'm trying to set the default gateway on the new desktop which already has the loopback and network routes as above (except on that host the interface is eth1). Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Set up default gateway in kernel routing table
On Thu, 27 Sep 2018, Rich Shepard wrote: Thought I wrote this. The network is 192.168.0.0. This host is 192.168.55.7, and the netmask is 255.255.255.0. The kernel routing table on my current desktop is: # route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface default router1.appl-ec 0.0.0.0 UG1 00 eth0 loopback* 255.0.0.0 U 0 00 lo 192.168.0.0 * 255.255.0.0 U 0 00 eth0 Just tried again: route add default gw 192.168.55.4 eth1 and get the SIOCADDRT: network not reachable error. From the new desktop I can ping the old desktop, but not the router. Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Set up default gateway in kernel routing table
On Thu, 27 Sep 2018, John Meissen wrote: What's the IP address and netmask of the system you're trying to set this on? 192.168.55.7netmask 255.255.255.0 ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Set up default gateway in kernel routing table
What's the IP address and netmask of the system you're trying to set this on? >Having been a while since I last set routes I've lost a step when setting > the default gateway. > >The routing table has both loopback and LAN routes. Now I need to set the > default gateway and the kernel tells me there's a SIOCADDRT (address) error. > >In slackware's rc.inet1.conf interface configuration file the default > gateway is set on 192.168.55.4. Using this command: > > route add default gw 192.168.55.4 > > returns the above error that the network is unreachable. > >The route man page example has a host name for the gateway and I've tried > that, too, with the same result. > >What have I missed here? > >On a curious, somewhat related issue, while there's only one Ethernet port > on the motherboard ifconfig sees it as eth1 rather than eth0. > > Rich > ___ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Set up default gateway in kernel routing table
The gateway has to relate to an subnet that is configured on an interface. If you want to make the default route 192.168.55.4, one interface (physical, or logical) must be on the 192.168.xxx.xxx subnet, where 192.168.55.4 is included. For example, if the subnet is 192.168.55.0/24, then your interface would need also be in the 192.168.55.0/24 block. If the gateway is .4, and there are no other hosts/devices, your computer's interface could be configured with any IP between 192.168.55.1-3, 192.168.55.5-254. > On Sep 27, 2018, at 11:44 AM, Rich Shepard wrote: > > Having been a while since I last set routes I've lost a step when setting > the default gateway. > > The routing table has both loopback and LAN routes. Now I need to set the > default gateway and the kernel tells me there's a SIOCADDRT (address) error. > > In slackware's rc.inet1.conf interface configuration file the default > gateway is set on 192.168.55.4. Using this command: > > route add default gw 192.168.55.4 > > returns the above error that the network is unreachable. > > The route man page example has a host name for the gateway and I've tried > that, too, with the same result. > > What have I missed here? > > On a curious, somewhat related issue, while there's only one Ethernet port > on the motherboard ifconfig sees it as eth1 rather than eth0. > > Rich > ___ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug -- Louis Kowolowskilou...@cryptomonkeys.org Cryptomonkeys: http://www.cryptomonkeys.com/ Making life more interesting for people since 1977 ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
[PLUG] Set up default gateway in kernel routing table
Having been a while since I last set routes I've lost a step when setting the default gateway. The routing table has both loopback and LAN routes. Now I need to set the default gateway and the kernel tells me there's a SIOCADDRT (address) error. In slackware's rc.inet1.conf interface configuration file the default gateway is set on 192.168.55.4. Using this command: route add default gw 192.168.55.4 returns the above error that the network is unreachable. The route man page example has a host name for the gateway and I've tried that, too, with the same result. What have I missed here? On a curious, somewhat related issue, while there's only one Ethernet port on the motherboard ifconfig sees it as eth1 rather than eth0. Rich ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Distinguishing instances of GUI file manager by color
You might look into the Meld application. It is file/directory compare tool with multiple panes that works pretty well although it can be a bit slow when working with large remote directories. It's available via apt-get on Debian. -- David On Thu, 2018-09-27 at 05:11 -0500, Richard Owlett wrote: > On 09/26/2018 04:52 AM, Richard Owlett wrote: > > I'm setting up a new machine and copying files from the old > > machine's > > home directory. At the same time I'm creating a new directory > > structure > > to better match how I work. > > > > I found it expedient to have at least three instances of the file > > manager open - [one for source directory and at least two for > > destination (sub)directories]. > > > > Suggestions? > > Is it even possible? > > > > Brief web search was not encouraging. But my search terms may have > > been > > the problem. Suggested search terms? > > > > TIA > > > > > > > I asked related questions on a Debian list and a Tcl/Tk group. > Suggestions tended towards a two pane file manager. > Having followed multiple chains of links caused me to rethink my > work > flow simplifying use of my current file manager (Caja). > > Long term, I'll pursue a two pane solution. > I've installed Krusader and GNOME Commander for testing. > > A chain of links led to 'filerunner' > [https://sourceforge.net/projects/filerunner/] which I downloaded and > am > reading the documentation to chose which options to initially chose. > > Usage appears to be intuitive - at least for my work style. > It is intrinsically highly configurable. > It is written in Tcl/Tk allowing/encouraging further customization. > > It will likely be my long term solution. > > Thanks for all the links. > > > > > > > ___ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Distinguishing instances of GUI file manager by color
On 09/26/2018 04:52 AM, Richard Owlett wrote: I'm setting up a new machine and copying files from the old machine's home directory. At the same time I'm creating a new directory structure to better match how I work. I found it expedient to have at least three instances of the file manager open - [one for source directory and at least two for destination (sub)directories]. Suggestions? Is it even possible? Brief web search was not encouraging. But my search terms may have been the problem. Suggested search terms? TIA > I asked related questions on a Debian list and a Tcl/Tk group. Suggestions tended towards a two pane file manager. Having followed multiple chains of links caused me to rethink my work flow simplifying use of my current file manager (Caja). Long term, I'll pursue a two pane solution. I've installed Krusader and GNOME Commander for testing. A chain of links led to 'filerunner' [https://sourceforge.net/projects/filerunner/] which I downloaded and am reading the documentation to chose which options to initially chose. Usage appears to be intuitive - at least for my work style. It is intrinsically highly configurable. It is written in Tcl/Tk allowing/encouraging further customization. It will likely be my long term solution. Thanks for all the links. ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
