In reply to a post by BatBoy:

This is obviously a path around the firewall, I think you need a more sophisticated network structure. Alternatively, have you considered a combined modem/router?

Thanks BatBoy, as I thought. On the combined modem/router,, I have just "upgraded" from a couple of old modem routers, which were starting to show their age, to give me GB LAN and faster WLAN cababilities.
Also looking forward to FTTC, although not sure when I'll be able to get it yet.
I thought this would be a good and reasonably futureproof way forward.
To be fair, it's working pretty well as I can now stream multimedia around my LAN much more easily/quickly.
My only bug bear is that I can't monitor my ADSL stats as easily as I could on a one piece modem/router.
In honesty thats all I'm missing. Didn't realise it would be hard to achieve

I have adjusted my IP plan a bit having read the advice here. I now have

Modem:
WAN IP = Dynamic
Local IP = 192.168.0.64
Connection = 1483 Bridge IP VC Mux
DHCP = Disabled

Router:
IP = 192.168.0.1
Subnet = 255.255.255.92
DHCP Range = 192.168.0.2..62

I have set both modems up the same and tried both. In each case a can still not access the modem from within the LAN.
A tracert to the IP of the modem shoes it going straight to the IPS's routers and getting stuck there. So the modem isn't looking at the ip at all. Which I guess is what Ive asked it to do by setting it to bridge mode.
I'm wondering if Half Bridge/PPP IP Extension would fair any better?
Anyone any experience of it?

I have no idea what a subnet of 255.255.255.92 will do to your network.

In reply to a post by BatBoy:

I have no idea what a subnet of 255.255.255.92 will do to your network.

It will create a LAN segment of 192.168.0.2 to 192.168.0.62.
Everything else will be outside my LAN.

Probably too late now but what you should have done is keep a combined Modem and Router so you can access the modem stats. Feed the 100Mbps Ethernet into a small 8/12/16 port managed Gigabit switch. Connect all your devices to the switch and the traffic will move at high speeds on your network whilst only using the switch to router connection for inbound/outbound traffic and management requirements such as DHCP server requests.

Ah, the wonders of hindsight

In reply to a post by crey:

I have adjusted my IP plan a bit having read the advice here. I now have

Modem:
WAN IP = Dynamic
Local IP = 192.168.0.64
Connection = 1483 Bridge IP VC Mux
DHCP = Disabled

Router:
IP = 192.168.0.1
Subnet = 255.255.255.92
DHCP Range = 192.168.0.2..62

I'm sure you realise that in the subnet mask, 128+64=192 (typo: you've missed out the 1in the /26 subnet mask - 255.255.255.192)!
Furthermore, 192.168.0.64/26 is the network address - the first usable IP address is ...65.

But, going back to your opening post, now that you've unlocked the router functionality of the BT Voyager 190, why don't you configure it as a router and use the Asus as a switch + wireless access point.

Edited by JimmyBoy (Tue 04-Dec-12 14:07:20)

In reply to a post by prlzx:

...If someone has a router where they can add an IP alias (in the right subnet) to the WAN interface (something more advanced like pfSense would allow that) it might work, but would be impressed if the ASUS has this option?

As suggested by 'prlzx', adding an alias should work if the Asus OS allows you to do so.

e.g.

ifconfig eth1:1 192.168.1.2 netmask 255.255.255.252

eth1      Link encap:Ethernet  HWaddr F0:FF:F0:FF:F0:FF  
          inet addr:93.97.54.nnn  Bcast:93.97.55.255  Mask:255.255.248.0
          UP BROADCAST NOTRAILERS RUNNING  MTU:1500  Metric:1
          RX packets:89188367 errors:0 dropped:0 overruns:0 frame:0
          TX packets:54725209 errors:1 dropped:0 overruns:0 carrier:1
          collisions:0 txqueuelen:1000 
          RX bytes:663989107 (633.2 MB)  TX bytes:661912097 (631.2 MB)
          Interrupt:5 Base address:0xe400 Memory:e8203000-e8203038 

eth1:1    Link encap:Ethernet  HWaddr F0:FF:F0:FF:F0:FF  
          inet addr:192.168.1.2  Bcast:192.168.1.3  Mask:255.255.255.252
          UP BROADCAST NOTRAILERS RUNNING  MTU:1500  Metric:1
          Interrupt:5 Base address:0xe400 Memory:e8203000-e8203038

Modem stats.

Alternatively, when you feel the need to view the BT Voyager 190 line stats, reconfigure the Asus WAN port with a static IP address in the appropriate subnet (instead of PPPoE), obtain the stats, then reconfigure back to PPPoE. It's not an elegant solution, but it'll work.

Cheers JimmyBoy, a couple of things for me to study up on.
Your alternate config idea will work in the interim at any rate.
Thanks again

Update: I can certainly telnet into the Asus so config should be possible. Having trouble as many of the simple linux network commands don't see to be recognised.
I'm going to look through the Asus users forum and surrort pages see if I can find anything there

Edited by deleted (Tue 04-Dec-12 16:20:11)

Thought I had firewall set on both WAG320Ns, and definitely there on the load balancer. But now I have doubts.
I'll have to check when I get home.

In reply to a post by crey:

Router:
IP = 192.168.0.1
Subnet = 255.255.255.92
DHCP Range = 192.168.0.2..62

That is an invalid subnet mask. the last octet can only be certain numbers, which are 0, 128, 192, 224, 240, 248, 252, or 255 (254 would fit in the mathematical pattern that these numbers are formed from , but for other reasons is invalid in the last octet)

In reply to a post by BatBoy:

I have no idea what a subnet of 255.255.255.92 will do to your network.

It depends, in a well designed and programmed router it will be rejected as invallid and the superflous bits ignored and the subnet 255.255.255.0 would be used. In a badly programmed router that chose to use the net mask it would match some interesting numbers. Putting 192.168.0.1-192.168.0.3, 192.168.0.32-192.168.0.35, 192.168.0.128-192.168.0.131 and 192.168.0.160-192.168.0.162 in the same subnet with 192.168.0.0 as the network address and 192.168.0.163 as the broadcast address.

Or the router would crash.

Also most network drivers would fail to handle that subnet, either rejecting it as the well programmed router above did or failing to bring up a network connection.