|
|
Sunday 6th Jan 2008 22:55:19
I think something's wrong with my headphones (and my network)
  
Today, after lunch, M****, A******, Pop/Mark and I did go for a walk around Bolton-le-Sands. We have the A****** unit potty trained (although often he'll require reminders), but still worry slightly what happens outside of the house and whether A****** knows the score. Thus, any suspect movement/utterance on A******'s part that could be interpreted as the need for the toilet tends to send us into a bit of a panic. Ah well. It's all good.
|     
So yeah . . . I think these last four photographs are largely of the same thing, but I couldn't decide upon my favourite, so I've left them all in. Hmmmmm. And tonight I did watch the film Sunshine, whilst M**** was enjoying a meal at the Borough with Liz and Mark. But yeah . . . Sunshine - damn fine film. I give it five stars. Tonight I have also been playing around with a computer (cobbled together with spare parts), trying to get it to behave as a router, but also as an exercise in networking, routing and such-like. However, something very puzzling is happening . . . It has two network cards, yeah? So far so good. Both of these networks cards are acknowledged by the operating system as eth0 and eth1 and seem to be working fine. I've given them static IP addresses, 192.168.0.10 and 192.168.0.11. From any machine in my network, I can ping and connect to that machine via either of these IP addresses. So all good so far. But then I started thinking, "But which network card is eth0 and which is eth1?" So, on my main PC I open up two terminal windows and in one I ping 192.168.0.10 and, in the other, ping 192.168.0.11. Both ping back, as expected. So, then comes the weird bit. I unplug one of the network cables and both ping requests carry on being answered. Eh?! I unplug the other network cable and both ping requests stop (destination host unreachable). So one of my network cards is both eth0 and eth1 and the other network card is just sitting there doing nothing. How is this possible? What is going on?
|
|
|
|
Comments received:
- Name: Simone_Death
- IP address: 195.137.60.155
- Date/time: Thursday 10th January 2008 23:08:48
- Comment: this is because the computer itself is acting as both IPs. The IP addresses haven't been assigned to each physical address but the system
or the system knows it is bridging the networks so when one route is unavailable it uses the other route to ping ie the hardware-software-hardware route. Maybe that's it... Let me know.
- Name: jonath
- IP address: 194.81.188.100
- Date/time: Friday 11th January 2008 10:47:50
- Comment: Yes, you've given me an idea here. I guess it's kind of clever that the PC is doing this, perhaps because one of the network cards isn't set-up correctly, so it's allowing one network card to act as two. Or something. Erm . . . which makes me think, "Perhaps the kernel isn't configured for both of these network cards." Time to recompile that pesky kernel.
- Name: Cary
- IP address: 62.6.152.72
- Date/time: Wednesday 16th January 2008 13:40:53
- Comment: Sunshine...very good film indeed!
- Name: philh
- IP address: 195.92.70.130
- Date/time: Thursday 17th January 2008 13:38:31
- Comment: Yeah, I think simone's right, if you want to make it act as a router you'll need to give it something to route. They should be on different subnets (ie 192.168.1.10 and 192.168.0.10, assuming they're class C).
- Name: jonath
- IP address: 192.168.0.50
- Date/time: Friday 18th January 2008 22:25:24
- Comment: I've ordered the DVD of Sunshine. It's a film I could watch a few more times yet. PhilH? Fluffy Phil? Or another Phil? It sounds like what you're saying is that the network cards aren't too important; what is more important is setting up the router to do, erm, routing, and that the networks will kind of follow. Is that right? I don't understand subnets and class C things. Help.
Add your comment (or not):
|
|
|
