meteor713 <(E-Mail Removed)> wrote:
> In Japan, FTTH service (NTT etc.) gives the dynamic subnet. The given
> subnet lasts quite long time, but if I reset the router, I get
> different subnet.
> If you search Google with "PPPoE IP-8", you will see the Japanese
> service about "OCN IP-8" service.
Okay, I did a search on google, and then did another search limiting
the language to English. :-/
There was a page at one site which described, in moderate detail,
an ISP PPPoE implementation that was very similar to your situation,
http://www.dslreports.com/faq/10245 for anyone interested. The
information on that page, together with your comments and an faq page
from
http://www.tldp.org/HOWTO/DSL-HOWTO/appendix.html, section
8.3.2. Fiber in the Loop (IFITL or FTTC, and FTTH)
are the basis for comments that follow. Now I understand much more than
when we started - but not really enough. This problem has turned out to
much more complex than I thought it was in the beginning.
....
> ppp1 Link encap:Point-to-Point Protocol
> inet addr:210.10.1.0 P-t-P:10.1.1.1 Mask:255.255.255.255
> UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
> RX packets:129 errors:0 dropped:0 overruns:0 frame:0
> TX packets:316 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:3
> RX bytes:8042 (7.8 Kb) TX bytes:18176 (17.7 Kb)
>>
>> Isn't 210.10.1.1 the router's PPP interface local IP address rather than
>> the (Ethernet) bridge's IP address?
> That is another problem.
> I setup eth0 and eth1 as bridge br0.
> After negotiate PPPoE, 210.10.1.1 ( In real, 210.10.1.0 assigned...
> anyway) IP is assigned to br0, not eth1. But RP-PPPoE just does that.
So it really is the bridge's (br0's) IP address. And apparently the
210.10.1.0 works as the IP address of the PPP interface. This is very
different from a PPPoE connection with a single public IP address, and
not yet common in the United States.
> Anyway, here is a full story why I tried to do this.
> NTT, or OCN service in Japan, They offer FTTH service, it's over
> 50Mbps in quite a low price. Sorrowfully, we must buy the router in
> quite an expensive price. the router's activity is just connect PPPoE
> on one ethernet (WAN) and responses dhcp client on the other ethernet
> (LAN). That's all. So I want to replace it with Linux box
I'm fairly sure that you need *some* device in addition to the Linux
box to transform the protocol used on the outside lines to the Ethernet
protocol the Linux box uses. The device is commonly called a modem.
Sometimes the modem also functions as a router and/or a bridge.
> In compact, the problem counts two.
> 1. How can RP-PPPoE get subnet local ip.
> 2. How can PPPoE assign his IP to br0.
Regrettably, it's become evident that I'm far below an experience level
required to provide any decent answers, if any exist. Unless there is a
reply from someone that has actually devised and implemented a workaround
that eliminates the router (by using a less expensive modem) then the
router appears to be necessary.
Personally I don't see why SNAT implemented with iptables shouldn't
work just fine for the LAN hosts, but you seem to think otherwise.
Well - perhaps the usable bandwidth allocated to a single public IP
address would be less than that for a subnet of public IP addresses.
And I'm sure you must have a good reason to want public addresses.
--
Clifford Kite Email: "echo
xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads:
http://ckite.no-ip.net/