#linuxcnc Logs

Nov 06 2023

07:47 PM Tom_itx is now known as Tom_L
08:04 PM roycroft: silver is what most folks i know use
08:04 PM roycroft: if the fitment is good the joint will be almost invisible
09:13 PM CloudEvil: How much do you care about strength?
09:14 PM CloudEvil: I've used regular electrical solder in ghte past with adequate for what I needed it for results. (>>> epoxy)
09:55 PM Tom_L: JT-Cave, PR#36 is up
10:00 PM roycroft: electrical solder has almost no strength
10:00 PM roycroft: but some times that's enough
10:01 PM Tom_L: what happens if 2 devices have the same ip but connected to different lan cards?
10:03 PM CloudEvil: Unfortunately not fire.
10:05 PM Tom_L: the static lan ip being the same as a connected device on the other lan card
10:06 PM Tom_L: probably not the best thing to do... just wondered if they would interfere
10:06 PM CloudEvil: It can sometimes work depending on lots of stuff.
10:07 PM CloudEvil: It may be very fragile.
10:07 PM Tom_L: i was just doing some mesa card testing and noticed the ip i used is also used by another device
10:07 PM Tom_L: wasn't aware of it at the time
10:07 PM Tom_L: but the test passed
10:07 PM CloudEvil: Which ethernet address each device chooses as canonical for the IP address.
10:14 PM lcnc-relay: <plaidrabbit#0> As a general guess from knowing general linux code, it depends on how the routing is configured, but it's generally bad. Code can talk to multiple devices on multiple networks, but it has to be written to support it (by doing it's binding very carefully). Otherwise it's mostly luck if that situation works, and it'll be fragile.
10:15 PM norias: hmm
10:19 PM roycroft: i don't know what that is supposed to mean
10:20 PM roycroft: it reads to me like "a program can bind to multiple ip addresses, but you have to correctly code it to do so"
10:20 PM lcnc-relay: <plaidrabbit#0> a program can bind to multiple ip addresses, but you have to correctly code it to do so
10:26 PM lcnc-relay: <plaidrabbit#0> If you have two similar, but not exactly the same, you can specify the connect-from ip address in the call to bind(). Most code specifies the sin_addr.s_addr = htonl(INADDR_ANY), but there are other options available.
10:37 PM lcnc-relay: <plaidrabbit#0> But you can also specify routing to dodge some of the problems as well. You can configure your routing to route specific ip addresses to specific interfaces. So you can specify 10.0.0.1 to go out one interface, and 10.0.0.2 to go out another. But this is a system-wide setting, not application specific.
10:44 PM roycroft: there may be something that can be done with iptables to accomplish that, but i'm not terribly familiar with iptables
11:32 PM solarwind: what the FUCK the collet is back in its place in the collet rack
11:32 PM solarwind: but I'm the only person here
11:32 PM CloudEvil: Aliens.
11:32 PM roycroft: it went on a walkabout
11:32 PM solarwind: there's a real possibility I sleepwalk (sleep-machine?)
11:33 PM solarwind: there's no other way this is possible
11:33 PM roycroft: it found itself, and realised that it belonged in the sohp
11:33 PM solarwind: I'm being serious