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