Groups | Search | Server Info | Login | Register
Groups > comp.protocols.ppp > #134
| From | Marco Moock <mo01@posteo.de> |
|---|---|
| Newsgroups | comp.protocols.ppp |
| Subject | Re: pppd: reject IPCP or IP6CP configuration requests |
| Date | 2023-09-03 13:10 +0200 |
| Organization | A noiseless patient Spider |
| Message-ID | <ud1pji$snk4$1@dont-email.me> (permalink) |
| References | <09d30e8f-8c14-4bed-8b6b-cd27190d0070n@googlegroups.com> <ud1k71$rmk8$1@dont-email.me> <e6680e1c-666e-4444-8b5d-af982d8953dfn@googlegroups.com> |
Am 03.09.2023 um 03:45:23 Uhr schrieb michael gurevich: > On Sunday, September 3, 2023 at 12:38:42 PM UTC+3, Marco Moock wrote: > > Am 03.09.2023 um 01:48:30 Uhr schrieb michael gurevich: > > > > > I am trying to establish a ppp link for device running FreeRTOS > > > that has either an IPV6 or an IPV4 address with host running > > > linux. For example if device has only IPV6 address, sending pppd > > > command creates on host global IPV6 address and "not global" IPV4 > > > address. > > IIRC IPv6CP differs from IPCP (IPv4), only an interface identifier > > (64 bit, not an IPv6 address), is being negotiated. > > The client then creates a link-local (fe80::/64) address with that > > identifier. > > After that is send a router solicitation to get an router > > advertisement. This can (normally it does) include a prefix > > (2001:db8::/64) with the A flag (address autoconfiguration). It can > > now use that prefix to create the global address with the > > identifier exchanged via IPv6CP. > > > > The IPv6 router advertisement can have the M or O flag enabled, > > that means the client should contact a DHCPV6 server to get > > addresses or additional information like DNS or NTP servers. > My problem is a bit different, along with IPV6 link-local and IPV6 > global addresses, I got a link-local IPV4 address despite the fact > the device is lacking an IPV4 address initially. I wanted to prevent > it and the IPCP request was rejected , but the request kept coming > indefinitely. The it is a problem with IPCP, not IPv6CP. Does it really give you 0.0.0.0 back or did you replace it here not to show the IP? If you don't want IPv4 addressing, why don't you simply disable IPCP and only enable IPv6CP? Some systems (Windows by default, some Linux distributions too), create an APIPA link-local address from 169.254.0.0/16 if they don't get a normal IPv4 address by DHCP, PPP etc. If you don't want this, you have to configure the client's operating system.
Back to comp.protocols.ppp | Previous | Next — Previous in thread | Next in thread | Find similar
pppd: reject IPCP or IP6CP configuration requests michael gurevich <mihailgur11@gmail.com> - 2023-09-03 01:48 -0700
Re: pppd: reject IPCP or IP6CP configuration requests Marco Moock <mo01@posteo.de> - 2023-09-03 11:38 +0200
Re: pppd: reject IPCP or IP6CP configuration requests michael gurevich <mihailgur11@gmail.com> - 2023-09-03 03:45 -0700
Re: pppd: reject IPCP or IP6CP configuration requests Marco Moock <mo01@posteo.de> - 2023-09-03 13:10 +0200
Re: pppd: reject IPCP or IP6CP configuration requests michael gurevich <mihailgur11@gmail.com> - 2023-09-04 07:41 -0700
Re: pppd: reject IPCP or IP6CP configuration requests Marco Moock <mo01@posteo.de> - 2023-09-04 17:11 +0200
Re: pppd: reject IPCP or IP6CP configuration requests michael gurevich <mihailgur11@gmail.com> - 2023-09-04 23:19 -0700
Re: pppd: reject IPCP or IP6CP configuration requests Marco Moock <mo01@posteo.de> - 2023-09-05 08:59 +0200
Re: pppd: reject IPCP or IP6CP configuration requests michael gurevich <mihailgur11@gmail.com> - 2023-09-05 04:50 -0700
Re: pppd: reject IPCP or IP6CP configuration requests Marco Moock <mo01@posteo.de> - 2023-09-06 16:01 +0200
csiph-web