TCP/IP over Firewire hides other network connections

[marcus]

Hi!

Is it possible to configure IP over Firewire to work with IP over
Ethernet? And since I have a problem with this, what component (Windows
XP driver, router, etc.) may cause this problem when mixing Firewire
and Ethernet IPs?

I'm asking because I'm trying to backup my computers connected in a
network and interconnected by Firewire. However, all hosts connected in
a local network through a DHCP router is not visible if my "1394
connection" is active. If I inactivate it, all hosts over the local
network is visible and available (either by means of file sharing or
manually pinging them in the console). However, I have always access to
my Internet connection whether or not my 1394-connection is active or
not.

It is like Firewire connections and Ethernet connection cannot work
together. My DHCP router give out IPs for Ethernet connections in the
range a.b.c.100-199 and Firewire IPs are manually assigned from the
range a.b.c.200-299.

Thanks for any help
marcus

 

[Ron Lowe]

Hi!

Is it possible to configure IP over Firewire to work with IP over
Ethernet? And since I have a problem with this, what component (Windows
XP driver, router, etc.) may cause this problem when mixing Firewire
and Ethernet IPs?

I'm asking because I'm trying to backup my computers connected in a
network and interconnected by Firewire. However, all hosts connected in
a local network through a DHCP router is not visible if my "1394
connection" is active. If I inactivate it, all hosts over the local
network is visible and available (either by means of file sharing or
manually pinging them in the console). However, I have always access to
my Internet connection whether or not my 1394-connection is active or
not.

It is like Firewire connections and Ethernet connection cannot work
together. My DHCP router give out IPs for Ethernet connections in the
range a.b.c.100-199 and Firewire IPs are manually assigned from the
range a.b.c.200-299.

Thanks for any help
marcus

If both the Ethernet and Firewire interfaces both use the same subnet (
a.b.c ) then this will cause the problem. In this case, windows will have
2 routes to the same subnet, but on different interfaces. Windows will then
decide which interface to use based on the route metric, and if automatic
route metrics are enabled, the firewire will win because it's faster. So
all traffic to ANY a.b.c address will be routed down the firewire interface.

To be able to use both together, hse different subnets on each interface.
For example, if your ethernet is using 192.168.0.x with a mask of
255.255.255.0, try using 192.168.1.x with a mask of 255.255.255.0 on the
firewire.

So manually assign the firewire interface an address in the 192.168.1.x
range, and do the same for the other devices on the firewire segment of the
network.

Now, traffic to 192.168.0.x will go out the ethernet interface, but
192.168.1.x will go out the firewire interface.

 

[marcus]

That did the trick!
Thanks very much
/marcus