|
|
21.
|
|
|
USE PEER DNS
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../pppoeconf:372
|
|
|
22.
|
|
|
You need at least one DNS IP address to resolve the normal host names. Normally your provider sends you addresses of useable servers when the connection is established. Would you like to add these addresses automatically to the list of nameservers in your local /etc/resolv.conf file? (recommended)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../pppoeconf:373
|
|
|
23.
|
|
|
LIMITED MSS PROBLEM
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../pppoeconf:389
|
|
|
24.
|
|
|
Many providers have routers that do not support TCP packets with a MSS higher than 1460. Usually, outgoing packets have this MSS when they go through one real Ethernet link with the default MTU size (1500). Unfortunately, if you are forwarding packets from other hosts (i.e. doing masquerading) the MSS may be increased depending on the packet size and the route to the client hosts, so your client machines won't be able to connect to some sites. There is a solution: the maximum MSS can be limited by pppoe. You can find more details about this issue in the pppoe documentation. 
Should pppoe clamp MSS at 1452 bytes?
If unsure, say yes.
(If you still get problems described above, try setting to 1412 in the dsl-provider file.) |
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../pppoeconf:390
|
|
|
25.
|
|
|
DONE
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../pppoeconf:419
|
|
|
26.
|
|
|
Your PPPD is configured now. Would you like to start the connection at boot time?
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../pppoeconf:420
|
|
|
27.
|
|
|
ERROR
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../pppoeconf:437
|
|
|
28.
|
|
|
The interfaces file generated by pppoeconf appears to be invalid. This is probably because pppoeconf is unable to handle your original interfaces file. Should pppoeconf nevertheless change your interfaces file with the one that appears to be invalid?
If you agree, you will probably break your network connectivity after rebooting, and cause some local problems if lo is down. Your original interfaces file will be moved to $REALINTFILE~ so you can restore it.
If not, you will have to make sure that $iface is configured before starting your DSL connection and start the connection manually.
Note that this situation is not expected and you should consider submitting a bug report against pppoeconf including your original interfaces file and the one generated by pppoeconf. |
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../pppoeconf:438
|
|
|
29.
|
|
|
ESTABLISH A CONNECTION
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../pppoeconf:459
|
|
|
30.
|
|
|
Now, you can make a DSL connection with "pon dsl-provider" and terminate it with "poff". Would you like to start the connection now?
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../pppoeconf:460
|
