pie/ftth-tiscali-no-modem
2
1
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed typos

Browse Source
This commit is contained in:
pie
2022-02-06 20:49:46 +01:00
parent 6864ed7938
commit 72e8e22930
1 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@@ -47,15 +47,15 @@ and
(replace 123456 with your password) (replace 123456 with your password)
Finally you can switch on the service like: Finally you can switch on the service with:
``` ```
ppp call tiscali ppp call tiscali
``` ```
you can use `journalctl -f` and check whether things are going fine. and then use `journalctl -f` to check whether things are going fine.
Systemd automatization can be created with the help of [these scripts](https://gitlab.com/jimdigriz/debian-clearfog-gt-8k/-/blob/master/README.md). Systemd automation can be created with the help of [these scripts](https://gitlab.com/jimdigriz/debian-clearfog-gt-8k/-/blob/master/README.md).
## Long Story ## Long Story
@@ -86,7 +86,7 @@ The approach is [like this](https://wiki.wireshark.org/CaptureSetup/Ethernet#cap
The packets captured just after switching on the ZTE H388X are shown here: The packets captured just after powering on the ZTE H388X are shown here:
![packets](README.assets/packets.png) ![packets](README.assets/packets.png)
@@ -96,12 +96,12 @@ There are basically three steps:
* Yellow box: the PPP Initialization starts from the ZTE and is followed by an Offer from the Cisco server. * Yellow box: the PPP Initialization starts from the ZTE and is followed by an Offer from the Cisco server.
* Green box: the authentication, with CHAP protocol. * Green box: the authentication, with CHAP protocol.
When using `pppd` the first packet is a PADI, which looks exactly the same as the one in No. 7 above, except for the 802.1Q part shown by the blue arrow. That was indeed the trick: the server replies only is the PADI request comes from a VLAN with ID:835. When using `pppd`, the cleanup part is missing and the first packet is a PADI, which looks exactly like the one in packet No. 7 above, except for the 802.1Q part shown by the blue arrow. That was indeed the trick: the server replies only when the PADI request comes from a VLAN with ID 835.
Setting the PPP device to a newly created vlan with Creating the vlan with
``` ```
`ip link add link eth0 name eth0.835 type vlan id 835` `ip link add link eth0 name eth0.835 type vlan id 835`
``` ```
makes the Cisco server happy and it promptly replies to our PADI packet. and setting it as the device for the PPP connection makes the Cisco server happy: it promptly replies to our PADI packet and the connection is setup in less than a second.