Morning Dave, > It would be normal for a router to have a different IP address on the > downstream side to the upstream side with the upstream side being of the > 192.168.0/1.x type of address for your local LAN and the gateway and DNS is > then set to be the router.
Yep - I know that bit. That's how it was under Demon as well. The only difference now is that instead of the router being connected to the ADSL phone line (filter), I am now using one of the 4 Ethernet ports to connect the modem into the router. I can't see how it makes a difference (yet) as this set up works fine for Ethernet connections, just wireless is pants at the moment! The setup is cable->modem->router (port 1) Then the internal equipment (printer etc) will be connected to ports 2, 3 and 4 of the router. They are/will be set to fetch an IP address form the router. Now, this is interesting because they seem to be connecting directly to the Virgin network and not seing the 192.168.x.x addresses - they all appear to have an 81.x.x.x address instead. I wonder if this is because the upstream side is not coming into the router via the ADSL input - Hmmmmm. > I for instance currently > (and being cable it rarely changes) have a external IP address of > 82.22.94.182 supplied by Virgin, but all my local equipment on 192.168.1.x > addresses with both Gateway and DNS set to 192.168.1.1 9which is the router > address). That's what my wireless stuff looks like - but cannot connect. The wired stuff all appears to have an IP on the Virgin network - nothing local at all. > Just a thought - is your router set to act a DHCP server - you > want it to so it can deliver local addresses to your PC's, and that is also > where you set the address range to be used for the local subnet. I can't remember offhand. I'll check it and see. It certainly looks like that's how it works for the wireless anyway. Cheers, Norman. _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
