Odd networking problem
Sun and said:
...wrong. Ethernet in its original implementation was a *broadcast* medium0, meaning that all packets sent to X.Y.Z.W would be received by all interfaces on X.Y.Z.0 if the subnet mask was 255.255.255.0 . If you have 2 NICs in the same machine, they need to be on different subnets; otherwise routing and so forth get really confused. That's probably what's behind the symptoms you're seeing.
What are you trying to do here? Ethernet bonding, where 2 NICs behave as if they were a single interface? That requires some additional setup. Would you like it if you had one interface that had more than one IP? That's possible without bonding, but it requires some additional ifconfig commands to set the aliases up. Say exactly what it is that you want to do, provide specifics, and someone will probably be able to tell you how to achieve it. HTH,
No, in general. GUI programs are meant to be "user" friendly, where "user" != "programmer". Most GUIs are not designed with scriptability in mind. Yes, it is possible to write a program...
On Tue, 16 Aug 2005 20:41:04 +0200, Tristan Miller It was just the most basic example, and of...
0 Now that thicknet, thinnet, and hubs are obsolete, this is no longer really true. Machines still have to behave as if it were because of backwards combatability.
-- Matt GThere is no Darkness in Eternity-But only Light too dim for us to see Brainbench MVP for Linux Admin mail: TRAP + SPAN don't belong ----------------------------- penguins, is Tux." --MegaHAL