[10:25] Morning [13:11] Morning peoples, dogs, turkeys and everything else [16:35] morning [17:26] afternoon [19:57] is there an easy way to host a router through your linux desktop? [19:57] I need to basically emulate a local network to access a weird device which has an assigned IP address I can't get on my work network [19:57] so I was thinking of just faking it intothinking it was on a local network to configure it [20:02] Create a virtual bridge and add a network adapter on the same subnet as the network device. [20:02] If you can change the IP on the device though then that is the complicated way to do it. Just give your workstation a static IP on the same subnet, update the device, and then change your workstation settings back [20:05] ah [20:06] can I keep it off the network? [20:14] Yes. Plug your network device directly into your workstation. Traditionally you needed a crossover cable for this but most network devices now have auto-polarity so a patch cable is probably sufficient. [20:16] you can also add a route to access wrong-subnet devices on your local network. [20:16] using your ip as the gateway. [20:17] Can you? I don't know how to set up advanced routing in Linux. How does the kernel know to forward packets to the other subnet when the route sends them back to your adapter? [20:19] And how does it do that without an adapter on that subnet? [20:19] basically at this point i have it plugged in th [20:19] that's it [20:20] ChinnoDog: I thought you were a networking expert! [20:21] I am MutantTurkey but I haven't set up a full fledged Linux router before. Hence the questions. [20:22] Plug the thing into your workstation already. [20:25] Done [20:25] on the thing there are two of the network LED's on, green is solid, gthe porange blinking slowly [20:25] so it's connecte [20:27] ChinnoDog: you have to be on a flat network, but as long as you are the ip doesn't matter. [20:27] ChinnoDog: it's plugged in, but nothing comes up automatically of course [20:27] ChinnoDog: I've done this tons of times while working with SAN hardware and such. [20:28] you just do a route add, and delete it when you're done. [20:28] add a route to where? [20:28] That is interesting JonathanD. I'll have to research that more. [20:28] MutantTurkey: I usually do it directly to the piece of equipment I want to talk to. [20:29] MutantTurkey: that only works if you want to add your device to the network which you already said you don't. You want to access it off-network which you can do now if you know the IP. [20:29] on the "know the ip" side, I've had reasonable success firing up wireshark while connected direclty and bouncing hte whatever-it-is [20:36] wireshark isn't giving me any output [20:37] MutantTurkey: if you get nothing at all, it might be listening in the wrong place or something. [20:37] dmesg gives me e1000e: eth0 NIC Link is UP 100Mbps Full Duplex. Flow Conrol None. [20:37] Whats your client machine. [20:37] my lappy [20:37] What OS? [20:37] ubuntu somethin [20:38] I'd expect at least to see your ubuntu talking a little. [20:38] i'll retry as root [20:39] it tries to do a dhcp discover [20:40] You're seeing your traffic then, at least. [20:40] So now you probably want to bounce the other device and see if it talks. [20:40] what does bounce the other device mean? [20:45] turn it on and off [20:45] or unplug the net cable and plug it back in, you can try that too. [20:45] I suppose you could just scan for IPs if you're sure you're in the right subnet. [21:05] okay so it's trying to dhcp to my laptop [21:05] my laptop needs to return something giving it an ip address I assume [21:05] what daemon does that though? [21:11] hmmm so it looks like it has a source 192.168.0.10 on netcat [21:11] but how do I connect to that? [21:30] Use $client to connect to the $device. [21:30] You still haven't told us what the device is. [21:31] Networked bacon cooking machine? [21:31] * ChinnoDog telnets to 192.168.0.10, issues order to cook two slices of bacon extra crispy