Philip Blundell wrote:
>
> >But I wan't to have it as a point-to-point interface 192.168.1.153
>
> What is the actual behaviour you are trying to achieve?
Because the card is connected through a cross-over
cat5 cable to another computer.
Because if I use the netmask 255.255.255.0, it creates
a network route that interferes with the other network.
Example:
Machine A Machine B Machine C
192.168.1.152 192.168.1.153 192.168.1.154
All three computers are connected through with
a 10Mb coax network.
The Tulips are connected between machines A and B.
Each uses the same IP for both interfaces. If this
second link is marked as a point-to-point interface
then the correct route will be created. Then anything
from 192.168.1.152 to 192.168.1.153 will go through
the 100Mb link and anything else will go over the
coax.
The problem is of course that the interface insists
on being listed as a broadcast interface.
Actually, ifconfig shows:
eth1 Link encap:Ethernet HWaddr 00:00:F8:08:44:59
inet addr:192.168.2.152 Bcast:192.168.2.255
Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:9 dropped:0 overruns:0 carrier:9
Collisions:0
Interrupt:9 Base address:0x6500
But route shows:
192.168.1.153 0.0.0.0 255.255.255.255 UH 0 0 0
eth1
So the right route is being created. So the bug is in ifconfig
displaying broadcast when it isn't.
>
> p.
I hope I'm making sense here...
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
