it's like your computer no longer has GPS! But you can simply switch to another public DNS server to resolve those issues. The number, known as an IP address, is a far better description of where CNET actually lives. That server tells your web browser that "" actually means "203.36.226.2". To figure out the "driving directions," if you will, your computer contacts a special server (called DNS, for Domain Name System) to figure out the route. Name=ppp-amnet password=XXXXXX use-peer-dns=yes user=XXXXXXĪdd name=dhcp_pool1 ranges=192.168.88.2-192.168.88.254Īdd address-pool=dhcp_pool1 authoritative=yes disabled=no interface=\Īdd bridge=bridge-local interface=ether2-master-localĪdd address=192.168.88.0/24 dns-server=192.168.88.1 gateway=192.168.88."" is just the street address of this website. Set 9 master-port=ether6-master-local name=ether10-slave-localĪdd add-default-route=yes allow=chap disabled=no interface=ether1-gateway \ Set 8 master-port=ether6-master-local name=ether9-slave-local Set 7 master-port=ether6-master-local name=ether8-slave-local Set 6 master-port=ether6-master-local name=ether7-slave-local Set 4 master-port=ether2-master-local name=ether5-slave-local Set 3 master-port=ether2-master-local name=ether4-slave-local Set 2 master-port=ether2-master-local name=ether3-slave-local Set 0 band=2ghz-b/g/n disabled=no frequency=2462 ht-rxchains=0,1 ht-txchains=\Ġ,1 l2mtu=2290 mode=ap-bridge name=XXXXXX ssid=XXXXXX wireless-protocol=\ Set allow-remote-requests=yes servers=XXXXXXĪdd address=192.168.88.1 name=lake-routerĪdd chain=input comment="default configuration" protocol=icmpĪdd chain=input comment="default configuration" connection-state=\Īdd chain=input comment="default configuration" connection-state=relatedĪdd action=drop chain=input comment="default configuration" \Īdd action=masquerade chain=srcnat comment="default NAT" out-interface=\Īdd disabled=no interface=ether3-slave-localĪdd disabled=no interface=ether6-master-localĪdd disabled=no interface=ether7-slave-localĪdd disabled=no interface=ether8-slave-localĪdd disabled=no interface=ether9-slave-local Set idle-timeout=none keepalive-timeout=2mĪdd name=default-dhcp ranges=192.168.88.10-192.168.88.254Īdd address-pool=default-dhcp authoritative=yes disabled=no interface=\Īdd bridge=bridge-local interface=ether3-slave-localĪdd bridge=bridge-local interface=ether6-master-localĪdd bridge=bridge-local interface=ether1-gatewayĪdd address=192.168.88.1/24 comment="default configuration" interface=\Īdd address=192.168.88.0/24 comment="default configuration" dns-server=\ġ92.168.88.1 gateway=192.168.88.1 netmask=24 Set 0 band=2ghz-b/g/n channel-width=20/40mhz-ht-above disabled=no \ĭistance=indoors ht-rxchains=0,1 ht-txchains=0,1 l2mtu=2290 mode=\Īp-bridge security-profile=lake ssid=lake wireless-protocol=802.11 Lake supplicant-identity="" unicast-ciphers=tkip,aes-ccm \ Tkip,aes-ccm management-protection=allowed mode=dynamic-keys name=\ Wpa-pre-shared-key=XXXXXX wpa2-pre-shared-key=XXXXXXĪdd authentication-types=wpa2-psk eap-methods=passthrough group-ciphers=\ Tkip,aes-ccm mode=dynamic-keys unicast-ciphers=tkip,aes-ccm \ Set authentication-types=wpa2-psk group-ciphers=\ Max-mru=1492 max-mtu=1492 name=pppoe-amnet password=XXXXXX \ Set 10 master-port=ether6-master-local name=ether10-slave-localĪdd add-default-route=yes allow=chap disabled=no interface=bridge-local \ Set 9 master-port=ether6-master-local name=ether9-slave-local Set 8 master-port=ether6-master-local name=ether8-slave-local Set 7 master-port=ether6-master-local name=ether7-slave-local My config is below it would be great if someone could give it a quick eyeball.Īdd admin-mac=D4:CA:6D:32:00:6A auto-mac=no l2mtu=1598 name=bridge-local \ I'm quite sure it has to do with my lousy understanding of bridging and switching groups, and that I'm doing something wrong. I've tried purging the ARP cache, and I've tried every port on the router with the same erratic response. In the case of one machine here (OS X), it will eventually be issued an IP, but still won't work. When I say 'don't connect', I mean aren't issued an IP. The problem is that ethernet clients either connect after a brief delay, work for anywhere from a few seconds to a few minutes, and then stop - or don't connect at all. Wireless clients connect fine, no worries there. I must admit that I am quite clueless on how port switching, slaving, and bridging works, or rather, what is the appropriate and 'best practice' solution with port switching and bridging. The router seems to work fine, with the exception that the ethernet ports are not behaving normally. I'm trying to set up a RB2011 for home use.