ComputerBase Menü
Aktuelles

Router trennt sich ständig vom LAN - dann autom. reconnect

A

amethist

Newbie
Registriert
Okt. 2012
Beiträge
3
Hallo,

ich suche Hilfe für folgendes Problem:

Seit dem ich einen Router habe, trennt Windows (oder der Router oder Netzwerkkarte?) fortlaufend die LAN-Verbindung um nur ganz kurz danach (1 Sekunde oder so) wieder das Lan (und damit das Internet) aufzuschalten. Ich habe kein "echtes" Netzwerk sondern z.Zt. nur 1 PC - Router - Modem - Internet.
Die Internetverbindung nur über das Modem ohne den Router dazwischen (per pppoe) funktioniert ohne Probleme.

Ich habe sogar schon den ASUS-Support zu diesem Problem angeschrieben - die meinen nur schick das Geräte zurück - evtl. Hardwarefehler. Das habe ich auch gemacht! Dies hier ist mein 2.Router - mit dem selben Problem! (Soll ich jetzt lachen oder weinen?) Deswegen vermute ich eher kein Hardwarefehler sondern einen Einstellungsfehler. Evtl. hat die Gemeinde ja einen besseren Vorschlag? Mich irritieren z.B. die vielen Einträge zu dnsmasq im Protokoll, s.u. (im Grunde endet jede Trennung mit diesem Block)

Windows 7 prof. / Router: ASUS RT-N66U mit neuester Firmware (4.0.0.4.220). / GLan: Realtek Onboard auf Asrock 870 Extreme3 / Verbindung über Kabel (nicht Wireless).

Folgendes Protokoll habe ich vom Router:

Jan 1 00:00:09 syslogd started: BusyBox v1.17.4
Jan 1 00:00:09 kernel: klogd started: BusyBox v1.17.4 (2012-09-06 17:04:58 CST)
Jan 1 00:00:09 kernel: Linux version 2.6.22.19 (root@asus) (gcc version 4.2.4) #1 Thu Sep 6 17:25:51 CST 2012
Jan 1 00:00:09 kernel: CPU revision is: 00019749
Jan 1 00:00:09 kernel: Determined physical RAM map:
Jan 1 00:00:09 kernel: memory: 07fff000 @ 00000000 (usable)
Jan 1 00:00:09 kernel: memory: 08000000 @ 87fff000 (usable)
Jan 1 00:00:09 kernel: Zone PFN ranges:
Jan 1 00:00:09 kernel: Normal 0 -> 131072
Jan 1 00:00:09 kernel: HighMem 131072 -> 589823
Jan 1 00:00:09 kernel: early_node_map[2] active PFN ranges
Jan 1 00:00:09 kernel: 0: 0 -> 32767
Jan 1 00:00:09 kernel: 0: 557055 -> 589823
Jan 1 00:00:09 syslog: module ledtrig-usbdev not found in modules.dep
Jan 1 00:00:09 syslog: module leds-usb not found in modules.dep
Jan 1 00:00:09 kernel: Built 1 zonelists. Total pages: 65535
Jan 1 00:00:09 kernel: Kernel command line: root=/dev/mtdblock2 noinitrd console=ttyS0,115200
Jan 1 00:00:09 kernel: Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
Jan 1 00:00:09 kernel: Primary data cache 32kB, 4-way, linesize 32 bytes.
Jan 1 00:00:09 kernel: Synthesized TLB refill handler (20 instructions).
Jan 1 00:00:09 kernel: Synthesized TLB load handler fastpath (32 instructions).
Jan 1 00:00:09 kernel: Synthesized TLB store handler fastpath (32 instructions).
Jan 1 00:00:09 kernel: Synthesized TLB modify handler fastpath (31 instructions).
Jan 1 00:00:09 kernel: PID hash table entries: 512 (order: 9, 2048 bytes)
Jan 1 00:00:09 kernel: CPU: BCM5300 rev 1 pkg 0 at 600 MHz
Jan 1 00:00:09 kernel: Using 300.000 MHz high precision timer.
Jan 1 00:00:09 kernel: console [ttyS0] enabled
Jan 1 00:00:09 kernel: Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Jan 1 00:00:10 kernel: Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Jan 1 00:00:10 kernel: Memory: 255016k/131068k available (2445k kernel code, 6820k reserved, 494k data, 200k init, 131072k highmem)
Jan 1 00:00:10 kernel: Mount-cache hash table entries: 512
Jan 1 00:00:10 kernel: NET: Registered protocol family 16
Jan 1 00:00:10 kernel: PCI: Initializing host
Jan 1 00:00:10 kernel: PCI: Reset RC
Jan 1 00:00:10 kernel: PCI: Initializing host
Jan 1 00:00:10 kernel: PCI: Reset RC
Jan 1 00:00:10 kernel: PCI: Fixing up bus 0
Jan 1 00:00:10 kernel: PCI/PCIe coreunit 0 is set to bus 1.
Jan 1 00:00:10 kernel: PCI: Fixing up bridge
Jan 1 00:00:10 kernel: PCI: Fixing up bridge
Jan 1 00:00:10 kernel: PCI: Enabling device 0000:01:00.1 (0004 -> 0006)
Jan 1 00:00:10 kernel: PCI: Fixing up bus 1
Jan 1 00:00:10 kernel: PCI/PCIe coreunit 1 is set to bus 2.
Jan 1 00:00:10 kernel: PCI: Fixing up bridge
Jan 1 00:00:10 kernel: PCI: Fixing up bridge
Jan 1 00:00:10 kernel: PCI: Enabling device 0000:02:00.1 (0004 -> 0006)
Jan 1 00:00:10 kernel: PCI: Fixing up bus 2
Jan 1 00:00:10 kernel: NET: Registered protocol family 2
Jan 1 00:00:10 kernel: Time: MIPS clocksource has been installed.
Jan 1 00:00:10 kernel: IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 00:00:10 kernel: TCP established hash table entries: 4096 (order: 3, 32768 bytes)
Jan 1 00:00:10 kernel: TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
Jan 1 00:00:10 kernel: TCP: Hash tables configured (established 4096 bind 4096)
Jan 1 00:00:10 kernel: TCP reno registered
Jan 1 00:00:10 kernel: highmem bounce pool size: 64 pages
Jan 1 00:00:10 kernel: squashfs: version 3.2-r2 (2007/01/15) Phillip Lougher
Jan 1 00:00:10 kernel: io scheduler noop registered (default)
Jan 1 00:00:10 kernel: HDLC line discipline: version $Revision: 4.8 $, maxframe=4096
Jan 1 00:00:10 kernel: N_HDLC line discipline registered.
Jan 1 00:00:10 kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
Jan 1 00:00:10 kernel: serial8250: ttyS0 at MMIO 0xb8000300 (irq = 8) is a 16550A
Jan 1 00:00:10 kernel: serial8250: ttyS1 at MMIO 0xb8000400 (irq = 8) is a 16550A
Jan 1 00:00:10 kernel: PPP generic driver version 2.4.2
Jan 1 00:00:10 kernel: MPPE/MPPC encryption/compression module registered
Jan 1 00:00:10 kernel: NET: Registered protocol family 24
Jan 1 00:00:10 kernel: PPPoL2TP kernel driver, V0.18.3
Jan 1 00:00:10 kernel: PPTP driver version 0.8.5
Jan 1 00:00:10 kernel: Physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank
Jan 1 00:00:10 kernel: Amd/Fujitsu Extended Query Table at 0x0040
Jan 1 00:00:10 kernel: Physically mapped flash: CFI does not contain boot bank location. Assuming top.
Jan 1 00:00:10 kernel: number of CFI chips: 1
Jan 1 00:00:10 kernel: cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
Jan 1 00:00:10 kernel: Flash device: 0x2000000 at 0x1c000000
Jan 1 00:00:10 kernel: Creating 5 MTD partitions on "Physically mapped flash":
Jan 1 00:00:10 kernel: 0x00000000-0x00040000 : "pmon"
Jan 1 00:00:10 kernel: 0x00040000-0x01fe0000 : "linux"
Jan 1 00:00:10 kernel: 0x00168c90-0x01680000 : "rootfs"
Jan 1 00:00:10 kernel: 0x01fe0000-0x02000000 : "nvram"
Jan 1 00:00:10 kernel: 0x01f40000-0x01fe0000 : "jffs2"
Jan 1 00:00:10 kernel: Found an serial flash with 0 0KB blocks; total size 0MB
Jan 1 00:00:10 kernel: sflash: found no supported devices
Jan 1 00:00:10 kernel: dev_nvram_init: _nvram_init
Jan 1 00:00:10 kernel: _nvram_init: allocat header: 2280783872, size= 65536
Jan 1 00:00:10 kernel: sdhci: Secure Digital Host Controller Interface driver
Jan 1 00:00:10 kernel: sdhci: Copyright(c) Pierre Ossman
Jan 1 00:00:10 kernel: u32 classifier
Jan 1 00:00:10 kernel: OLD policer on
Jan 1 00:00:10 kernel: Netfilter messages via NETLINK v0.30.
Jan 1 00:00:10 kernel: nf_conntrack version 0.5.0 (2048 buckets, 16384 max)
Jan 1 00:00:10 kernel: ipt_time loading
Jan 1 00:00:10 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 00:00:10 kernel: net/ipv4/netfilter/tomato_ct.c [Sep 6 2012 17:25:17]
Jan 1 00:00:10 kernel: NET: Registered protocol family 1
Jan 1 00:00:10 kernel: NET: Registered protocol family 10
Jan 1 00:00:10 kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 00:00:10 kernel: NET: Registered protocol family 17
Jan 1 00:00:10 kernel: 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
Jan 1 00:00:10 kernel: All bugs added by David S. Miller <davem@redhat.com>
Jan 1 00:00:10 kernel: VFS: Mounted root (squashfs filesystem) readonly.
Jan 1 00:00:10 kernel: Freeing unused kernel memory: 200k freed
Jan 1 00:00:10 kernel: Warning: unable to open an initial console.
Jan 1 00:00:10 kernel: ctf: module license 'Proprietary' taints kernel.
Jan 1 00:00:10 kernel: et_module_init: passivemode set to 0x0
Jan 1 00:00:10 kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.100.138.20
Jan 1 00:00:10 kernel: wl_module_init: passivemode set to 0x0
Jan 1 00:00:10 kernel: PCI: Enabling device 0000:01:01.0 (0000 -> 0002)
Jan 1 00:00:10 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 5.100.138.20
Jan 1 00:00:10 kernel: PCI: Enabling device 0000:02:01.0 (0000 -> 0002)
Jan 1 00:00:10 kernel: eth2: Broadcom BCM4331 802.11 Wireless Controller 5.100.138.20
Jan 1 00:00:10 kernel: Algorithmics/MIPS FPU Emulator v1.5
Jan 1 00:00:10 kernel: usbcore: registered new interface driver usbfs
Jan 1 00:00:10 kernel: usbcore: registered new interface driver hub
Jan 1 00:00:10 kernel: usbcore: registered new device driver usb
Jan 1 00:00:10 kernel: SCSI subsystem initialized
Jan 1 00:00:10 kernel: Initializing USB Mass Storage driver...
Jan 1 00:00:10 kernel: usbcore: registered new interface driver usb-storage
Jan 1 00:00:10 kernel: USB Mass Storage support registered.
Jan 1 00:00:10 kernel: ufsd: driver 8.5 (U85_S[2011-11-01-13:41:37]) LBD=ON with ioctl loaded at c0215000
Jan 1 00:00:10 kernel: NTFS support included
Jan 1 00:00:10 kernel: Built_for__asus_n66u_2011-10-27
Jan 1 00:00:10 kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jan 1 00:00:10 kernel: ehci_hcd 0000:00:04.1: EHCI Host Controller
Jan 1 00:00:10 kernel: ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 1
Jan 1 00:00:10 kernel: ehci_hcd 0000:00:04.1: EHCI Fastpath: New EHCI driver starting
Jan 1 00:00:10 kernel: ehci_hcd 0000:00:04.1: irq 6, io mem 0x18004000
Jan 1 00:00:10 kernel: ehci_hcd 0000:00:04.1: USB 0.0 started, EHCI 1.00
Jan 1 00:00:10 kernel: usb usb1: configuration #1 chosen from 1 choice
Jan 1 00:00:10 kernel: hub 1-0:1.0: USB hub found
Jan 1 00:00:10 kernel: hub 1-0:1.0: 2 ports detected
Jan 1 00:00:10 kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jan 1 00:00:11 kernel: ohci_hcd 0000:00:04.0: OHCI Host Controller
Jan 1 00:00:11 kernel: ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 2
Jan 1 00:00:11 kernel: ohci_hcd 0000:00:04.0: irq 6, io mem 0x18009000
Jan 1 00:00:11 kernel: usb usb2: configuration #1 chosen from 1 choice
Jan 1 00:00:11 kernel: hub 2-0:1.0: USB hub found
Jan 1 00:00:11 kernel: hub 2-0:1.0: 2 ports detected
Jan 1 00:00:11 kernel: usbcore: registered new interface driver usblp
Jan 1 00:00:11 kernel: drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Jan 1 00:00:11 kernel: usbcore: registered new interface driver asix
Jan 1 00:00:11 kernel: usb 1-1: new high speed USB device using ehci_hcd and address 2
Jan 1 00:00:11 kernel: usb 1-1: configuration #1 chosen from 1 choice
Jan 1 00:00:11 kernel: hub 1-1:1.0: USB hub found
Jan 1 00:00:11 kernel: hub 1-1:1.0: 4 ports detected
Jan 1 00:00:11 kernel: usbcore: registered new interface driver cdc_ether
Jan 1 00:00:11 kernel: usbcore: registered new interface driver net1080
Jan 1 00:00:11 kernel: usbcore: registered new interface driver rndis_host
Jan 1 00:00:11 kernel: usbcore: registered new interface driver zaurus
Jan 1 00:00:11 kernel: usb 1-1.4: new high speed USB device using ehci_hcd and address 3
Jan 1 00:00:11 kernel: usb 1-1.4: configuration #1 chosen from 1 choice
Jan 1 00:00:11 kernel: scsi0 : SCSI emulation for USB Mass Storage devices
Jan 1 00:00:12 kernel: br0: starting userspace STP failed, staring kernel STP
Jan 1 00:00:12 kernel: vlan1: dev_set_promiscuity(master, 1)
Jan 1 00:00:12 kernel: device eth0 entered promiscuous mode
Jan 1 00:00:12 kernel: device vlan1 entered promiscuous mode
Jan 1 00:00:13 kernel: scsi 0:0:0:0: Direct-Access Multi Flash Reader 1.00 PQ: 0 ANSI: 0
Jan 1 00:00:13 kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk
Jan 1 00:00:13 kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Jan 1 00:00:14 kernel: COEX: downgraded chanspec 0x2d03 to 0x2b01: ext channel 5 used as ctrl channel by existing BSSs
Jan 1 00:00:14 kernel: device eth1 entered promiscuous mode
Jan 1 00:00:14 kernel: device eth2 entered promiscuous mode
Jan 1 00:00:14 stop_nat_rules: apply the redirect_rules!
Jan 1 00:00:15 kernel: br0: port 3(eth2) entering listening state
Jan 1 00:00:15 kernel: br0: port 2(eth1) entering listening state
Jan 1 00:00:15 kernel: br0: port 1(vlan1) entering listening state
Jan 1 00:00:15 kernel: br0: port 3(eth2) entering learning state
Jan 1 00:00:15 kernel: br0: port 2(eth1) entering learning state
Jan 1 00:00:15 kernel: br0: port 1(vlan1) entering learning state
Jan 1 00:00:15 kernel: br0: topology change detected, propagating
Jan 1 00:00:15 kernel: br0: port 3(eth2) entering forwarding state
Jan 1 00:00:15 kernel: br0: topology change detected, propagating
Jan 1 00:00:15 kernel: br0: port 2(eth1) entering forwarding state
Jan 1 00:00:15 kernel: br0: topology change detected, propagating
Jan 1 00:00:15 kernel: br0: port 1(vlan1) entering forwarding state
Jan 1 00:00:15 WAN Connection: ISP's DHCP did not function properly.
Jan 1 00:00:15 dnsmasq[508]: started, version 2.55 cachesize 1500
Jan 1 00:00:15 dnsmasq[508]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-I18N DHCP TFTP
Jan 1 00:00:15 dnsmasq[508]: asynchronous logging enabled, queue limit is 5 messages
Jan 1 00:00:15 dnsmasq-dhcp[508]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Jan 1 00:00:15 dnsmasq[508]: read /etc/hosts - 3 addresses
Jan 1 00:00:15 RT-N66U: start httpd
Jan 1 00:00:15 syslog: SNet version started
Jan 1 00:00:15 miniupnpd[528]: HTTP listening on port 56898
Jan 1 00:00:15 miniupnpd[528]: Listening for NAT-PMP traffic on port 5351
Jan 1 00:00:18 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Jan 1 00:00:18 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Jan 1 00:00:35 notify_rc : start_autodet
Jan 1 00:00:35 kernel: autodet uses obsolete (PF_INET,SOCK_PACKET)
Jan 1 00:00:38 notify_rc : start_autodet
Jan 1 00:00:55 notify_rc : start_autodet
Jan 1 00:01:19 notify_rc : restart_wireless
Jan 1 00:01:21 kernel: Ebtables v2.0 registered
Jan 1 00:01:21 kernel: device eth1 left promiscuous mode
Jan 1 00:01:21 kernel: br0: port 2(eth1) entering disabled state
Jan 1 00:01:21 kernel: device eth2 left promiscuous mode
Jan 1 00:01:21 kernel: br0: port 3(eth2) entering disabled state
Jan 1 00:01:25 kernel: COEX: downgraded chanspec 0x2e07 to 0x2b09: ext channel 5 used as ctrl channel by existing BSSs
Jan 1 00:01:25 kernel: COEX: downgraded chanspec 0x2d03 to 0x2b01: ext channel 5 used as ctrl channel by existing BSSs
Jan 1 00:01:26 kernel: device eth1 entered promiscuous mode
Jan 1 00:01:26 kernel: br0: port 2(eth1) entering listening state
Jan 1 00:01:26 kernel: br0: port 2(eth1) entering learning state
Jan 1 00:01:26 kernel: br0: topology change detected, propagating
Jan 1 00:01:26 kernel: br0: port 2(eth1) entering forwarding state
Jan 1 00:01:26 kernel: device eth2 entered promiscuous mode
Jan 1 00:01:26 kernel: br0: port 3(eth2) entering listening state
Jan 1 00:01:26 kernel: br0: port 3(eth2) entering learning state
Jan 1 00:01:26 kernel: br0: topology change detected, propagating
Jan 1 00:01:26 kernel: br0: port 3(eth2) entering forwarding state
Jan 1 00:02:29 notify_rc : restart_wan_if 0
Jan 1 00:02:29 dnsmasq[508]: read /etc/hosts - 3 addresses
Jan 1 00:02:29 stop_wan(): perform DHCP release
Jan 1 00:02:29 kernel: br0: port 1(vlan1) entering disabled state
Jan 1 00:02:29 kernel: vlan1: dev_set_promiscuity(master, 1)
Jan 1 00:02:29 kernel: br0: port 1(vlan1) entering listening state
Jan 1 00:02:29 kernel: br0: port 1(vlan1) entering learning state
Jan 1 00:02:29 kernel: br0: topology change detected, propagating
Jan 1 00:02:29 kernel: br0: port 1(vlan1) entering forwarding state
Jan 1 00:02:31 dnsmasq[508]: read /etc/hosts - 3 addresses
Jan 1 00:02:44 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Jan 1 00:02:44 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Jan 1 00:03:54 WAN Connection: Fail to connect with some issues.
Jan 1 00:03:55 notify_rc : restart_wan_if 0
Jan 1 00:03:55 dnsmasq[508]: read /etc/hosts - 3 addresses
Jan 1 00:03:55 stop_wan(): perform DHCP release
Jan 1 00:03:56 kernel: br0: port 1(vlan1) entering disabled state
Jan 1 00:03:56 kernel: br0: port 1(vlan1) entering listening state
Jan 1 00:03:56 kernel: br0: port 1(vlan1) entering learning state
Jan 1 00:03:56 kernel: br0: topology change detected, propagating
Jan 1 00:03:56 kernel: br0: port 1(vlan1) entering forwarding state
Jan 1 00:04:06 pppd[625]: Plugin rp-pppoe.so loaded.
Jan 1 00:04:06 pppd[625]: RP-PPPoE plugin version 3.10 compiled against pppd 2.4.5
Jan 1 00:04:06 pppd[626]: pppd 2.4.5 started by admin, uid 0
Jan 1 00:04:06 pppd[626]: PPP session is 4981 (0x1375)
Jan 1 00:04:06 pppd[626]: Connected to 00:90:1a:41:04:94 via interface eth0
Jan 1 00:04:06 pppd[626]: Using interface ppp0
Jan 1 00:04:06 pppd[626]: Connect: ppp0 <--> eth0
Jan 1 00:04:07 pppd[626]: PAP authentication succeeded
Jan 1 00:04:07 pppd[626]: peer from calling number 00:90:1A:41:04:94 authorized
Jan 1 00:04:07 pppd[626]: local IP address 81.173.235.197
Jan 1 00:04:07 pppd[626]: remote IP address 213.196.239.104
Jan 1 00:04:07 pppd[626]: primary DNS address 81.173.194.69
Jan 1 00:04:07 pppd[626]: secondary DNS address 81.173.194.77
Jan 1 00:04:07 notify_rc : start_nat_rules
Jan 1 00:04:07 start_nat_rules: apply the nat_rules!
Jan 1 00:04:07 dnsmasq[508]: read /etc/hosts - 3 addresses
Jan 1 00:04:07 dnsmasq[508]: using nameserver 81.173.194.77#53
Jan 1 00:04:07 dnsmasq[508]: using nameserver 81.173.194.69#53
Jan 1 00:04:07 kernel: nf_conntrack_rtsp v0.6.21 loading
Jan 1 00:04:07 kernel: nf_nat_rtsp v0.6.21 loading
Jan 1 00:04:07 notify_rc : stop_upnp
Jan 1 00:04:07 miniupnpd[528]: received signal 15, good-bye
Jan 1 00:04:07 notify_rc : start_upnp
Jan 1 00:04:07 syslog: SNet version started
Jan 1 00:04:08 notify_rc : stop_ntpc
Jan 1 00:04:08 notify_rc : start_ntpc
Jan 1 00:04:08 miniupnpd[670]: HTTP listening on port 33674
Jan 1 00:04:08 miniupnpd[670]: Listening for NAT-PMP traffic on port 5351
Oct 16 19:03:59 notify_rc : restart_upnp
Oct 16 19:03:59 miniupnpd[670]: received signal 15, good-bye
Oct 16 19:03:59 syslog: SNet version started
Oct 16 19:03:59 miniupnpd[676]: HTTP listening on port 55586
Oct 16 19:03:59 miniupnpd[676]: Listening for NAT-PMP traffic on port 5351
Oct 16 19:04:00 WAN Connection: WAN was restored.
Oct 16 19:04:00 notify_rc : start_nat_rules
Oct 16 19:04:01 pppd[626]: System time change detected.
Oct 16 19:04:51 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:04:51 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 19:06:41 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:06:41 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 19:08:37 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:08:37 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 19:11:26 notify_rc : start_autodet
Oct 16 19:11:29 notify_rc : start_autodet
Oct 16 19:11:39 notify_rc : restart_wan_if 0
Oct 16 19:11:39 dnsmasq[508]: read /etc/hosts - 3 addresses
Oct 16 19:11:39 dnsmasq[508]: using nameserver 81.173.194.77#53
Oct 16 19:11:39 dnsmasq[508]: using nameserver 81.173.194.69#53
Oct 16 19:11:39 pppd[626]: Hangup (SIGHUP)
Oct 16 19:11:39 pppd[626]: Connect time 7.7 minutes.
Oct 16 19:11:39 pppd[626]: Sent 136662 bytes, received 1548750 bytes.
Oct 16 19:11:39 dnsmasq[508]: read /etc/hosts - 3 addresses
Oct 16 19:11:39 dnsmasq[508]: using nameserver 81.173.194.77#53
Oct 16 19:11:39 dnsmasq[508]: using nameserver 81.173.194.69#53
Oct 16 19:11:39 pppd[626]: Connection terminated.
Oct 16 19:11:39 pppd[626]: Sent PADT
Oct 16 19:11:40 WAN Connection: Fail to connect with some issues.
Oct 16 19:11:40 notify_rc : stop_nat_rules
Oct 16 19:11:40 rc_service: stop_nat_rules is waitting restart_wan_if 0...
Oct 16 19:11:40 pppd[626]: Terminating on signal 15
Oct 16 19:11:40 pppd[626]: Exit.
Oct 16 19:11:41 stop_wan(): perform DHCP release
Oct 16 19:11:41 kernel: br0: port 1(vlan1) entering disabled state
Oct 16 19:11:41 kernel: br0: port 1(vlan1) entering listening state
Oct 16 19:11:41 kernel: br0: port 1(vlan1) entering learning state
Oct 16 19:11:41 kernel: br0: topology change detected, propagating
Oct 16 19:11:41 kernel: br0: port 1(vlan1) entering forwarding state
Oct 16 19:11:52 pppd[708]: Plugin rp-pppoe.so loaded.
Oct 16 19:11:52 pppd[708]: RP-PPPoE plugin version 3.10 compiled against pppd 2.4.5
Oct 16 19:11:52 pppd[709]: pppd 2.4.5 started by admin, uid 0
Oct 16 19:11:53 pppd[709]: PPP session is 5031 (0x13a7)
Oct 16 19:11:53 pppd[709]: Connected to 00:90:1a:41:04:94 via interface eth0
Oct 16 19:11:53 pppd[709]: Using interface ppp0
Oct 16 19:11:53 pppd[709]: Connect: ppp0 <--> eth0
Oct 16 19:11:53 pppd[709]: PAP authentication succeeded
Oct 16 19:11:53 pppd[709]: peer from calling number 00:90:1A:41:04:94 authorized
Oct 16 19:11:53 pppd[709]: local IP address 81.173.249.150
Oct 16 19:11:53 pppd[709]: remote IP address 213.196.239.104
Oct 16 19:11:53 pppd[709]: primary DNS address 81.173.194.69
Oct 16 19:11:53 pppd[709]: secondary DNS address 81.173.194.77
Oct 16 19:11:53 stop_nat_rules: apply the redirect_rules!
Oct 16 19:11:53 dnsmasq[508]: read /etc/hosts - 3 addresses
Oct 16 19:11:53 dnsmasq[508]: using nameserver 81.173.194.77#53
Oct 16 19:11:53 dnsmasq[508]: using nameserver 81.173.194.69#53
Oct 16 19:11:53 notify_rc : start_nat_rules
Oct 16 19:11:53 start_nat_rules: apply the nat_rules!
Oct 16 19:11:53 notify_rc : stop_upnp
Oct 16 19:11:53 miniupnpd[676]: received signal 15, good-bye
Oct 16 19:11:53 notify_rc : start_upnp
Oct 16 19:11:53 syslog: SNet version started
Oct 16 19:11:53 miniupnpd[738]: HTTP listening on port 39866
Oct 16 19:11:53 miniupnpd[738]: Listening for NAT-PMP traffic on port 5351
Oct 16 19:11:58 WAN Connection: WAN was restored.
Oct 16 19:11:58 notify_rc : start_nat_rules
Oct 16 19:12:00 notify_rc : restart_wireless
Oct 16 19:12:02 kernel: device eth1 left promiscuous mode
Oct 16 19:12:02 kernel: br0: port 2(eth1) entering disabled state
Oct 16 19:12:02 kernel: device eth2 left promiscuous mode
Oct 16 19:12:02 kernel: br0: port 3(eth2) entering disabled state
Oct 16 19:12:03 notify_rc : restart_upnp
Oct 16 19:12:03 rc_service: restart_upnp is waitting restart_wireless...
Oct 16 19:12:04 kernel: COEX: downgraded chanspec 0x2e07 to 0x2b09: ext channel 5 used as ctrl channel by existing BSSs
Oct 16 19:12:04 kernel: device eth1 entered promiscuous mode
Oct 16 19:12:04 kernel: br0: port 2(eth1) entering listening state
Oct 16 19:12:04 kernel: br0: port 2(eth1) entering learning state
Oct 16 19:12:04 kernel: br0: topology change detected, propagating
Oct 16 19:12:04 kernel: br0: port 2(eth1) entering forwarding state
Oct 16 19:12:04 kernel: device eth2 entered promiscuous mode
Oct 16 19:12:04 kernel: br0: port 3(eth2) entering listening state
Oct 16 19:12:05 kernel: br0: port 3(eth2) entering learning state
Oct 16 19:12:05 kernel: br0: topology change detected, propagating
Oct 16 19:12:05 kernel: br0: port 3(eth2) entering forwarding state
Oct 16 19:12:05 miniupnpd[738]: received signal 15, good-bye
Oct 16 19:12:05 syslog: SNet version started
Oct 16 19:12:05 miniupnpd[780]: HTTP listening on port 50324
Oct 16 19:12:05 miniupnpd[780]: Listening for NAT-PMP traffic on port 5351
Oct 16 19:15:09 kernel: COEX: downgraded chanspec 0x2d03 to 0x2b01: ext channel 5 used as ctrl channel by existing BSSs
Oct 16 19:16:03 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:16:03 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 19:17:38 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:17:38 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 19:19:54 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:19:54 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 19:21:20 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:21:20 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 19:21:51 dnsmasq-dhcp[508]: DHCPINFORM(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:21:51 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 19:29:52 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:29:52 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 19:30:09 kernel: COEX: downgraded chanspec 0x2e07 to 0x2b09: ext channel 5 used as ctrl channel by existing BSSs
Oct 16 19:35:11 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:35:11 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 19:37:08 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:37:08 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 19:38:02 dnsmasq-dhcp[508]: DHCPRELEASE(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:39:02 dnsmasq-dhcp[508]: DHCPDISCOVER(br0) 00:25:22:8f:48:01
Oct 16 19:39:02 dnsmasq-dhcp[508]: DHCPOFFER(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:39:02 dnsmasq-dhcp[508]: DHCPDISCOVER(br0) 00:25:22:8f:48:01
Oct 16 19:39:02 dnsmasq-dhcp[508]: DHCPOFFER(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:39:14 dnsmasq-dhcp[508]: DHCPDISCOVER(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:39:14 dnsmasq-dhcp[508]: DHCPOFFER(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:39:14 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:39:14 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 19:43:37 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:43:37 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 19:47:03 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:47:03 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 19:54:26 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:54:26 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 19:56:13 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:56:13 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 19:56:48 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 19:56:48 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 20:00:10 kernel: COEX: downgraded chanspec 0x2e07 to 0x2b09: channel 6 used by exiting BSSs
Oct 16 20:00:10 kernel: COEX: downgraded chanspec 0x2d03 to 0x2b01: channel 6 used by exiting BSSs
Oct 16 20:10:24 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 20:10:24 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 20:11:40 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 20:11:40 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 20:12:53 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 20:12:53 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 20:15:10 kernel: COEX: downgraded chanspec 0x2e07 to 0x2b09: ext channel 5 used as ctrl channel by existing BSSs
Oct 16 20:15:10 kernel: COEX: downgraded chanspec 0x2d03 to 0x2b01: ext channel 5 used as ctrl channel by existing BSSs
Oct 16 20:15:35 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 20:15:35 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 20:16:58 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 20:16:58 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 20:17:43 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 20:17:43 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 20:23:24 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 20:23:24 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 20:23:46 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 20:23:46 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 20:24:28 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 20:24:28 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 20:25:56 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 20:25:56 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 20:31:50 dnsmasq-dhcp[508]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 20:31:50 dnsmasq-dhcp[508]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
usw.


Bitte zahlreich Ideen posten. Falls Infos fehlen - bitte fragen (und mir sagen wie ich an die fehlenden Info komme). Wäre schade wenn ich auch dieses Gerät zurück schicken müsste.

ps. Bin berufstätig - werde also nur Abends nachsehen und posten.

Danke!
 
Zuletzt bearbeitet:
Nabend,

schalt doch mal DHCP im Router ab und gib deinem Rechner ne feste IP im 192.168.1. Netz - z.B. die 50. Der Router gibt dem Rechner mindestens alle paar Minuten aufgrund eines DHCP-Request eine neue ( die gleiche ) IP-Adresse.

Die Anfrage geht natürlich zügig, führt aber auf jeden Fall zu erwähnten aussetzern.

MfG Maklas
 
Danke für die Antwort,

das war es glaube ich noch nicht - vielleicht mache ich aber auch was falsch?!
- Habe meinem Rechner die IP 192.168.1.20 zugewiesen / meinem Handy testweise die 192.168.1.6
- Wenn DHCP-Server ausgeschaltet ist (am Router) - kann ich gar keine Verbindung zum Router herstellen - weder vom PC - noch vom Handy. / Internet lt. Router ist "an" (inklusive einer vergebenen IP). - komme aber nicht auf den Router drauf....bzw. über den Router ins Internet.
- Wenn DHCP-Server eingeschaltet ist mit zusätzlich manueller Zuweisung der IPs sieht das Protokoll (auszugsweise) wie folgt aus - dennoch Abbruch und reconnect der Verbindung.

Oct 16 21:44:23 WAN Connection: WAN was restored.
Oct 16 21:44:23 notify_rc : start_nat_rules
Oct 16 21:44:30 notify_rc : restart_upnp
Oct 16 21:44:30 miniupnpd[1916]: received signal 15, good-bye
Oct 16 21:44:30 syslog: SNet version started
Oct 16 21:44:30 miniupnpd[1924]: HTTP listening on port 40191
Oct 16 21:44:30 miniupnpd[1924]: Listening for NAT-PMP traffic on port 5351
Oct 16 21:44:34 dnsmasq-dhcp[1862]: DHCPREQUEST(br0) 192.168.1.6 18:87:96:89:e4:42
Oct 16 21:44:34 dnsmasq-dhcp[1862]: DHCPACK(br0) 192.168.1.6 18:87:96:89:e4:42 android-ab4c6b3fae5702ff
Oct 16 21:45:05 dnsmasq-dhcp[1862]: DHCPDISCOVER(br0) 00:25:22:8f:48:01
Oct 16 21:45:05 dnsmasq-dhcp[1862]: DHCPOFFER(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 21:45:05 dnsmasq-dhcp[1862]: DHCPDISCOVER(br0) 00:25:22:8f:48:01
Oct 16 21:45:05 dnsmasq-dhcp[1862]: DHCPOFFER(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 21:45:27 dnsmasq-dhcp[1862]: DHCPDISCOVER(br0) 00:25:22:8f:48:01
Oct 16 21:45:27 dnsmasq-dhcp[1862]: DHCPOFFER(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 21:45:27 dnsmasq-dhcp[1862]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 21:45:27 dnsmasq-dhcp[1862]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA
Oct 16 21:45:52 kernel: COEX: downgraded chanspec 0x2e07 to 0x2b09: ext channel 5 used as ctrl channel by existing BSSs
Oct 16 21:45:52 kernel: COEX: downgraded chanspec 0x2d03 to 0x2b01: ext channel 5 used as ctrl channel by existing BSSs
Oct 16 21:50:03 nmbd[1882]: [2012/10/16 21:50:03, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(392)
Oct 16 21:50:03 nmbd[1882]: Samba name server RT-N66U is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.1
Oct 16 21:51:46 dnsmasq-dhcp[1862]: DHCPREQUEST(br0) 192.168.1.20 00:25:22:8f:48:01
Oct 16 21:51:46 dnsmasq-dhcp[1862]: DHCPACK(br0) 192.168.1.20 00:25:22:8f:48:01 R-Type-RevA

Kann ich noch was an Windows ändern?
Oder: Muss ich dann noch (manuell) eine DHCP- und WINS-IP eingeben? (Der Router bietet auf der DHCP-Server-Seite diese Option an) Ferner könnte ich noch mit statischen Routen arbeiten.

Ansonsten bitte einfach weiter Ideen posten.

Grüße
amethist
 
mit manuell war gemeint, dass du testweise beim pc direkt feste netzwerkeinträge in den netzwerkeinstellungen vergibst.
also z.b.
ipadresse 192.168.1.6
subnertzmaske 255.255.255.0
gateway 192.168.1.1
bevorzugter dns-server 8.8.8.8 (z.b. den von google oder 192.168.1.1)

desweiteren solltest du die eingerichtete breitbandverbindung (b.z.w. einwahlsoftware vom provider?) beim pc löschen, da die ja durch den router ersetzt wird.
 
Habe ich nun auch probiert.
Also in der Lan-Verbindung unter Win7 die IPV4 Daten entsprechend eingetragen. Dann kann ich auch den DHCP-Server im Router abschalten und ich komme ins Internet! Insofern ja nicht schlecht - aber die fortlaufenden Abbrüche bleiben bestehen !

Ich schicke deswegen nochmal das neueste Protokoll mit:
Die ersten beiden Einträge erhielt ich beim ersten unterbrechen der Verbindung. (Dort mit DHCP im Router noch an) Der letzte Abbruch unten mit DHCP auf dem Router aus. Jetzt hat es also etwas mit nmbd zu tun?

Kann ich noch mehr überprüfen? Müssen z.B. in Windows spezielle Dienste an oder aus sein? Alternativ werde ich mal eine andere Netzwerkkarte prüfen.

Oct 17 06:49:01 nmbd[748]: [2012/10/17 06:49:01, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(392)
Oct 17 06:49:01 nmbd[748]: Samba name server RT-N66U is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.1
Oct 17 20:50:21 notify_rc : restart_net_and_phy
Oct 17 20:50:23 FTP Server: daemon is stoped
Oct 17 20:50:23 Samba Server: smb daemon is stoped
Oct 17 18:50:25 dnsmasq[510]: exiting on receipt of SIGTERM
Oct 17 18:50:25 pppd[498]: Connect time 50.9 minutes.
Oct 17 18:50:25 pppd[498]: Sent 2334327 bytes, received 13009354 bytes.
Oct 17 18:50:25 pppd[498]: Terminating on signal 15
Oct 17 18:50:25 pppd[498]: Connection terminated.
Oct 17 18:50:25 pppd[498]: Sent PADT
Oct 17 18:50:25 pppd[498]: Exit.
Oct 17 20:50:25 stop_wan(): perform DHCP release
Oct 17 20:50:25 kernel: br0: port 1(vlan1) entering disabled state
Oct 17 20:50:25 kernel: vlan1: dev_set_promiscuity(master, 1)
Oct 17 20:50:26 kernel: br0: port 1(vlan1) entering listening state
Oct 17 20:50:26 kernel: br0: port 1(vlan1) entering learning state
Oct 17 20:50:26 kernel: br0: topology change detected, propagating
Oct 17 20:50:26 kernel: br0: port 1(vlan1) entering forwarding state
Oct 17 20:50:27 stop_wan(): perform DHCP release
Oct 17 18:50:28 WAN Connection: Fail to connect with some issues.
Oct 17 18:50:28 notify_rc : stop_nat_rules
Oct 17 18:50:28 rc_service: stop_nat_rules is waitting restart_net_and_phy...
Oct 17 20:50:30 kernel: br0: port 3(eth2) entering disabled state
Oct 17 20:50:30 kernel: br0: port 2(eth1) entering disabled state
Oct 17 20:50:30 kernel: br0: port 1(vlan1) entering disabled state
Oct 17 20:50:30 kernel: Ebtables v2.0 registered
Oct 17 20:50:30 kernel: br0: port 1(vlan1) entering disabled state
Oct 17 20:50:30 kernel: vlan1: dev_set_promiscuity(master, -1)
Oct 17 20:50:30 kernel: device vlan1 left promiscuous mode
Oct 17 20:50:30 kernel: device eth1 left promiscuous mode
Oct 17 20:50:30 kernel: br0: port 2(eth1) entering disabled state
Oct 17 20:50:30 kernel: device eth2 left promiscuous mode
Oct 17 20:50:30 kernel: br0: port 3(eth2) entering disabled state
Oct 17 18:50:31 wanduck exit: apply the nat_rules!
Oct 17 20:50:36 kernel: br0: starting userspace STP failed, staring kernel STP
Oct 17 20:50:36 kernel: vlan1: dev_set_promiscuity(master, -1)
Oct 17 20:50:36 kernel: device eth0 left promiscuous mode
Oct 17 20:50:36 kernel: vlan1: dev_set_promiscuity(master, 1)
Oct 17 20:50:36 kernel: device eth0 entered promiscuous mode
Oct 17 20:50:36 kernel: device vlan1 entered promiscuous mode
Oct 17 20:50:37 kernel: COEX: downgraded chanspec 0x2d03 to 0x2b01: ext channel 5 used as ctrl channel by existing BSSs
Oct 17 20:50:37 kernel: device eth1 entered promiscuous mode
Oct 17 20:50:38 kernel: device eth2 entered promiscuous mode
Oct 17 20:50:38 kernel: br0: port 3(eth2) entering listening state
Oct 17 20:50:38 kernel: br0: port 2(eth1) entering listening state
Oct 17 20:50:38 kernel: br0: port 1(vlan1) entering listening state
Oct 17 20:50:38 kernel: br0: port 3(eth2) entering learning state
Oct 17 20:50:38 kernel: br0: port 2(eth1) entering learning state
Oct 17 20:50:38 kernel: br0: port 1(vlan1) entering learning state
Oct 17 20:50:38 kernel: br0: topology change detected, propagating
Oct 17 20:50:38 kernel: br0: port 3(eth2) entering forwarding state
Oct 17 20:50:38 stop_nat_rules: apply the redirect_rules!
Oct 17 20:50:38 kernel: br0: topology change detected, propagating
Oct 17 20:50:38 kernel: br0: port 2(eth1) entering forwarding state
Oct 17 20:50:38 kernel: br0: topology change detected, propagating
Oct 17 20:50:38 kernel: br0: port 1(vlan1) entering forwarding state
Oct 17 20:50:38 WAN Connection: Fail to connect with some issues.
Oct 17 20:50:47 pppd[885]: Plugin rp-pppoe.so loaded.
Oct 17 20:50:47 pppd[885]: RP-PPPoE plugin version 3.10 compiled against pppd 2.4.5
Oct 17 20:50:47 pppd[886]: pppd 2.4.5 started by admin2#, uid 0
Oct 17 20:50:47 dnsmasq[898]: started, version 2.55 cachesize 1500
Oct 17 20:50:47 dnsmasq[898]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-I18N DHCP TFTP
Oct 17 20:50:47 dnsmasq[898]: asynchronous logging enabled, queue limit is 5 messages
Oct 17 20:50:47 dnsmasq[898]: read /etc/hosts - 3 addresses
Oct 17 20:50:47 dnsmasq[898]: using nameserver 81.173.194.77#53
Oct 17 20:50:47 dnsmasq[898]: using nameserver 81.173.194.69#53
Oct 17 20:50:47 RT-N66U: start httpd
Oct 17 20:50:47 kernel: gro enabled with interval 2
Oct 17 20:50:48 pppd[886]: PPP session is 6509 (0x196d)
Oct 17 20:50:48 pppd[886]: Connected to 00:90:1a:41:04:94 via interface eth0
Oct 17 20:50:48 pppd[886]: Using interface ppp0
Oct 17 20:50:48 pppd[886]: Connect: ppp0 <--> eth0
Oct 17 20:50:48 Samba Server: daemon is started
Oct 17 20:50:48 pppd[886]: PAP authentication succeeded
Oct 17 20:50:48 pppd[886]: peer from calling number 00:90:1A:41:04:94 authorized
Oct 17 20:50:48 pppd[886]: local IP address 81.173.254.162
Oct 17 20:50:48 pppd[886]: remote IP address 213.196.239.104
Oct 17 20:50:48 pppd[886]: primary DNS address 81.173.194.69
Oct 17 20:50:48 pppd[886]: secondary DNS address 81.173.194.77
Oct 17 20:50:48 notify_rc : start_nat_rules
Oct 17 20:50:48 rc_service: start_nat_rules is waitting restart_net_and_phy...
Oct 17 20:50:48 dnsmasq[898]: read /etc/hosts - 3 addresses
Oct 17 20:50:48 dnsmasq[898]: using nameserver 81.173.194.77#53
Oct 17 20:50:48 dnsmasq[898]: using nameserver 81.173.194.69#53
Oct 17 20:50:49 start_nat_rules: apply the nat_rules!
Oct 17 20:50:49 notify_rc : stop_upnp
Oct 17 20:50:49 notify_rc : start_upnp
Oct 17 20:50:49 rc_service: start_upnp is waitting stop_upnp...
Oct 17 20:50:49 miniupnpd[769]: received signal 15, good-bye
Oct 17 20:50:49 miniupnpd[769]: SendSSDPGoodbye: sendto(udp_shutdown=14): No such device
Oct 17 20:50:49 miniupnpd[769]: Failed to broadcast good-bye notifications
Oct 17 20:50:50 syslog: SNet version started
Oct 17 20:50:50 miniupnpd[960]: HTTP listening on port 55695
Oct 17 20:50:50 miniupnpd[960]: Listening for NAT-PMP traffic on port 5351
Oct 17 20:50:53 WAN Connection: WAN was restored.
Oct 17 20:50:53 notify_rc : start_nat_rules
Oct 17 20:56:33 nmbd[919]: [2012/10/17 20:56:33, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(392)
Oct 17 20:56:33 nmbd[919]: Samba name server RT-N66U is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.1
Ergänzung ()

So,

habe jetzt mal alternativ die Verbindung sowohl über WLan mit einem Asus-USB Stick hergestellt als auch über Kabel mit einer anderen Netzwerkkarte.

Jetzt funktioniert alles ohne Probleme. Scheint also ein Fehler irgendwie in Verbindung mit dem Onboard Lan-Chip zu sein (Realtek RTL8111e). Habe heute extra noch ein Treiberupdate gemacht. Ich kann mich erinnern, dass ich bei einem anderen Board ebenfalls Probleme mit einem Realtek Chip hatte. Scheinen ja nicht so gut zu sein... haben andere den keine Probleme mit diesen Dingern?

Es wäre natürlich trotzdem interessant zu wissen, woran genau es nun gelegen hat - aber es gibt dann wohl zu viele Fehlerquellen. Wer hierzu noch Tipps hat - gerne schicken.

Grüße
 
Realtek ist einer der großen Anbieter, habe ich auch glaube ich, keine Probleme damit. Evtl. hast Du im Bios eingestellt, das der PC den Stromsparmodus für die LAN Ports aktivieren darf wenn er möchte. Das "könnte" ein Problem sein, mal aus machen.
 
Du musst dich einloggen oder registrieren, um hier zu antworten.
Zurück
Oben

Willkommen auf ComputerBase!

Mit Werbung weiterlesen

Besuche ComputerBase wie gewohnt mit Werbung und Tracking. Die Zustimmung ist jederzeit widerrufbar.

Details im Privacy Center und in der Liste unserer Partner. Ein Widerruf ist möglich in der Datenschutzerklärung.

… oder ComputerBase Pro bestellen

Nutze ComputerBase ohne Werbebanner, Video-Ads und Werbetracking schon für 4 €/Monat oder 36 €/Jahr.

Mehr zu ComputerBase Pro

Bereits Pro-Nutzer? Hier anmelden.

Tracking: Wir und unsere 160 Partner verarbeiten personenbezogene Daten, indem wir mit auf Ihrem Gerät gespeicherten Informationen (z. B. eindeutige Kennungen in Cookies) ein Nutzungsprofil erstellen, um z. B. Anzeigen zu personalisieren. Verarbeitungszwecke: Genaue Standortdaten und Abfrage von Geräteeigenschaften zur Identifikation, Informationen auf einem Gerät speichern und/oder abrufen, Personalisierte Anzeigen und Inhalte, Anzeigen- und Inhaltsmessungen, Erkenntnisse über Zielgruppen und Produktentwicklungen.

Impressum Kontakt Datenschutz