TomatoUSB

Being a newbie, could someone please indicate what steps I should
take to check why internet via "route modem" doesn't work,
whereas with the PVC in bridge mode it works.

Here are the details:
HW:
Hardware:
Modem/router - TP-Link TD-W8951ND
ip: 192.168.1.1

Router - Asus RT-N16 with TomatuUSB Shibby :
tomato-K26USB-1.28.RT-MIPSR2-112-AIO.trx
ip: 192.168.0.1

ISP uses PPPoE

what I did with "route modem":
1. Reset modem (but even after reset I see username/password
for authentication - I tried also with username/pw removed from modem).
2. Set up router:
2.1 PPPoE - username/pw
2.2 Route modem ip= 192.168.1.1
2.3 Change router IP to 192.168.0.1

Here is a part of the router log file - at the beginning with router in
"route modem" mode (no internet) and at the end with modem in
bridge mode (internet working).

no-conntrack ipset Tomato-helper auth
Jan 4 15:15:56 unknown daemon.info dnsmasq[12235]: asynchronous logging enabled, queue limit is 5 messages
Jan 4 15:15:56 unknown daemon.warn dnsmasq[12235]: no servers found in /etc/resolv.dnsmasq, will retry
Jan 4 15:15:56 unknown daemon.info dnsmasq[12235]: read /etc/hosts - 2 addresses
Jan 4 15:15:56 unknown daemon.info dnsmasq[12235]: read /etc/dnsmasq/hosts/hosts - 3 addresses
Jan 4 15:15:56 unknown daemon.err pppd[12226]: Unable to complete PPPoE Discovery
Jan 4 15:15:56 unknown daemon.info pppd[12226]: Terminating on signal 15
Jan 4 15:15:56 unknown daemon.info pppd[12226]: Exit.
Jan 4 15:15:57 unknown daemon.info pppd[12290]: Plugin rp-pppoe.so loaded.
Jan 4 15:15:57 unknown daemon.info pppd[12290]: RP-PPPoE plugin version 3.11 compiled against pppd 2.4.5
Jan 4 15:15:57 unknown user.info redial[12292]: Started. Time: 10
Jan 4 15:15:57 unknown daemon.notice pppd[12291]: pppd 2.4.5 started by root, uid 0
Jan 4 15:16:17 unknown user.info redial[12292]: WAN down. Reconnecting…
Jan 4 15:16:17 unknown daemon.info dnsmasq[12235]: exiting on receipt of SIGTERM
Jan 4 15:16:17 unknown user.debug init[1]: 182: pptp peerdns disabled
Jan 4 15:16:17 unknown daemon.info dnsmasq[12300]: started, version 2.67cs7 cachesize 1500
Jan 4 15:16:17 unknown daemon.info dnsmasq[12300]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset Tomato-helper auth
Jan 4 15:16:17 unknown daemon.info dnsmasq[12300]: asynchronous logging enabled, queue limit is 5 messages
Jan 4 15:16:17 unknown daemon.warn dnsmasq[12300]: no servers found in /etc/resolv.dnsmasq, will retry
Jan 4 15:16:17 unknown daemon.info dnsmasq[12300]: read /etc/hosts - 2 addresses
Jan 4 15:16:17 unknown daemon.info dnsmasq[12300]: read /etc/dnsmasq/hosts/hosts - 3 addresses
Jan 4 15:16:17 unknown daemon.err pppd[12291]: Unable to complete PPPoE Discovery
Jan 4 15:16:17 unknown daemon.info pppd[12291]: Terminating on signal 15
Jan 4 15:16:17 unknown daemon.info pppd[12291]: Exit.
Jan 4 15:16:18 unknown daemon.info pppd[12355]: Plugin rp-pppoe.so loaded.
Jan 4 15:16:18 unknown daemon.info pppd[12355]: RP-PPPoE plugin version 3.11 compiled against pppd 2.4.5
Jan 4 15:16:18 unknown daemon.notice pppd[12356]: pppd 2.4.5 started by root, uid 0
Jan 4 15:16:18 unknown user.info redial[12357]: Started. Time: 10
Jan 4 15:16:23 unknown daemon.info pppd[12356]: PPP session is 10540 (0x292c)
Jan 4 15:16:23 unknown daemon.warn pppd[12356]: Connected to 00:90:1a:a4:71:f5 via interface vlan2
Jan 4 15:16:23 unknown daemon.info pppd[12356]: Using interface ppp0
Jan 4 15:16:23 unknown daemon.notice pppd[12356]: Connect: ppp0 <—> vlan2
Jan 4 15:16:24 unknown daemon.notice pppd[12356]: PAP authentication succeeded
Jan 4 15:16:24 unknown daemon.notice pppd[12356]: peer from calling number 00:90:1A:A4:71:F5 authorized
Jan 4 15:16:24 unknown daemon.notice pppd[12356]: local IP address 89.201.189.98
Jan 4 15:16:24 unknown daemon.notice pppd[12356]: remote IP address 85.114.33.42
Jan 4 15:16:24 unknown daemon.notice pppd[12356]: primary DNS address 85.114.32.7
Jan 4 15:16:24 unknown daemon.notice pppd[12356]: secondary DNS address 85.114.32.8
Jan 4 15:16:24 unknown user.debug ip-up[12363]: 182: pptp peerdns disabled
Jan 4 15:16:24 unknown user.debug init[1]: 182: pptp peerdns disabled
Jan 4 15:16:24 unknown daemon.info dnsmasq[12300]: reading /etc/resolv.dnsmasq
Jan 4 15:16:24 unknown daemon.info dnsmasq[12300]: using nameserver 85.114.32.8#53
Jan 4 15:16:24 unknown daemon.info dnsmasq[12300]: using nameserver 85.114.32.7#53
Jan 4 15:16:24 unknown daemon.info dnsmasq[12300]: exiting on receipt of SIGTERM
Jan 4 15:16:24 unknown daemon.info dnsmasq[12366]: started, version 2.67cs7 cachesize 1500
Jan 4 15:16:24 unknown daemon.info dnsmasq[12366]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset Tomato-helper auth
Jan 4 15:16:24 unknown daemon.info dnsmasq[12366]: asynchronous logging enabled, queue limit is 5 messages
Jan 4 15:16:24 unknown daemon.info dnsmasq[12366]: reading /etc/resolv.dnsmasq
Jan 4 15:16:24 unknown daemon.info dnsmasq[12366]: using nameserver 85.114.32.8#53
Jan 4 15:16:24 unknown daemon.info dnsmasq[12366]: using nameserver 85.114.32.7#53
Jan 4 15:16:24 unknown daemon.info dnsmasq[12366]: read /etc/hosts - 2 addresses
Jan 4 15:16:24 unknown daemon.info dnsmasq[12366]: read /etc/dnsmasq/hosts/hosts - 3 addresses
Sep 13 07:29:35 unknown daemon.info pppd[12356]: System time change detected.
Sep 13 07:30:09 unknown cron.err crond[9505]: time disparity of 22978994 minutes detected
in bridge mode and at end

Perhaps I can clear up some misassumptions:

1. A "modem" such as the W8951ND is actually 3 devices:

1.1. Modem
1.2. Router
1.3. WiFi Radio

So, let's call it MRW; It consists of M==, =R=, and ==W.

2. A Modem converts data (Ethernet) to/from (ultra)sound for transmission over phone lines. A phone line switches circuits. Ethernet switches packets. In between there are such things as "virtual circuits". PVC="Permanent Virtual Circuit".

3. Setting up PPPoE means using the Ethernet link that the Modem has "sync"-ed, and making a PPP connection over that.
It should be obvious that once we have an ethernet link, that we can do all sorts of things with that link, including one or more PPP (IP) connections.

4. So, we can make a PPPoE connection in several ways:

4.1 From the =R= through the M==.
4.2 From an external (Tomato) router, through the M==, using one of the MRW's LAN ports.
4.3 From a PC, through the M==, using one of the MRW's LAN ports.

There is no technical reason why we could not have 5 separate PPPoE sessions simultaneously.

5. Please note that nothing about PPPoE has anything whatsoever to do with "Route Modem IP".
PPPoE has nothing at all to do with =R= or ==W.
"Route Modem IP" has nothing to do with M==.

If you have trouble setting up a PPPoE session from your router, "Route Modem IP" has nothing* do do with your problem!

"Route Modem IP" should really be called "Route =R=", because it gives you access to the router in the MRW.
Having access to the MRW's Router is completely irrelevant if you want to use only the MRW's Modem for PPPoE!

…

Sometimes the term "Bridge Mode" is used. This term is not well defined. But essentially it means "Set up the MRW in such a way that it behaves as if it were simply an M=="

Almost always, factory resetting a MRW will let it function as a M==.

…

Thus, if you are trying to set up a PPPoE session from a router, "Route Modem" is never ever a solution. It is completely irrelevant.

"Bridge Mode" is intended to be a solution, although it is usually not necessary.

Sometimes some settings in the MRW are necessary to make the M== establish an ethernet connection, such as PVC, etc.

…

Corrections invited.

wtf are you talking about?

OK, I have internet working now and would like to check that the
modem is not in bridge mode - how do I do this/what would be
the difference in what info I could access from the modem if it
was in bridge mode or not ?

I changed the title of the post as I was confused by two things
"bridge mode/PPPoE" and "bridge interface activated or not".

This is what I did to get internet working:
ON modem:
-remove authentication username/password
- leave in PPPoE mode
-activate bridge (I'm a newbie and am not sure how this is/isn't
connected/related with "bridge mode")
- set modem ip to 192.168.1.1
- connect modem lan -> router wan

ON router:
-set ip address to 192.168.0.1
-set internet authentication username/password
-set "Route modem" ip address to an ip address in the modem's
subnet (but not the modem address - this didn't work) eg
192.168.1.4 or 192.168.1.7 - this worked
-connect router -> switch ->pc

It's the same Planiwa that sprout nonsense in the linksysinfo forum, acting like a self-important guru while annoying the devs.

bump
Anyone can tell me what is the difference between what
I can / cannot do / information I can access with a modem which is/isn't
in bridge mode ?

The Original Poster had assumed that "Route Modem IP" is one way to make a PPPoE connection, and that "Bridge Mode" is another way to make a PPPoE connection.

The OP was of the opinion that there is a "Route Modem Mode" and a "Bridge Mode".

The OP then concluded that the "Route Modem Mode" "doesn't work", whereas "Bridge Mode" works.

The OP did not realize that "Route Modem IP" is not "a way to make a PPPoE connection".
.
.
"Route Modem IP" is a way of setting up the Tomato Router so that we can "talk to" the Modem+Router+WiFi device via the Tomato Router.

"Bridge Mode" is a way of setting up the Modem+Router+WiFi device so that it acts as just a Modem, with the Router and WiFi functions turned off.
.
.
What exactly is meant by "Bridge Mode", how consistent that meaning is, how to set up a particular Modem+Router+WiFi device for "Bridge Mode", and whether or not it is enough to reset such a device to Factory Defaults (and worry about optimization details later), these are all more or less interesting and relevant questions. Some answers can be found in the respective device manual.

What "Route Modem IP" is good for is also an interesting question, but not a directly related question.

…

Corrections invited.

why don't you go and play with your bucket and spade on the beach?

I thought the meanings were exactly as Planiwa indicated i.e.
"route modem ip" is to be able to talk to the modem from the router &
"Bridge Mode" is used to make the modem/router a plain modem (this may not
be technically all it is but I think what I assumed is basically on the
right track).

Could someone push me a bit forward by indicating how I should
check that the modem really is not in bridge mode / how can
I communicate to the modem via the router / what info
about the modem/connection can I access ?

I assume the modem is not in bridge mode as the encapsulation
is still set to PPPoE but I don't know what the "bridge interface
activated" means and how/whether it is in any way related
to bridge mode

if the thing isn't in bridge mode, you communicate with it using your pc since your pc will be in the same subnet and it's not a problem to do so.

if the thing is in bridged mode you can't talk to it via the pc - so we set it on a different subnet and use the route modem function to allow us to talk with it.

and it's easy to find all of this out using google