[Fli4l_dev] Tarball und OPT_IGMP

[B. Sprenger]

Hallo zusammen,
 >> Dann habe ich den Router rebootet und danach fror das Bild wieder ein.
>> Ein Reboot des Mediareceivers hat auch nicht geholfen.
>>
>> Und was nun?
>
> Bis Freitag warten und die Änderungen im dhcp_client-Paket testen.


So, der Freitag ist rum und ich habe heute das neue Build (fli4l 
3.9.0-r31452-FFL-506) heruntergeladen, konfiguriert und installiert.

Fazit: Es funktioniert nicht, das Bild friert ein.

In der Base ist jetzt:
IP_ROUTE_N='0'

in der circuits. txt hatte ich zunächst:
CIRC_2_NAME='IPTV'
CIRC_2_TYPE='dhcp'
CIRC_2_TAGS='internet'
CIRC_2_NETS_IPV4_N='1'
CIRC_2_NETS_IPV4_1='193.158.34.0/23'
CIRC_2_USEPEERDNS='no'
CIRC_2_ACTIVE='yes'
CIRC_2_WAIT='5'
CIRC_2_DHCP_DAEMON='dhcpcd'

CIRC_2_DHCP_DEV='IP_NET_3_DEV'
CIRC_2_DHCP_STARTDELAY='0'



Nachdem es nicht funktionierte habe ich es dann ergänzt um:
CIRC_2_ROUTE_DEV='IP_NET_3_DEV'
CIRC_2_ROUTE_GATEWAY_IPV4='93.227.63.254'

Hat aber auch nichts gebracht.
Stimmt diese Konfiguration so?


Das SYSLOG dazu (Auszug)

daemon.info dhcp-client: DHCP event 'PREINIT'
dhcpcd-wrapper[9828]: circ2: waiting for dhcpcd with PID 10012
dhcp-client: sleeping 0 seconds
dhcp-client: DHCP event 'NOCARRIER'
dhcpcd[10012]: eth1.8: waiting for carrier
dhcpcd[10012]: eth1.8: carrier acquired
dhcpcd-wrapper[9828]: dhcpcd[10012]: eth1.8: waiting for carrier
dhcpcd-wrapper[9828]: dhcpcd[10012]: eth1.8: carrier acquired
dhcp-client: DHCP event 'CARRIER'
dhcp-client: ignoring dhcp event 'CARRIER'
dhcpcd[10012]: DUID 00:01:00:01:1b:4a:e7:b3:00:40:63:da:cf:32
dhcpcd[10012]: eth1.8: IAID 63:da:cf:32
dhcpcd-wrapper[9828]: dhcpcd[10012]: DUID 
00:01:00:01:1b:4a:e7:b3:00:40:63:da:cf:32
dhcpcd-wrapper[9828]: dhcpcd[10012]: eth1.8: IAID 63:da:cf:32
dhcpcd[10012]: eth1.8: soliciting an IPv6 router
dhcpcd-wrapper[9828]: dhcpcd[10012]: eth1.8: soliciting an IPv6 router
pppd[9761]: local IP address 79.255.39.131
pppd[9761]: remote IP address 217.0.119.41
pppd[9761]: primary DNS address 217.0.43.97
pppd[9761]: secondary DNS address 217.0.43.113
ip-up[10279]: executing ip-up scripts for circ1[ppp0]
ip-up[10279]: circuit circ1[ppp0] comes up with 79.255.39.131/32 routed 
over [79.255.39.131]-->[217.0.119.41]
ip-up[10279]: adding dynamic mapping circ1/ipv4 --> 79.255.39.131/32
dhcpcd[10012]: eth1.8: soliciting a DHCP lease
dhcpcd-wrapper[9828]: dhcpcd[10012]: eth1.8: soliciting a DHCP lease
dhcpcd[10012]: eth1.8: offered 93.227.44.174 from 193.158.137.14 `DHSTG001'
dhcpcd-wrapper[9828]: dhcpcd[10012]: eth1.8: offered 93.227.44.174 from 
193.158.137.14 `DHSTG001'
circuit_change_state: circuit circ1 changes state from ready to online
ip-up[10279]: executing /etc/ppp/ip-up050.conntrack
ip-up[10279]: conntrack v1.4.2 (conntrack-tools): 11 flow entries have 
been deleted.
ip-up[10279]: executing /etc/ppp/ip-up200.dns
ip-up[10279]: using nameserver 217.0.43.97
ip-up[10279]: using nameserver 217.0.43.113


[..]

Jul 5 18:43:37 fli4l daemon.info dhcpcd[10012]: eth1.8: leased 
93.227.44.174 for 86400 seconds
dhcpcd[10012]: eth1.8: adding route to 93.227.0.0/18
dhcpcd[10012]: eth1.8: adding route to 193.158.137.14/32 via 93.227.63.254
dhcpcd[10012]: eth1.8: adding route to 87.141.128.0/17 via 93.227.63.254
dhcpcd-wrapper[9828]: dhcpcd[10012]: eth1.8: leased 93.227.44.174 for 
86400 seconds
dhcpcd-wrapper[9828]: dhcpcd[10012]: eth1.8: adding route to 93.227.0.0/18
dhcpcd-wrapper[9828]: dhcpcd[10012]: eth1.8: adding route to 
193.158.137.14/32 via 93.227.63.254
dhcpcd-wrapper[9828]: dhcpcd[10012]: eth1.8: adding route to 
87.141.128.0/17 via 93.227.63.254
openvpn-NE: add chain in-ovpn-NE to INPUT
dhcp-client: DHCP event 'BOUND'
dhcp-client: new_broadcast_address='93.227.63.255'
dhcp-client: new_classless_static_routes='193.158.137.14/32 
93.227.63.254 87.141.128.0/17 93.227.63.254'
dhcp-client: new_dhcp_lease_time='86400'
dhcp-client: new_dhcp_message_type='5'
dhcp-client: new_dhcp_rebinding_time='75600'
dhcp-client: new_dhcp_renewal_time='43200'
dhcp-client: new_dhcp_server_identifier='193.158.137.14'
dhcp-client: new_ip_address='93.227.44.174'
dhcp-client: new_network_number='93.227.0.0'
dhcp-client: new_server_name='DHSTG001'
dhcp-client: new_subnet_cidr='18'
dhcp-client: Event: up, local: '93.227.44.174', remote: '93.227.63.254', 
prefix: '93.227.44.174/18'
ip-up[12325]: executing ip-up scripts for circ2[eth1.8]
ip-up[12325]: circuit circ2[eth1.8] comes up with 93.227.44.174/18 
routed over [93.227.44.174]-->[93.227.63.254]
ip-up[12325]: adding dynamic mapping circ2/ipv4 --> 93.227.44.174/18

[..]
fli4l boot finished - VERSION: 3.9.0-r31452-FFL-506 KERNEL: 3.15.3 ARCH: 
i686


Was könnte bei mir falsch laufen?
Ich vermute ja fast einen Fehler bei mir bzw. in meiner Konfiguration, 
aber ich kann nichts finden.

LG
Boris