dasbrot
Goto Top

Kabel Deutschland Vodafone Wan Problem mit PFsense. Verbindung immer wieder weg

Hallo.

Ich habe ein riesen Problem an einigen Kabel Deutschland Anschlüssen.
Das Kabelmodem ist im Bridge Mode. Pfsense holt sich die externe feste IP via dhcp

Das Klappt mal Minuten, mal Stunden. Funktioniert dann aber so lange nicht, bis man mal das Wan Kabel zieht, oder renew anschubst.

Ein Ansatz war dieser fred https://forum.pfsense.org/index.php?topic=108531.0
Solution:
In my case it always takes about 3 minutes until the UPC dhcp server starts to respond again.
So all you have to do is go to: Interfaces > WAN
DHCP Client Configuration section
check Options Advanced Configuration
Set the Protocol timing Timeout higher.
I chose 1800 which is 30 minutes, but I wanted to be on the safe side.

Ich musste diesen Wert jedoch unter select-timeout eintragen. Nicht unter Timeout. ... Bei Timeout war die Verbindung nach 1 Minute wieder weg.
Aber das ergibt doch keinen Sin ? https://www.freebsd.org/cgi/man.cgi?query=dhclient.conf&sektion=5#PR ...

Da steht :
select-timeout time;
It is possible (some might say desirable) for there to be more
than one DHCP server serving any given network. In this case, it
is possible that a client may be sent more than one offer in
response to its initial lease discovery message. It may be that
one of these offers is preferable to the other (e.g., one offer
may have the address the client previously used, and the other
may not).

The select-timeout is the time after the client sends its first
lease discovery request at which it stops waiting for offers from
servers, assuming that it has received at least one such offer.
If no offers have been received by the time the select-timeout
has expired, the client will accept the first offer that arrives.

By default, the select-timeout is zero seconds - that is, the
client will take the first offer it sees.

Unter Timeout steht :

timeout time;
The timeout statement determines the amount of time that must
pass between the time that the client begins to try to determine
its address and the time that it decides that it is not going to
be able to contact a server. By default, this timeout is sixty
seconds. After the timeout has passed, if there are any static
leases defined in the configuration file, or any leases remaining
in the lease database that have not yet expired, the client will
loop through these leases attempting to validate them, and if it
finds one that appears to be valid, it will use that lease's
address. If there are no valid static leases or unexpired leases
in the lease database, the client will restart the protocol after
the defined retry interval.


Hat auch einen halben Tag lang funktioniert.(also select-timeout) Auch wenn dauernd
DHCPREQUEST on em0 to 88.134.228.130 port 67
DHCPREQUEST on em0 to 88.134.228.130 port 67

im Log stand.

DHCP Log Wan:

Sep 21 11:52:11	dhclient	36271	bound to 90.187.7.xx -- renewal in 2700 seconds.
Sep 21 11:52:11	dhclient		Creating resolv.conf
Sep 21 11:52:11	dhclient		RENEW
Sep 21 11:52:11	dhclient	36271	DHCPACK from 83.169.163.146
Sep 21 11:52:11	dhclient	36271	DHCPREQUEST on em0 to 255.255.255.255 port 67
Sep 21 11:41:33	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 11:37:20	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 11:34:03	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 11:26:48	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 11:23:46	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 11:20:43	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 11:19:28	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 11:18:17	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 11:17:40	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 11:17:03	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 11:16:44	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 11:16:32	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 11:16:15	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 11:15:41	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 11:15:27	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 11:15:14	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 11:15:05	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 11:14:33	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 11:14:22	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 11:14:15	dhclient	36271	DHCPREQUEST on em0 to 88.134.228.130 port 67
Sep 21 10:29:15	dhclient	30109	bound to 90.187.7.xx -- renewal in 2700 seconds.
Sep 21 10:29:15	dhclient		Creating resolv.conf
Sep 21 10:29:15	dhclient		/sbin/route add default 90.187.7.xx
Sep 21 10:29:15	dhclient		Adding new routes to interface: em0
Sep 21 10:29:15	dhclient		New Routers (em0): 90.187.7.xx
Sep 21 10:29:15	dhclient		New Broadcast Address (em0): 255.255.255.255
Sep 21 10:29:15	dhclient		New Subnet Mask (em0): 255.255.255.252
Sep 21 10:29:15	dhclient		New IP Address (em0): 90.187.7.xx
Sep 21 10:29:15	dhclient		ifconfig em0 inet 90.187.7.xx netmask 255.255.255.252 broadcast 255.255.255.255
Sep 21 10:29:15	dhclient		Starting add_new_address()
Sep 21 10:29:15	dhclient		REBOOT
Sep 21 10:29:15	dhclient	30109	DHCPACK from 83.169.163.146
Sep 21 10:29:15	dhclient	30109	DHCPREQUEST on em0 to 255.255.255.255 port 67
Sep 21 10:29:15	dhclient		PREINIT

Komisch ist, er fragt 88.134.228.130
Antworten tut : 83.169.163.146

Nachdem ich das Log kopiert habe war die Verbindung wieder weg. Ca. alle Stunde kommt die Verbindung wieder für einige Minuten zu stande.

Hat jemand eine Idee ?

Content-Key: 349692

Url: https://administrator.de/contentid/349692

Printed on: July 18, 2024 at 16:07 o'clock

Member: em-pie
em-pie Sep 21, 2017 at 10:41:46 (UTC)
Goto Top
Moin,

Bin jetzt kein Experte, aber wenn man dem Link glauben schenken darf, wäre eine spannende Frage, ob eurer pfSense virtualisiert oder nativ auf einem Stückchen Blech läuft...

Gruß
em-pie
Member: DasBrot
DasBrot Sep 22, 2017 at 06:01:10 (UTC)
Goto Top
Läuft auf nem kleinen Atom mit zwei mal Intel nic. Also nicht virtualisiert.