• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Bridging connections...

Ichinisan

Ichinisan

Lifer
My computer is behind a Linksys WRT54G wireless router with DHCP enabled. I also have it connected to the file server via firewire. Windows has generated "Autoconfiguration" (169...) addresses for the firewire network connections. I can use Remote Desktop Connection (mstsc) to access the file server via it's Windows network name.

I thought that I should be able to bridge the Local Area Network (ethernet NIC) connection with the 1394 firewire to assign IP's via DHCP from the router and allow the file server to access the Internet.

Why won't it work?

The "host" computer (the one with that is connected to the file server via firewire and the router via CAT5 ethernet) has "Internet Connection" listed as an Internet Gateway in Network Connections along with the 1394 and LAN connections. Does this have something to do with UPnP? I'm not totally clear on what UPnP does, but my router says that it's enabled. I haven't changed any network settings on this default install of WinXP Pro SP2.

How can I set this up so that my file server can access the Internet through firewire?
 
Strange. I did exactly what I had done before and it worked. I guess I had to wait for Windows to generate autoconfiguration addresses, though I can't find where to go to manually specify *after* the bridge has been made.
 
Eh, it's not working afterall.

I bridged the two network connections (LAN and 1394). The Network Bridge gets an IP from my router, but the two network connections behind the new bridge do not get autoconfiguration addresses...no matter how long I wait.
 
When I would bridge my wireless card to my LAN card DHCP would assign a second IP address from my ISP to my other wireless-only PC (My cable co allowed multiple IP addresses over DHCP). Only problem was that there seemed to be some cascading packet-loss problem so it would become unusable after a few minutes, but it means that LAN bridged with 1394 SHOULD work regardless, right? No "autoconfiguration addresses", manual configuration or ICS required.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top