Modify

Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#1212 closed request (support)

Bridge mode causes disconnect status

Reported by: powerpee@… Owned by:
Priority: normal Milestone:
Component: fon-base-firmware Version: 2.3.7.0 beta3
Severity: unknown
Cc: Hardware: 2.0n (FON2300)

Description

Hi,

I have a Fon 2.0N in bridge mode. The Fon is behind a routing modem (UBEE NATbox). Although bridging works I cannot get the Picase, Torrent and other apps to work because the FON states it is not connected: error 'The La Fonera needs to be connected for this application to work.' In menu applications I get: 'You are currently offline and cannot install new applications'.

  • All internet connections via the Fon are working fine.

Switchting to DHCP mode solves this problem but is undesireable in my network setup (two DHCP servers, utp lines, etc etc).

setup: UBEE: DHCP server, 192.168.178.1, 255.255.255.0 FON: Bridge, 192.168.178.2, 255.255.255.0

I can't figure out why the Fon won't reach "ONLINE" status...and have been struggling for a long, looong while. Can you help me plz out?

PS: I've tried opening some TCP / UDP ports and have added the FON MAC address to my modem/gateway/firewall statically. This doesn't solve the problem, even after the FON has been up for two days now.

Looking forward to your reply.

Pee

Attachments (0)

Change History (8)

comment:1 Changed 7 years ago by matthijs

  • Status changed from new to infoneeded

Did you configure the DNS server and gateway correctly on your Fonera? The Fonera uses those to connect to the internet, but clients get their info directly through DHCP from your modem (which can explain why all clients have internet, but your Fonera does not).

If this does not help, could you connect to your Fonera using SSH and provide the output of the "logread" command here? See reportbugs for instructions on how to do this.

comment:2 Changed 7 years ago by anonymous

Fonera is configured: Gateway & DNS: 192.168.178.1 (UBEE)

root@Fonera:~# logread Jul 29 23:08:22 Fonera daemon.info avahi-daemon[1658]: Withdrawing address record for 192.168.178.2 on br-lan. Jul 29 23:08:22 Fonera daemon.info avahi-daemon[1658]: Leaving mDNS multicast group on interface br-lan.IPv4 with address 192.168.178.2. Jul 29 23:08:22 Fonera daemon.info avahi-daemon[1658]: Joining mDNS multicast group on interface br-lan.IPv4 with address 169.254.255.1. Jul 29 23:08:22 Fonera daemon.info avahi-daemon[1658]: Registering new address record for 169.254.255.1 on br-lan.IPv4. Jul 29 23:08:22 Fonera user.warn kernel: MASQUERADE: br-lan ate my IP address Jul 29 23:08:22 Fonera user.warn kernel: MASQUERADE: br-lan ate my IP address Jul 29 23:08:23 Fonera user.info kernel: br-lan: port 2(ra0) entering disabled state Jul 29 23:08:23 Fonera user.info kernel: br-lan: port 1(eth0.1) entering disabled state Jul 29 23:08:23 Fonera daemon.info avahi-daemon[1658]: Interface br-lan.IPv4 no longer relevant for mDNS. Jul 29 23:08:23 Fonera daemon.info avahi-daemon[1658]: Leaving mDNS multicast group on interface br-lan.IPv4 with address 169.254.255.1. Jul 29 23:08:23 Fonera daemon.info avahi-daemon[1658]: Withdrawing address record for 169.254.255.1 on br-lan. Jul 29 23:08:23 Fonera user.debug kernel: eth0.1: del 01:00:5e:00:00:01 mcast address from vlan interface Jul 29 23:08:23 Fonera user.debug kernel: eth0.1: del 01:00:5e:00:00:01 mcast address from master interface Jul 29 23:08:23 Fonera user.info kernel: device ra0 left promiscuous mode Jul 29 23:08:23 Fonera user.info kernel: br-lan: port 2(ra0) entering disabled state Jul 29 23:08:23 Fonera user.info kernel: device eth0.1 left promiscuous mode Jul 29 23:08:23 Fonera user.info kernel: br-lan: port 1(eth0.1) entering disabled state Jul 29 23:08:23 Fonera user.notice root: removing br-lan from firewall zone lan Jul 29 23:08:24 Fonera user.notice root: adding eth0.2 to firewall zone wan Jul 29 23:08:24 Fonera user.info kernel: eth0.1: dev_set_promiscuity(master, -1) Jul 29 23:08:24 Fonera user.info kernel: device eth0 left promiscuous mode Jul 29 23:08:24 Fonera user.debug kernel: eth0.1: add 01:00:5e:00:00:01 mcast address to master interface Jul 29 23:08:24 Fonera user.info : uci: Entry not found Jul 29 23:08:24 Fonera user.debug kernel: eth0.1: del 01:00:5e:00:00:01 mcast address from vlan interface Jul 29 23:08:24 Fonera user.debug kernel: eth0.1: del 01:00:5e:00:00:01 mcast address from master interface Jul 29 23:08:24 Fonera user.debug kernel: eth0.1: add 01:00:5e:00:00:01 mcast address to master interface Jul 29 23:08:25 Fonera user.info kernel: eth0.1: dev_set_promiscuity(master, 1) Jul 29 23:08:25 Fonera user.info kernel: device eth0 entered promiscuous mode Jul 29 23:08:25 Fonera user.info kernel: device eth0.1 entered promiscuous mode Jul 29 23:08:25 Fonera user.info kernel: br-lan: port 1(eth0.1) entering learning state Jul 29 23:08:25 Fonera user.info kernel: br-lan: topology change detected, propagating Jul 29 23:08:25 Fonera user.info kernel: br-lan: port 1(eth0.1) entering forwarding state Jul 29 23:08:25 Fonera user.notice root: runnow --> /etc/fonstated/ConfigWifi Jul 29 23:08:25 Fonera user.notice upnp firewall: removing wan interface Jul 29 23:08:26 Fonera user.notice upnp firewall: adding wan interface eth0.2() Jul 29 23:08:26 Fonera user.warn kernel: setting region code 0 Jul 29 23:08:26 Fonera user.warn kernel: setting region code 7 Jul 29 23:08:26 Fonera user.warn kernel: RA_WIFI using 2 SSIDs Jul 29 23:08:26 Fonera user.warn kernel: geo beacon private:0 public:0 Jul 29 23:08:26 Fonera user.warn kernel: MAC: 00:18:84:88:dd:0c Jul 29 23:08:26 Fonera daemon.notice miniupnpd[931]: received signal 15, good-bye Jul 29 23:08:26 Fonera user.notice upnp firewall: removing wan interface Jul 29 23:08:26 Fonera user.notice upnp firewall: adding wan interface eth0.2() Jul 29 23:08:27 Fonera daemon.err miniupnpd[2341]: Unable to open pidfile for writing /var/run/miniupnpd.pid: File exists Jul 29 23:08:27 Fonera daemon.err miniupnpd[2341]: bind(http): Address already in use Jul 29 23:08:27 Fonera daemon.err miniupnpd[2341]: Failed to open socket for HTTP. EXITING Jul 29 23:08:29 Fonera user.warn kernel: 0x1300 = 00064320 Jul 29 23:08:29 Fonera daemon.err miniupnpd[931]: sendto(udp_shutdown=7): Invalid argument Jul 29 23:08:29 Fonera daemon.err miniupnpd[931]: Failed to broadcast good-bye notifications Jul 29 23:08:29 Fonera user.info kernel: br-lan: port 1(eth0.1) entering disabled state Jul 29 23:08:29 Fonera user.info kernel: br-lan: port 1(eth0.1) entering learning state Jul 29 23:08:29 Fonera user.info kernel: br-lan: topology change detected, propagating Jul 29 23:08:29 Fonera user.info kernel: br-lan: port 1(eth0.1) entering forwarding state Jul 29 23:08:29 Fonera daemon.info avahi-daemon[1658]: Joining mDNS multicast group on interface br-lan.IPv4 with address 192.168.178.2. Jul 29 23:08:29 Fonera daemon.info avahi-daemon[1658]: New relevant interface br-lan.IPv4 for mDNS. Jul 29 23:08:29 Fonera daemon.info avahi-daemon[1658]: Registering new address record for 192.168.178.2 on br-lan.IPv4. Jul 29 23:08:30 Fonera user.info kernel: device ra0 entered promiscuous mode Jul 29 23:08:30 Fonera user.info kernel: br-lan: port 2(ra0) entering learning state Jul 29 23:08:30 Fonera user.info kernel: br-lan: topology change detected, propagating Jul 29 23:08:30 Fonera user.info kernel: br-lan: port 2(ra0) entering forwarding state Jul 29 23:08:30 Fonera user.notice root: runnow --> /etc/fonstated/RestartChilli Jul 29 23:08:30 Fonera user.notice root: runnow --> /etc/fonstated/RestartDnsmasq Jul 29 23:08:31 Fonera user.notice root: adding br-lan to firewall zone lan Jul 29 23:08:32 Fonera daemon.notice miniupnpd[2523]: HTTP listening on port 5000 Jul 29 23:08:34 Fonera daemon.info dnsmasq[2731]: started, version 2.45 cachesize 150 Jul 29 23:08:34 Fonera daemon.info dnsmasq[2731]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N TFTP Jul 29 23:08:34 Fonera user.info syslog: whitelist file: /etc/fon/whitelist.dnsmasq Jul 29 23:08:34 Fonera daemon.info dnsmasq[2731]: using local addresses only for domain lan Jul 29 23:08:34 Fonera daemon.info dnsmasq[2731]: reading /tmp/dhcp.leases Jul 29 23:08:34 Fonera daemon.info dnsmasq[2731]: reading /tmp/resolv.conf.auto Jul 29 23:08:34 Fonera daemon.info dnsmasq[2731]: using nameserver 192.168.178.1#53 Jul 29 23:08:34 Fonera daemon.info dnsmasq[2731]: using local addresses only for domain lan Jul 29 23:08:34 Fonera daemon.info dnsmasq[2731]: read /etc/hosts - 2 addresses Jul 29 23:08:34 Fonera user.notice root: runnow --> /etc/fonstated/ReconfOpenVPN Jul 29 23:08:34 Fonera user.crit fonstated: finished running /etc/fonstated/UMTS Jul 29 23:08:34 Fonera user.crit fonstated: running event /etc/fonstated/SetupHosts Jul 29 23:08:34 Fonera user.crit fonstated: finished running /etc/fonstated/SetupHosts Jul 29 23:08:34 Fonera user.crit fonstated: running event /etc/fonstated/BootServices Jul 29 23:08:34 Fonera user.notice root: runnow --> /etc/fonstated/Redirect Jul 29 23:08:34 Fonera user.notice root: runnow --> /etc/fonstated/StartFonsmcd Jul 29 23:08:35 Fonera user.notice root: runnow --> /etc/fonstated/RestartMountd Jul 29 23:08:35 Fonera user.notice root: runnow --> /etc/fonstated/StartHttpd Jul 29 23:08:35 Fonera user.crit mountd[2834]: Starting OpenWrt? (auto)mountd V1 Jul 29 23:08:35 Fonera user.crit mountd[2834]: trying to mount /tmp/run/mountd/ as the autofs root Jul 29 23:08:36 Fonera user.crit fonstated: finished running /etc/fonstated/BootServices Jul 29 23:08:36 Fonera user.crit fonstated: running event /etc/fonstated/FWallDaemon Jul 29 23:08:36 Fonera daemon.info avahi-daemon[1658]: Got SIGHUP, reloading. Jul 29 23:08:36 Fonera daemon.info avahi-daemon[1658]: Loading service file /tmp/mdnsftp.service. Jul 29 23:08:36 Fonera user.notice root: runnow --> /etc/fonstated/FWallDaemon Jul 29 23:08:36 Fonera user.crit mountd[2834]: new mount : Disc-A2 -> sda2 (EXT3) Jul 29 23:08:36 Fonera user.crit mountd[2834]: mounting /tmp/run/mountd/sda2 Jul 29 23:08:36 Fonera user.crit mountd[2923]: mount -t ext3 -o rw,noatime,defaults /dev/sda2 /tmp/run/mountd/sda2 Jul 29 23:08:36 Fonera user.crit fonstated: finished running /etc/fonstated/FWallDaemon Jul 29 23:08:36 Fonera user.crit fonstated: running event /etc/fonstated/StartTorrent Jul 29 23:08:36 Fonera user.crit fonstated: finished running /etc/fonstated/StartTorrent Jul 29 23:08:37 Fonera user.notice root: runnow --> /etc/fonstated/SetupDlmd Jul 29 23:08:37 Fonera user.crit fonstated: enqueue --> StartFonsmcd? Jul 29 23:08:37 Fonera user.crit fonstated: running event /etc/fonstated/StartFonsmcd Jul 29 23:08:37 Fonera authpriv.info dropbear[2942]: Not backgrounding Jul 29 23:08:37 Fonera daemon.info avahi-daemon[1658]: Service "Fonera2.0 FTP Server" (/tmp/mdnsftp.service) successfully established. Jul 29 23:08:37 Fonera user.crit fonstated: finished running /etc/fonstated/StartFonsmcd Jul 29 23:08:37 Fonera user.emerg syslog: starting onlined Jul 29 23:08:37 Fonera user.notice root: runnow --> /etc/fonstated/FWallDaemon Jul 29 23:08:37 Fonera user.info kernel: kjournald starting. Commit interval 5 seconds Jul 29 23:08:37 Fonera user.info kernel: EXT3 FS on sda2, internal journal Jul 29 23:08:37 Fonera user.info kernel: EXT3-fs: recovery complete. Jul 29 23:08:37 Fonera user.info kernel: EXT3-fs: mounted filesystem with ordered data mode. Jul 29 23:08:37 Fonera user.crit mountd[2834]: ----------> mount ret = 0 Jul 29 23:08:37 Fonera daemon.info avahi-daemon[1658]: Got SIGHUP, reloading. Jul 29 23:08:37 Fonera daemon.info avahi-daemon[1658]: Loading service file /tmp/mdnsssh.service. Jul 29 23:08:37 Fonera user.notice root: runnow --> /etc/fonstated/FWallDaemon Jul 29 23:08:38 Fonera daemon.info avahi-daemon[1658]: Got SIGHUP, reloading. Jul 29 23:08:38 Fonera daemon.info avahi-daemon[1658]: Loading service file /tmp/mdnssmb.service. Jul 29 23:08:38 Fonera user.notice root: runnow --> /etc/fonstated/FWallDaemon Jul 29 23:08:38 Fonera daemon.info dnsmasq[2990]: started, version 2.45 cachesize 150 Jul 29 23:08:38 Fonera daemon.info dnsmasq[2990]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N TFTP Jul 29 23:08:38 Fonera user.info syslog: whitelist file: /etc/fon/whitelist.dnsmasq Jul 29 23:08:38 Fonera daemon.info avahi-daemon[1658]: Service "Fonera2.0 SSH" (/tmp/mdnsssh.service) successfully established. Jul 29 23:08:39 Fonera daemon.info avahi-daemon[1658]: Service "LaFonera?" (/tmp/mdnssmb.service) successfully established. Jul 29 23:08:39 Fonera daemon.info dnsmasq[2990]: using local addresses only for domain lan Jul 29 23:08:39 Fonera daemon.info dnsmasq[2990]: reading /tmp/dhcp.leases Jul 29 23:08:39 Fonera daemon.info dnsmasq[2990]: reading /tmp/resolv.conf.auto Jul 29 23:08:39 Fonera daemon.info dnsmasq[2990]: using nameserver 192.168.178.1#53 Jul 29 23:08:39 Fonera daemon.info dnsmasq[2990]: using local addresses only for domain lan Jul 29 23:08:39 Fonera daemon.info dnsmasq[2990]: read /etc/hosts - 2 addresses Jul 29 23:08:39 Fonera user.crit mountd[2834]: Got a autofs packet Jul 29 23:08:39 Fonera user.crit mountd[2834]: kernel is requesting a mount -> sda2 Jul 29 23:08:42 Fonera user.notice root: adding tun-ovpn to firewall zone vpn Jul 29 23:08:43 Fonera user.crit fonstated: enqueue --> SetupDlmd? Jul 29 23:08:43 Fonera user.crit fonstated: running event /etc/fonstated/SetupDlmd Jul 29 23:08:43 Fonera user.crit fonstated: finished running /etc/fonstated/SetupDlmd Jul 29 23:08:44 Fonera user.notice root: adding br-lan to firewall zone lan Jul 29 23:08:44 Fonera user.notice root: adding eth0.2 to firewall zone wan Jul 29 23:09:07 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:09:38 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:09:40 Fonera user.crit mountd[2834]: /tmp/run/mountd/sda2 has expired... unmounting Jul 29 23:09:40 Fonera user.crit mountd[2834]: finished unmounting Jul 29 23:10:09 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:10:40 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:11:11 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:11:42 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:12:13 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:12:44 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:13:15 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:13:45 Fonera user.warn kernel: RT305x_ESW: Link Status Changed Jul 29 23:13:46 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:13:55 Fonera user.warn kernel: RT305x_ESW: Link Status Changed Jul 29 23:13:56 Fonera user.warn kernel: RT305x_ESW: Link Status Changed Jul 29 23:14:17 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:14:30 Fonera user.warn kernel: RT305x_ESW: Link Status Changed Jul 29 23:14:48 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:15:19 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:15:50 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:16:21 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:16:52 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:17:23 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:17:54 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:18:25 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:18:56 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:19:06 Fonera authpriv.info dropbear[4152]: Child connection from 192.168.178.3:51010 Jul 29 23:19:07 Fonera authpriv.info dropbear[4152]: exit before auth: Exited normally Jul 29 23:19:27 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:19:58 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:20:29 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:20:43 Fonera authpriv.info dropbear[4275]: Child connection from 192.168.178.3:51021 Jul 29 23:20:44 Fonera authpriv.info dropbear[4275]: exit before auth: Exited normally Jul 29 23:21:00 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:21:31 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:21:57 Fonera authpriv.info dropbear[4373]: Child connection from 192.168.178.3:51031 Jul 29 23:21:58 Fonera authpriv.info dropbear[4373]: exit before auth: Exited normally Jul 29 23:22:02 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:22:33 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:23:04 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:23:35 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:24:06 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:24:37 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success Jul 29 23:24:47 Fonera authpriv.info dropbear[4589]: Child connection from 192.168.178.3:51051 Jul 29 23:24:58 Fonera authpriv.notice dropbear[4589]: password auth succeeded for 'root' from 192.168.178.3:51051 Jul 29 23:25:08 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success

comment:3 Changed 7 years ago by powerpee@…

better like this?

root@Fonera:~# logread
Jul 29 23:08:22 Fonera daemon.info avahi-daemon[1658]: Withdrawing address record for 192.168.178.2 on br-lan.
Jul 29 23:08:22 Fonera daemon.info avahi-daemon[1658]: Leaving mDNS multicast group on interface br-lan.IPv4 with address 192.168.178.2.
Jul 29 23:08:22 Fonera daemon.info avahi-daemon[1658]: Joining mDNS multicast group on interface br-lan.IPv4 with address 169.254.255.1.
Jul 29 23:08:22 Fonera daemon.info avahi-daemon[1658]: Registering new address record for 169.254.255.1 on br-lan.IPv4.
Jul 29 23:08:22 Fonera user.warn kernel: MASQUERADE: br-lan ate my IP address
Jul 29 23:08:22 Fonera user.warn kernel: MASQUERADE: br-lan ate my IP address
Jul 29 23:08:23 Fonera user.info kernel: br-lan: port 2(ra0) entering disabled state
Jul 29 23:08:23 Fonera user.info kernel: br-lan: port 1(eth0.1) entering disabled state
Jul 29 23:08:23 Fonera daemon.info avahi-daemon[1658]: Interface br-lan.IPv4 no longer relevant for mDNS.
Jul 29 23:08:23 Fonera daemon.info avahi-daemon[1658]: Leaving mDNS multicast group on interface br-lan.IPv4 with address 169.254.255.1.
Jul 29 23:08:23 Fonera daemon.info avahi-daemon[1658]: Withdrawing address record for 169.254.255.1 on br-lan.
Jul 29 23:08:23 Fonera user.debug kernel: eth0.1: del 01:00:5e:00:00:01 mcast address from vlan interface
Jul 29 23:08:23 Fonera user.debug kernel: eth0.1: del 01:00:5e:00:00:01 mcast address from master interface
Jul 29 23:08:23 Fonera user.info kernel: device ra0 left promiscuous mode
Jul 29 23:08:23 Fonera user.info kernel: br-lan: port 2(ra0) entering disabled state
Jul 29 23:08:23 Fonera user.info kernel: device eth0.1 left promiscuous mode
Jul 29 23:08:23 Fonera user.info kernel: br-lan: port 1(eth0.1) entering disabled state
Jul 29 23:08:23 Fonera user.notice root: removing br-lan from firewall zone lan
Jul 29 23:08:24 Fonera user.notice root: adding eth0.2 to firewall zone wan
Jul 29 23:08:24 Fonera user.info kernel: eth0.1: dev_set_promiscuity(master, -1)
Jul 29 23:08:24 Fonera user.info kernel: device eth0 left promiscuous mode
Jul 29 23:08:24 Fonera user.debug kernel: eth0.1: add 01:00:5e:00:00:01 mcast address to master interface
Jul 29 23:08:24 Fonera user.info : uci: Entry not found
Jul 29 23:08:24 Fonera user.debug kernel: eth0.1: del 01:00:5e:00:00:01 mcast address from vlan interface
Jul 29 23:08:24 Fonera user.debug kernel: eth0.1: del 01:00:5e:00:00:01 mcast address from master interface
Jul 29 23:08:24 Fonera user.debug kernel: eth0.1: add 01:00:5e:00:00:01 mcast address to master interface
Jul 29 23:08:25 Fonera user.info kernel: eth0.1: dev_set_promiscuity(master, 1)
Jul 29 23:08:25 Fonera user.info kernel: device eth0 entered promiscuous mode
Jul 29 23:08:25 Fonera user.info kernel: device eth0.1 entered promiscuous mode
Jul 29 23:08:25 Fonera user.info kernel: br-lan: port 1(eth0.1) entering learning state
Jul 29 23:08:25 Fonera user.info kernel: br-lan: topology change detected, propagating
Jul 29 23:08:25 Fonera user.info kernel: br-lan: port 1(eth0.1) entering forwarding state
Jul 29 23:08:25 Fonera user.notice root: runnow --> /etc/fonstated/ConfigWifi
Jul 29 23:08:25 Fonera user.notice upnp firewall: removing wan interface
Jul 29 23:08:26 Fonera user.notice upnp firewall: adding wan interface eth0.2()
Jul 29 23:08:26 Fonera user.warn kernel: setting region code 0
Jul 29 23:08:26 Fonera user.warn kernel: setting region code 7
Jul 29 23:08:26 Fonera user.warn kernel: RA_WIFI using 2 SSIDs
Jul 29 23:08:26 Fonera user.warn kernel: geo beacon private:0 public:0
Jul 29 23:08:26 Fonera user.warn kernel: MAC: 00:18:84:88:dd:0c
Jul 29 23:08:26 Fonera daemon.notice miniupnpd[931]: received signal 15, good-bye
Jul 29 23:08:26 Fonera user.notice upnp firewall: removing wan interface
Jul 29 23:08:26 Fonera user.notice upnp firewall: adding wan interface eth0.2()
Jul 29 23:08:27 Fonera daemon.err miniupnpd[2341]: Unable to open pidfile for writing /var/run/miniupnpd.pid: File exists
Jul 29 23:08:27 Fonera daemon.err miniupnpd[2341]: bind(http): Address already in use
Jul 29 23:08:27 Fonera daemon.err miniupnpd[2341]: Failed to open socket for HTTP. EXITING
Jul 29 23:08:29 Fonera user.warn kernel: 0x1300 = 00064320
Jul 29 23:08:29 Fonera daemon.err miniupnpd[931]: sendto(udp_shutdown=7): Invalid argument
Jul 29 23:08:29 Fonera daemon.err miniupnpd[931]: Failed to broadcast good-bye notifications
Jul 29 23:08:29 Fonera user.info kernel: br-lan: port 1(eth0.1) entering disabled state
Jul 29 23:08:29 Fonera user.info kernel: br-lan: port 1(eth0.1) entering learning state
Jul 29 23:08:29 Fonera user.info kernel: br-lan: topology change detected, propagating
Jul 29 23:08:29 Fonera user.info kernel: br-lan: port 1(eth0.1) entering forwarding state
Jul 29 23:08:29 Fonera daemon.info avahi-daemon[1658]: Joining mDNS multicast group on interface br-lan.IPv4 with address 192.168.178.2.
Jul 29 23:08:29 Fonera daemon.info avahi-daemon[1658]: New relevant interface br-lan.IPv4 for mDNS.
Jul 29 23:08:29 Fonera daemon.info avahi-daemon[1658]: Registering new address record for 192.168.178.2 on br-lan.IPv4.
Jul 29 23:08:30 Fonera user.info kernel: device ra0 entered promiscuous mode
Jul 29 23:08:30 Fonera user.info kernel: br-lan: port 2(ra0) entering learning state
Jul 29 23:08:30 Fonera user.info kernel: br-lan: topology change detected, propagating
Jul 29 23:08:30 Fonera user.info kernel: br-lan: port 2(ra0) entering forwarding state
Jul 29 23:08:30 Fonera user.notice root: runnow --> /etc/fonstated/RestartChilli
Jul 29 23:08:30 Fonera user.notice root: runnow --> /etc/fonstated/RestartDnsmasq
Jul 29 23:08:31 Fonera user.notice root: adding br-lan to firewall zone lan
Jul 29 23:08:32 Fonera daemon.notice miniupnpd[2523]: HTTP listening on port 5000
Jul 29 23:08:34 Fonera daemon.info dnsmasq[2731]: started, version 2.45 cachesize 150
Jul 29 23:08:34 Fonera daemon.info dnsmasq[2731]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N TFTP
Jul 29 23:08:34 Fonera user.info syslog: whitelist file: /etc/fon/whitelist.dnsmasq
Jul 29 23:08:34 Fonera daemon.info dnsmasq[2731]: using local addresses only for domain lan
Jul 29 23:08:34 Fonera daemon.info dnsmasq[2731]: reading /tmp/dhcp.leases
Jul 29 23:08:34 Fonera daemon.info dnsmasq[2731]: reading /tmp/resolv.conf.auto
Jul 29 23:08:34 Fonera daemon.info dnsmasq[2731]: using nameserver 192.168.178.1#53
Jul 29 23:08:34 Fonera daemon.info dnsmasq[2731]: using local addresses only for domain lan
Jul 29 23:08:34 Fonera daemon.info dnsmasq[2731]: read /etc/hosts - 2 addresses
Jul 29 23:08:34 Fonera user.notice root: runnow --> /etc/fonstated/ReconfOpenVPN
Jul 29 23:08:34 Fonera user.crit fonstated: finished running /etc/fonstated/UMTS
Jul 29 23:08:34 Fonera user.crit fonstated: running event /etc/fonstated/SetupHosts
Jul 29 23:08:34 Fonera user.crit fonstated: finished running /etc/fonstated/SetupHosts
Jul 29 23:08:34 Fonera user.crit fonstated: running event /etc/fonstated/BootServices
Jul 29 23:08:34 Fonera user.notice root: runnow --> /etc/fonstated/Redirect
Jul 29 23:08:34 Fonera user.notice root: runnow --> /etc/fonstated/StartFonsmcd
Jul 29 23:08:35 Fonera user.notice root: runnow --> /etc/fonstated/RestartMountd
Jul 29 23:08:35 Fonera user.notice root: runnow --> /etc/fonstated/StartHttpd
Jul 29 23:08:35 Fonera user.crit mountd[2834]: Starting OpenWrt (auto)mountd V1
Jul 29 23:08:35 Fonera user.crit mountd[2834]: trying to mount /tmp/run/mountd/ as the autofs root
Jul 29 23:08:36 Fonera user.crit fonstated: finished running /etc/fonstated/BootServices
Jul 29 23:08:36 Fonera user.crit fonstated: running event /etc/fonstated/FWallDaemon
Jul 29 23:08:36 Fonera daemon.info avahi-daemon[1658]: Got SIGHUP, reloading.
Jul 29 23:08:36 Fonera daemon.info avahi-daemon[1658]: Loading service file /tmp/mdns//ftp.service.
Jul 29 23:08:36 Fonera user.notice root: runnow --> /etc/fonstated/FWallDaemon
Jul 29 23:08:36 Fonera user.crit mountd[2834]: new mount : Disc-A2 -> sda2 (EXT3)
Jul 29 23:08:36 Fonera user.crit mountd[2834]: mounting /tmp/run/mountd/sda2
Jul 29 23:08:36 Fonera user.crit mountd[2923]: mount -t ext3 -o rw,noatime,defaults /dev/sda2 /tmp/run/mountd/sda2
Jul 29 23:08:36 Fonera user.crit fonstated: finished running /etc/fonstated/FWallDaemon
Jul 29 23:08:36 Fonera user.crit fonstated: running event /etc/fonstated/StartTorrent
Jul 29 23:08:36 Fonera user.crit fonstated: finished running /etc/fonstated/StartTorrent
Jul 29 23:08:37 Fonera user.notice root: runnow --> /etc/fonstated/SetupDlmd
Jul 29 23:08:37 Fonera user.crit fonstated: enqueue --> StartFonsmcd
Jul 29 23:08:37 Fonera user.crit fonstated: running event /etc/fonstated/StartFonsmcd
Jul 29 23:08:37 Fonera authpriv.info dropbear[2942]: Not backgrounding
Jul 29 23:08:37 Fonera daemon.info avahi-daemon[1658]: Service "Fonera2.0 FTP Server" (/tmp/mdns//ftp.service) successfully established.
Jul 29 23:08:37 Fonera user.crit fonstated: finished running /etc/fonstated/StartFonsmcd
Jul 29 23:08:37 Fonera user.emerg syslog: starting onlined
Jul 29 23:08:37 Fonera user.notice root: runnow --> /etc/fonstated/FWallDaemon
Jul 29 23:08:37 Fonera user.info kernel: kjournald starting.  Commit interval 5 seconds
Jul 29 23:08:37 Fonera user.info kernel: EXT3 FS on sda2, internal journal
Jul 29 23:08:37 Fonera user.info kernel: EXT3-fs: recovery complete.
Jul 29 23:08:37 Fonera user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jul 29 23:08:37 Fonera user.crit mountd[2834]: ----------> mount ret = 0
Jul 29 23:08:37 Fonera daemon.info avahi-daemon[1658]: Got SIGHUP, reloading.
Jul 29 23:08:37 Fonera daemon.info avahi-daemon[1658]: Loading service file /tmp/mdns//ssh.service.
Jul 29 23:08:37 Fonera user.notice root: runnow --> /etc/fonstated/FWallDaemon
Jul 29 23:08:38 Fonera daemon.info avahi-daemon[1658]: Got SIGHUP, reloading.
Jul 29 23:08:38 Fonera daemon.info avahi-daemon[1658]: Loading service file /tmp/mdns//smb.service.
Jul 29 23:08:38 Fonera user.notice root: runnow --> /etc/fonstated/FWallDaemon
Jul 29 23:08:38 Fonera daemon.info dnsmasq[2990]: started, version 2.45 cachesize 150
Jul 29 23:08:38 Fonera daemon.info dnsmasq[2990]: compile time options: IPv6 GNU-getopt ISC-leasefile no-DBus no-I18N TFTP
Jul 29 23:08:38 Fonera user.info syslog: whitelist file: /etc/fon/whitelist.dnsmasq
Jul 29 23:08:38 Fonera daemon.info avahi-daemon[1658]: Service "Fonera2.0 SSH" (/tmp/mdns//ssh.service) successfully established.
Jul 29 23:08:39 Fonera daemon.info avahi-daemon[1658]: Service "LaFonera" (/tmp/mdns//smb.service) successfully established.
Jul 29 23:08:39 Fonera daemon.info dnsmasq[2990]: using local addresses only for domain lan
Jul 29 23:08:39 Fonera daemon.info dnsmasq[2990]: reading /tmp/dhcp.leases
Jul 29 23:08:39 Fonera daemon.info dnsmasq[2990]: reading /tmp/resolv.conf.auto
Jul 29 23:08:39 Fonera daemon.info dnsmasq[2990]: using nameserver 192.168.178.1#53
Jul 29 23:08:39 Fonera daemon.info dnsmasq[2990]: using local addresses only for domain lan
Jul 29 23:08:39 Fonera daemon.info dnsmasq[2990]: read /etc/hosts - 2 addresses
Jul 29 23:08:39 Fonera user.crit mountd[2834]: Got a autofs packet
Jul 29 23:08:39 Fonera user.crit mountd[2834]: kernel is requesting a mount -> sda2
Jul 29 23:08:42 Fonera user.notice root: adding tun-ovpn to firewall zone vpn
Jul 29 23:08:43 Fonera user.crit fonstated: enqueue --> SetupDlmd
Jul 29 23:08:43 Fonera user.crit fonstated: running event /etc/fonstated/SetupDlmd
Jul 29 23:08:43 Fonera user.crit fonstated: finished running /etc/fonstated/SetupDlmd
Jul 29 23:08:44 Fonera user.notice root: adding br-lan to firewall zone lan
Jul 29 23:08:44 Fonera user.notice root: adding eth0.2 to firewall zone wan
Jul 29 23:09:07 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:09:38 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:09:40 Fonera user.crit mountd[2834]: /tmp/run/mountd/sda2 has expired... unmounting
Jul 29 23:09:40 Fonera user.crit mountd[2834]: finished unmounting
Jul 29 23:10:09 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:10:40 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:11:11 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:11:42 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:12:13 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:12:44 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:13:15 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:13:45 Fonera user.warn kernel: RT305x_ESW: Link Status Changed
Jul 29 23:13:46 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:13:55 Fonera user.warn kernel: RT305x_ESW: Link Status Changed
Jul 29 23:13:56 Fonera user.warn kernel: RT305x_ESW: Link Status Changed
Jul 29 23:14:17 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:14:30 Fonera user.warn kernel: RT305x_ESW: Link Status Changed
Jul 29 23:14:48 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:15:19 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:15:50 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:16:21 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:16:52 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:17:23 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:17:54 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:18:25 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:18:56 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:19:06 Fonera authpriv.info dropbear[4152]: Child connection from 192.168.178.3:51010
Jul 29 23:19:07 Fonera authpriv.info dropbear[4152]: exit before auth: Exited normally
Jul 29 23:19:27 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:19:58 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:20:29 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:20:43 Fonera authpriv.info dropbear[4275]: Child connection from 192.168.178.3:51021
Jul 29 23:20:44 Fonera authpriv.info dropbear[4275]: exit before auth: Exited normally
Jul 29 23:21:00 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:21:31 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:21:57 Fonera authpriv.info dropbear[4373]: Child connection from 192.168.178.3:51031
Jul 29 23:21:58 Fonera authpriv.info dropbear[4373]: exit before auth: Exited normally
Jul 29 23:22:02 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:22:33 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:23:04 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:23:35 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:24:06 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:24:37 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success
Jul 29 23:24:47 Fonera authpriv.info dropbear[4589]: Child connection from 192.168.178.3:51051
Jul 29 23:24:58 Fonera authpriv.notice dropbear[4589]: password auth succeeded for 'root' from 192.168.178.3:51051
Jul 29 23:25:08 Fonera user.emerg syslog: onlined: failed to resolve hostname updates.fon.com: Success

comment:4 follow-up: Changed 7 years ago by matthijs

Yes, better like that :-)

Seems that it can somehow not resolve names using the DNS server you configured. Perhaps your modem does not allow DNS requests for clients that did not request a DHCP address? Or perhaps your modem isn't running its own DNS server (though I assume you got the DNS server address by peeking at what you get when running DHCP...).

In either case, you can probably work around this by configuring a public DNS server instead of pointing your Fonera at your modem. For example, try using "8.8.8.8" as the DNS server, this is Google's public DNS server network (see https://developers.google.com/speed/public-dns/).

comment:5 in reply to: ↑ 4 Changed 7 years ago by anonymous

Replying to matthijs:

Yes, better like that :-)

Seems that it can somehow not resolve names using the DNS server you configured. Perhaps your modem does not allow DNS requests for clients that did not request a DHCP address? Or perhaps your modem isn't running its own DNS server (though I assume you got the DNS server address by peeking at what you get when running DHCP...).

In either case, you can probably work around this by configuring a public DNS server instead of pointing your Fonera at your modem. For example, try using "8.8.8.8" as the DNS server, this is Google's public DNS server network (see https://developers.google.com/speed/public-dns/).

Matthijs, the google DNS server solves the "disconnected" problem. Thanx!

The menu seems very, very sluggish. I've now rebooted the Fon and have connected via IP now...and everything seems "in order".

I resolved the DNS address by following the instructions on how to configure a bridged connection with the Fon; which state to use your gateways IP. Weird thing is that when I entered the DNS of my ISP (212.54.40.25 / 212.54.35.25) the problem didn't resolve. I've added the Fon's MAC to the list of fixed IP's in my router, so I assumed this would work fine with the Fon being on a fixed IP. Apparantly not.

If you don't mind; I'd like to ask a question off topic.

  • Is there a way to be able to connect to the Fon by using Fonera instead of the IP?
  • Accessing the FTP server on the FON takes a long time to respond (awaiting welcoming message). I suppose this has to do with the routing?

comment:6 follow-up: Changed 7 years ago by matthijs

  • Resolution set to support
  • Status changed from infoneeded to closed
  • Type changed from bug to request

Good to hear it is solved. As for your other questions:

  • In bridge mode, the Fonera is not the DNS server for the clients, so it cannot make "fonera" resolve to itself. However, it does run a multicast DNS server, which can make "fonera.local" resolve to itself. For this, your client needs to run a multicast DNS (also known as mDns, Zeroconf, Avahi or Apple Bonjour) program. On MacOS X, this is enabled by default, on Linux this can be achieved by installing the "avahi" or "avahi-daemon" package, on Windows this can be done by installing the Bonour print service (which should also work for non-printers): http://support.apple.com/kb/DL999
  • The FTP server taking long, did you test this after fixing the DNS server on your Fonera? It is likely that this problem was caused by the DNS server being wrong / not working (I suspect the FTP server tries to do a "reverse DNS lookup" for every incoming connection, which could take a long time to complete when the DNS is not working correctly.

comment:7 in reply to: ↑ 6 Changed 7 years ago by powerpee@…

So, if I understand correctly if the Fonera is not the DNS server, then the Router should handle the DNS requests from within the LAN right...? The Fonera is placed in the LAN and has it's own IP address...sorry, I'm not very good at network stuff.

FTP access is indeed much faster now!

Thanks very much for the help, much appreciated! Keep up the development on Fonera :-)

Replying to matthijs:

Good to hear it is solved. As for your other questions:

  • In bridge mode, the Fonera is not the DNS server for the clients, so it cannot make "fonera" resolve to itself. However, it does run a multicast DNS server, which can make "fonera.local" resolve to itself. For this, your client needs to run a multicast DNS (also known as mDns, Zeroconf, Avahi or Apple Bonjour) program. On MacOS X, this is enabled by default, on Linux this can be achieved by installing the "avahi" or "avahi-daemon" package, on Windows this can be done by installing the Bonour print service (which should also work for non-printers): http://support.apple.com/kb/DL999
  • The FTP server taking long, did you test this after fixing the DNS server on your Fonera? It is likely that this problem was caused by the DNS server being wrong / not working (I suspect the FTP server tries to do a "reverse DNS lookup" for every incoming connection, which could take a long time to complete when the DNS is not working correctly.

comment:8 Changed 7 years ago by matthijs

Yes, you understand correctly (but only in bridge mode, in DHCP mode, the Fonera _is_ the DNS server).

Add Comment

Modify Ticket

Action
as closed The ticket will remain with no owner.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.