Bridge connection problems
I am connecting an old aironet 340 to a new Aironet 1300. I can get the association working and aironets talking. The problem is the 340 will not forward on any TCIP data. The association is connected and you can ping from the 1300 to the 340 and back but not past that point.
Both the 340 and the 1300 are in bridge mode. I can have the 1300 as the root and the 340 as non-root but that can be changed. If i change it around and the 340 is root I can ping and telnet from the 340 side but can not connect to the 1300. But the 340 and 1300 are still conected.
Similar Messages
-
I'm trying to connect a bridge connection between my laptop and USB connected android phone using this guide:
http://blog.mycila.com/2010/06/reverse- … id-22.html
My internet interface is wlan0, not eth0.
However, I run into problem:
$ sudo ifconfig wlan0 0.0.0.0
$ sudo ifconfig usb0 0.0.0.0
$ sudo brctl addbr br0
$ sudo brctl addif br0 wlan0
can't add wlan0 to bridge br0: Operation not supported
I also tried doing it this way:
On PC:
sudo ifconfig usb0 192.168.42.1
# enable routing
sysctl net.ipv4.ip_forward=1
# enable nat
iptables -t nat -I POSTROUTING -s 192.168.42.129 -j MASQUERADE -o wlan0
And issue this command on the phone:
route add -net default gw 192.168.42.1
But I can't even ping localhost from the phone
# ping 192.168.42.129
PING 192.168.42.129 (192.168.42.129) 56(84) bytes of data.
^C
--- 192.168.42.129 ping statistics ---
161 packets transmitted, 0 received, 100% packet loss, time 160105ms
# ping localhost
PING localhost (127.0.0.1) 56(84) bytes of data.
^C
--- localhost ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
# busybox ping localhost
PING localhost (127.0.0.1): 56 data bytes
Last edited by Lockheed (2013-01-28 11:37:21)Ok, so here's my conf:
# You should put this config-file in /etc/arno-iptables-firewall/ #
# --------------------------- Configuration file ------------------------------
# -= Arno's iptables firewall =-
# Single- & multi-homed firewall script with DSL/ADSL support
# (C) Copyright 2001-2012 by Arno van Amersfoort
# Co-authors : Lonnie Abelbeck & Philip Prindeville
# Homepage : http://rocky.eld.leidenuniv.nl/
# Freshmeat : http://freshmeat.net/projects/iptables-firewall/?topic_id=151
# Email : arnova AT rocky DOT eld DOT leidenuniv DOT nl
# (note: you must remove all spaces and substitute the @ and the .
# at the proper locations!)
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# version 2 as published by the Free Software Foundation.
# This program is distributed in the hope that it will be useful, but WITHOUT
# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
# FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
# more details.
# You should have received a copy of the GNU General Public License along with
# this program; if not, write to the Free Software Foundation Inc., 59 Temple
# Place - Suite 330, Boston, MA 02111-1307, USA.
# External (internet) interface settings #
# The external interface(s) that will be protected (and used as internet
# connection). This is probably ppp+ or dsl+ for non-transparent(!) (A)DSL
# modems otherwise it's probably "ethX" (eg. eth0). Multiple interfaces should
# be space separated.
EXT_IF="eth0 wlan0"
# Enable if THIS machines (dynamically) obtains its IP through (IPv4) DHCP
# and/or (IPv6) DHCPv6 (from your ISP)
EXT_IF_DHCP_IP=1
# (EXPERT SETTING!) Here you can specify your external(!) IPv4 subnet(s). You
# should only use this if you for example have a corporate network and/or
# running a DHCP server on your external(!) interface. Home users should
# normally NOT touch this setting. Multiple subnets should be space separated.
# Don't forget to specify a proper subnet masker (eg. /24, /16 or /8)!
#EXTERNAL_NET=""
# (EXPERT SETTING!) Here you can specify the IPv4 address used for broadcasts
# on your external subnet. You only need to set this option if you want to use
# the BROADCAST_XXX_NOLOG variables AND you use a non-standard broadcast
# address (not *.255.255.255, *.*.255.255 or *.*.*.255)! So normally leaving
# this empty should work fine. Multiple addresses should be space separated.
#EXT_NET_BCAST_ADDRESS=""
# Enable this if THIS MACHINE is running an IPv4 DHCP(BOOTP) server for a subnet
# on the external(!) interface. Note that you don't need this for internal
# subnets, as for these nets everything is accepted by default. Don't forget to
# configure the EXTERNAL_NET variable, to make this work. (IPv4 Only)
EXTERNAL_DHCP_SERVER=0
# Enable this if THIS MACHINE is running an IPv6 DHCPv6 server for a Link-Local
# address on the external(!) interface. Note that you don't need this for internal
# subnets, as for these nets everything is accepted by default. (IPv6 Only)
EXTERNAL_DHCPV6_SERVER=0
# Internal (LAN) interface settings #
# Specify here your internal network (LAN) interface(s). Multiple(!) interfaces
# should be space separated. Remark this if you don't have any internal network
# interfaces. Note that by default ALL traffic is accepted from these
# interfaces.
INT_IF="usb0 usb1"
# Specify here the internal IPv4 subnet(s) which is/are connected to the
# internal interface(s). For multiple interfaces(!) you can either specify
# multiple subnets here or specify one big subnet for all internal interfaces.
# Note that this variable is mainly used for antispoofing.
INTERNAL_NET="10.1.3.0/24"
# Set this variable to 0 to disable antispoof checking for the internal nets
# (EXPERT SETTING!)
INTERNAL_NET_ANTISPOOF=1
# (EXPERT SETTING!) Here you can specify the IPv4 address used for broadcasts
# on your internal subnet. You only need to set this option if you want to use
# the MAC filter AND you use a non-standard broadcast address
# (not *.255.255.255, *.*.255.255 or *.*.*.255)! So normally leaving
# this empty should work fine. Multiple addresses (if you have multiple
# internal nets) should be space separated.
#INT_NET_BCAST_ADDRESS=""
# DMZ (aka DeMilitarized Zone) settings #
# Put in the following variable the network interfaces that are DMZ-classified.
# You can also use this interface if you want to shield your Wireless network
# from your LAN.
DMZ_IF=""
# Specify here the subnet which is connected to the DMZ interface (DMZ_IF).
# For multiple interfaces(!) you can either specify multiple subnets here or
# specify one big subnet for all DMZ interfaces.
DMZ_NET=""
# Set this variable to 0 to disable antispoof checking for the dmz nets
# (EXPERT SETTING!)
DMZ_NET_ANTISPOOF=1
# NAT (Masquerade, SNAT, DNAT) settings (IPv4 only!) #
# Enable this if you want to perform NAT (masquerading) for your internal
# network (LAN) (eg. share your internet connection with your internal
# net(s) connected to eg. INT_IF)
NAT=1
# (EXPERT SETTING!) In case you would like to use SNAT instead of
# MASQUERADING then uncomment and set the IP or IPs here of your static
# external address(es). Note that when multiple IPs are specified, SNAT
# multiroute is enabled (load balancing over multiple external (internet)
# interfaces, check the README file for more info). Note that the order of IPs
# should match the order of interfaces (they belong to) in $EXT_IF!
#NAT_STATIC_IP="193.2.1.1"
# (EXPERT SETTING!) Use this variable only if you want specific subnets or
# hosts to be able to access the internet. When no value is specified, your
# whole internal net will have access. In both cases it's obviously only
# meaningful when NAT is enabled. Note that you can also use this variable if
# you want to use NAT for your DMZ.
NAT_INTERNAL_NET="$INTERNAL_NET"
# (EXPERT SETTING!) Enable this if you want to be able to redirect local ports
# or protocols on your gateway using NAT forwards.
NAT_LOCAL_REDIRECT=0
# NAT TCP/UDP/IP forwards. Forward ports or protocols from the gateway to
# an internal client through (D)NAT. Note that you can also use these
# variables to forward ports to DMZ hosts.
# TCP/UDP form:
# "{SRCIP1,SRCIP2,...~}PORT1,PORT2-PORT3,...>DESTIP1{~port} \
# {SRCIP3,...~}PORT3,...>DESTIP2{~port}"
# IP form:
# "{SRCIP1,SRCIP2,...~}PROTO1,PROTO2,...>DESTIP1 \
# {SRCIP3~}PROTO3,PROTO4,...>DESTIP2"
# TCP/UDP port forward examples:
# Simple (forward port 80 to internal host 192.168.0.10):
# NAT_FORWARD_xxx="80>192.168.0.10 20,21>192.168.0.10"
# Advanced (forward port 20 & 21 to 192.168.0.10 and
# forward from 1.2.3.4 port 81 to 192.168.0.11 port 80:
# NAT_FORWARD_xxx="1.2.3.4~81>192.168.0.11~80"
# IP protocol forward example:
# (forward protocols 47 & 48 to 192.168.0.10)
# NAT_FORWARD_IP="47,48>192.168.0.10"
# NOTE 1: {~port} is optional. Use it to redirect a specific port to a
# different port on the internal client.
# NOTE 2: {SRCIPx} is optional. Use it to restrict access for specific source
# (inet) IP addresses.
# (IPv4 Only)
NAT_FORWARD_TCP=""
NAT_FORWARD_UDP=""
NAT_FORWARD_IP=""
# TCP/UDP/IP forwards. Forward IPv6 and non-NAT'ed IPv4 ports or protocols
# from the gateway to an internal client. Note that you can also use these
# variables to forward ports to DMZ hosts.
# TCP/UDP form:
# "SRCIP1,SRCIP2,...>DESTIP1{~port} \
# SRCIP3,...>DESTIP2{~port}"
# IP form:
# "SRCIP1,SRCIP2,...>DESTIP1~PROTO \
# SRCIP3,...>DESTIP2~PROTO"
# TCP/UDP port forward examples:
# Simple (IPv6 forward port 80 to internal host 2001:db8::2):
# INET_FORWARD_TCP="::/0>2001:db8::2~80"
# Simple (IPv4 non-NAT forward port 80 to internal host 192.168.0.10):
# INET_FORWARD_TCP="0/0>192.168.0.10~80"
# Advanced (forward all UDP ports for 2000::/3 net to 2001:db8::/32 net):
# INET_FORWARD_UDP="2000::/3>2001:db8::/32"
# IP protocol forward example:
# (forward protocol 58 (ICMPv6) to 2001:db8::2)
# INET_FORWARD_IP="::/0>2001:db8::2~58"
# (IPv6 and non-NAT'ed IPv4 Only)
INET_FORWARD_TCP=""
INET_FORWARD_UDP=""
INET_FORWARD_IP=""
# General settings #
# (EXPERT SETTING!) Location of the iptables-binary (use 'locate iptables' or
# 'whereis iptables' to manually locate it), required for (default) IPv4 support
IP4TABLES="/usr/sbin/iptables"
# (EXPERT SETTING!) Location of the ip6tables-binary (use 'locate ip6tables' or
# 'whereis ip6tables' to manually locate it), required for IPv6 support
IP6TABLES="/usr/sbin/ip6tables"
# (EXPERT SETTING!) Location of the environment file
ENV_FILE="/usr/share/arno-iptables-firewall/environment"
# (EXPERT SETTING!) Location of plugin binary & config files
PLUGIN_BIN_PATH="/usr/share/arno-iptables-firewall/plugins"
PLUGIN_CONF_PATH="/etc/arno-iptables-firewall/plugins"
# Most people don't want to get any firewall logs being spit to the console.
# This option makes the kernel ring buffer only log messages with level
# "panic".
DMESG_PANIC_ONLY=1
# Enable this if you want TOS mangling (RFC)
MANGLE_TOS=0
# Enable this if you want to set the maximum packet size via the
# Maximum Segment Size(through MSS field)
SET_MSS=1
# Enable this if you want to increase the TTL value by one in the prerouting
# chain. This hides the firewall when performing eg. traceroutes to internal
# hosts. (IPv4 only!)
TTL_INC=0
# (EXPERT SETTING!) Enable this if you want to set the TTL value for packets in
# the OUTPUT & FORWARD chain. Note that this only works with newer 2.6 kernels
# (2.6.14 or better) or patched 2.4 kernels, which have netfilter TTL target
# support. Don't mess with this unless you really know what you are doing!
# (IPv4 only!)
#PACKET_TTL="64"
# Enable this to support the IRC-protocol.
USE_IRC=0
# (EXPERT SETTING!) Loosen the forward chain for the external interface(s).
# Enable it to allow the use of protocols like UPnP. Note that it *could* be
# less secure.
LOOSE_FORWARD=0
# (EXPERT SETTING!) Enable (1) to allow IPv6 Link-Local addresses to be
# forwarded between interfaces. (IPv6 Only)
FORWARD_LINK_LOCAL=0
# (EXPERT SETTING!) Disable (0) to not drop all IPv6 packets with
# Routing Header Type 0. Enabled by default. (IPv6 Only)
IPV6_DROP_RH_ZERO=1
# (EXPERT SETTING!) Enable this if you want to drop packets originating from a
# private address.
# Note: To enable logging of dropped private addresses set RESERVED_NET_LOG=1
RESERVED_NET_DROP=0
# (EXPERT SETTING!) Protect this machine from being abused for a DRDOS-attack
# ("Distributed Reflection Denial Of Service"-attack). (STILL EXPERIMENTAL!)
DRDOS_PROTECT=0
# Enable (1) if you want to enable mixed IPv4/IPv6 traffic support
# Disable (0) if you want to enable only IPv4 traffic support
IPV6_SUPPORT=0
# This option fixes problems with SMB broadcasts when using nmblookup
NMB_BROADCAST_FIX=0
# Set this to 0 to suppress "assuming module is compiled in kernel" messages
COMPILED_IN_KERNEL_MESSAGES=1
# (EXPERT SETTING!) You can choose the default policy for the INPUT & FORWARD
# chain here (1=DROP, 0=ACCEPT). The default policy is DROP. This means that
# when there are no rule(s) available (yet), the packet will be DROPPED. In
# practice this rule only does something while the firewall is starting. Once
# it's started and all rules are in place, the default policy doesn't do
# anything anymore. People that use eg. NFS and let their clients boot from NFS
# (diskless client systems) probably want to disable this option to fix
# "NFS server not responding" etc. errors on their clients.
DEFAULT_POLICY_DROP=1
# (EXPERT SETTING!) (Other) trusted network interfaces for which ALL IP
# traffic should be ACCEPTED. (multiple(!) interfaces should be space
# separated). Be warned that anything TO and FROM these interfaces is allowed
# (ACCEPTED) so make sure it's NOT routable(accessible) from the outside world
# (internet)! And of course putting one of your external interfaces here would
# be extremely stupid.
TRUSTED_IF=""
# (EXPERT SETTING!) Put here the interfaces that should trust
# each other (accept forward traffic). You can use | (piping-sign) to create
# seperate interface groups. And (again) of course putting one of your external
# interfaces here would be extremely stupid.
IF_TRUSTS=""
# Location of the custom iptables rules file (if any).
CUSTOM_RULES="/etc/arno-iptables-firewall/custom-rules"
# Location of the local (user/global) configuration file, if used
LOCAL_CONFIG_FILE=""
# (EXPERT SETTING!) Set this (to 1) to disable the use of iptables-save and
# iptables-restore to add rules in batch rather than one-by-one. Much slower
# when disabled. BLOCK_HOSTS and BLOCK_HOSTS_FILE utilizes this feature.
DISABLE_IPTABLES_BATCH=0
# (EXPERT SETTING!) Set this (to 1) to enable tracing
TRACE=0
# Logging options - All logging is rate limited to prevent log flooding #
# Enable logging for explicitly blocked hosts.
BLOCKED_HOST_LOG=1
# Enable logging for various stealth scans (reliable).
SCAN_LOG=1
# Enable logging for possible stealth scans (less reliable).
POSSIBLE_SCAN_LOG=1
# Enable logging for TCP-packets with bad flags.
BAD_FLAGS_LOG=1
# Enable logging of invalid TCP packets. Keep disabled (0) by default to reduce
# INVALID packets being logged because of lost (legimate) connections. When
# debugging any problems, you should enable it (temporarily)!
INVALID_TCP_LOG=0
# Enable logging of invalid UDP packets. Keep disabled (0) by default to reduce
# INVALID packets being logged because of lost (legimate) connections. When
# debugging any problems, you should enable it (temporarily)!
INVALID_UDP_LOG=0
# Enable logging of invalid ICMP packets. Keep disabled (0) by default to reduce
# INVALID packets being logged because of lost (legimate) connections. When
# debugging any problems, you should enable it (temporarily)!
INVALID_ICMP_LOG=0
# Enable (1) logging of source IPs with reserved or private addresses.
RESERVED_NET_LOG=0
# Enable logging of fragmented packets.
FRAG_LOG=1
# Enable logging of denied local (OUTPUT) connections.
INET_OUTPUT_DENY_LOG=1
# Enable logging of denied LAN output (FORWARD) connections.
LAN_OUTPUT_DENY_LOG=1
# Enable logging of denied LAN INPUT connections.
LAN_INPUT_DENY_LOG=1
# Enable logging of denied DMZ output (FORWARD) connections.
DMZ_OUTPUT_DENY_LOG=1
# Enable logging of denied DMZ input (FORWARD) connections.
DMZ_INPUT_DENY_LOG=1
# Enable logging of dropped FORWARD packets.
FORWARD_DROP_LOG=1
# Enable logging of dropped IPv6 Link-Local forwarded packets.
# Note: requires FORWARD_LINK_LOCAL=0 (IPv6 Only)
LINK_LOCAL_DROP_LOG=1
# Enable logging of dropped ICMP-request packets (ping).
ICMP_REQUEST_LOG=1
# Enable logging of dropped "other" ICMP packets.
ICMP_OTHER_LOG=1
# Enable logging of normal connection attempts to privileged TCP ports.
PRIV_TCP_LOG=1
# Enable logging of normal connection attempts to privileged UDP ports.
PRIV_UDP_LOG=1
# Enable logging of normal connection attempts to unprivileged TCP ports.
UNPRIV_TCP_LOG=1
# Enable logging of normal connection attempts to unprivileged UDP ports.
UNPRIV_UDP_LOG=1
# Enable logging of IPv4 IGMP packets
IGMP_LOG=1
# Enable logging of normal connection attempts to "other-IP"-protocols (non
# TCP/UDP/ICMP/IGMP).
OTHER_IP_LOG=1
# Enable logging for ICMP flooding.
ICMP_FLOOD_LOG=1
# (EXPERT SETTING!) The location of the dedicated firewall log file. When
# enabled the firewall script will also log start/stop etc. info to this file
# as well. Note that in order to make this work, you should also configure
# syslogd to log firewall messages to this file (see LOGLEVEL below for further
# info).
#FIREWALL_LOG="/var/log/firewall.log"
# (EXPERT SETTING!) Current log-level ("info": default kernel syslog level)
# "debug": can be used to log to /var/log/firewall.log, but you have to configure
# syslogd accordingly (see included syslogd.conf examples).
LOGLEVEL="info"
# Put in the following variables which hosts you want to log certain incoming
# connection attempts for.
# TCP/UDP port format (LOG_HOST_INPUT_xxx):
# "host1,host2~port1,port2 host3,host4~port3,port4 ..."
# IP protocol format (LOG_HOST_INPUT_IP):
# "host1,host2~proto1,proto2 host3,host4~proto4,proto4 ..."
LOG_HOST_INPUT_TCP=""
LOG_HOST_INPUT_UDP=""
LOG_HOST_INPUT_IP=""
# Put in the following variables which hosts you want to log certain outgoing
# connection attempts for.
# TCP/UDP port format (LOG_HOST_OUTPUT_xxx):
# "host1,host2~port1,port2 host3,host4~port3,port4 ..."
# IP protocol format (LOG_HOST_OUTPUT_IP):
# "host1,host2~proto1,proto2 host3,host4~proto4,proto4 ..."
LOG_HOST_OUTPUT_TCP=""
LOG_HOST_OUTPUT_UDP=""
LOG_HOST_OUTPUT_IP=""
# Put in the following variables which services you want to log incoming
# connection attempts for.
LOG_INPUT_TCP=""
LOG_INPUT_UDP=""
LOG_INPUT_IP=""
# Put in the following variables which services you want to log outgoing
# connection attempts for.
LOG_OUTPUT_TCP=""
LOG_OUTPUT_UDP=""
LOG_OUTPUT_IP=""
# Put in the following variable which hosts you want to log incoming connection
# (attempts) for.
LOG_HOST_INPUT=""
# Put in the following variable which hosts you want to log outgoing connection
# (attempts) to.
LOG_HOST_OUTPUT=""
# sysctl based settings (EXPERT SETTINGS!) #
# Enable for synflood protection (through /proc/.../tcp_syncookies).
SYN_PROT=1
# Enable this to reduce the ability of others DOS'ing your machine.
REDUCE_DOS_ABILITY=1
# Enable to ignore all ICMP echo-requests (IPv4) on ALL interfaces.
ECHO_IGNORE=0
# Enable to log packets with impossible addresses to the kernel log.
LOG_MARTIANS=0
# Only disable this if you're NOT using forwarding (required for NAT etc.) for
# increased security.
# Note: If enabled and IPV6 enabled, local IPv6 autoconf will be disabled.
IP_FORWARDING=1
# (EXPERT SETTING!) Only disable this if IP_FORWARDING is disabled and
# you do not use autoconf to obtain your IPv6 address.
# Note: This is ignored if IP_FORWARDING is enabled. (IPv6 Only)
IPV6_AUTO_CONFIGURATION=1
# Enable if you want to accept ICMP redirect messages. Should be set to "0" in
# case of a router.
ICMP_REDIRECT=0
# Enable/modify this if you want to be a able to handle a larger (or smaller)
# number of simultaneous connections. For high traffic machines I recommend to
# use a value of at least 16384 (note that a higher value (obviously) also uses
# more memory).
CONNTRACK=16384
# Enable ECN (Explicit Congestion Notification) TCP flag. Disabled by default,
# as some routers are still not compatible with this.
ECN=0
# Enable to drop connections from non-routable IPs, eg. prevent source
# routing. By default the firewall itself also provides rules against source
# routing. Note than when you use eg. VPN (Freeswan), you should probably
# disable this setting.
RP_FILTER=1
# Protect against source routed packets. Attackers can use source routing to
# generate traffic pretending to be from inside your network, but which is
# routed back along the path from which it came, namely outside, so attackers
# can compromise your network. Source routing is rarely used for legitimate
# purposes, so normally you should always leave this enabled(1)!
SOURCE_ROUTE_PROTECTION=1
# Here we set the local port range (ports from which connections are
# initiated from our site). Don't mess with this unless you really know what
# you are doing!
LOCAL_PORT_RANGE="32768 61000"
# Here you can change the default TTL used for sending packets. The value
# should be between 10 and 255. Don't mess with this unless you really know
# what you are doing!
DEFAULT_TTL=64
# In most cases pmtu discovery is ok, but in some rare cases (when having
# problems) you might want to disable it.
NO_PMTU_DISCOVERY=0
# Firewall policies for the LAN (EXPERT SETTINGS!) #
# LAN_xxx = LAN->localhost(this machine) input access rules #
# Note that when both LAN_OPEN_xxx & LAN_HOST_OPEN_xxx are NOT used, the #
# default policy for this chain is accept (unless denied through #
# LAN_DENY_xxx and/or LAN_HOST_DENY_xxx)! #
# Enable this to allow for ICMP-requests(ping) from your LAN
LAN_OPEN_ICMP=1
# Put in the following variables the TCP/UDP ports or IP protocols TO
# (remote end-point) which the LAN hosts are permitted to connect to.
LAN_OPEN_TCP=""
LAN_OPEN_UDP=""
LAN_OPEN_IP=""
# Put in the following variables the TCP/UDP ports or IP protocols TO (remote
# end-point) which LAN hosts are NOT permitted to connect to.
LAN_DENY_TCP=""
LAN_DENY_UDP=""
LAN_DENY_IP=""
# Put in the following variables the TCP/UDP ports or IP
# protocols TO (remote end-point) which certain LAN hosts are
# permitted to connect to.
# TCP/UDP port format (LAN_INPUT_HOST_OPEN_xxx):
# "host1,host2~port1,port2 host3,host4~port3,port4 ..."
# IP protocol format (LAN_INPUT_HOST_OPEN_xxx):
# "host1,host2~proto1,proto2 host3,host4~proto3,proto4 ..."
LAN_HOST_OPEN_TCP=""
LAN_HOST_OPEN_UDP=""
LAN_HOST_OPEN_IP=""
# Put in the following variables the TCP/UDP ports or IP protocols TO (remote
# end-point) which certain LAN hosts are NOT permitted to connect to.
# TCP/UDP port format (LAN_INPUT_HOST_DENY_xxx):
# "host1,host2~port1,port2 host3,host4~port3,port4 ..."
# IP protocol format (LAN_INPUT_HOST_DENY_xxx):
# "host1,host2~proto1,proto2 host3,host4~proto3,proto4 ..."
LAN_HOST_DENY_TCP=""
LAN_HOST_DENY_UDP=""
LAN_HOST_DENY_IP=""
# LAN_INET_xxx = LAN->internet access rules (forward) #
# Note that when both LAN_INET_OPEN_xxx & LAN_INET_HOST_OPEN_xxx are NOT #
# used, the default policy for this chain is accept (unless denied #
# through LAN_INET_DENY_xxx and/or LAN_INET_HOST_DENY_xxx)! #
# Enable this to allow for ICMP-requests(ping) for LAN->INET
LAN_INET_OPEN_ICMP=1
# Put in the following variables the TCP/UDP ports or IP
# protocols TO (remote end-point) which the LAN hosts are
# permitted to connect to via the external (internet) interface.
LAN_INET_OPEN_TCP=""
LAN_INET_OPEN_UDP=""
LAN_INET_OPEN_IP=""
# Put in the following variables the TCP/UDP ports or IP protocols TO (remote
# end-point) which the LAN hosts are NOT permitted to connect to
# via the external (internet) interface. Examples of usage are for blocking
# IRC (TCP 6666:6669) for the internal network.
LAN_INET_DENY_TCP=""
LAN_INET_DENY_UDP=""
LAN_INET_DENY_IP=""
# Put in the following variables which LAN hosts you want to allow to certain
# hosts/services on the internet. By default all services are allowed.
# TCP/UDP form:
# "SRCIP1,SRCIP2,...>DESTIP1~port \
# SRCIP3,...>DESTIP2~port"
# IP form:
# "SRCIP1,SRCIP2,...>DESTIP1~protocol \
# SRCIP3,...>DESTIP2~protocol"
# TCP/UDP examples:
# Simple:
# (Allow port 80 on INET host 1.2.3.4 for all LAN hosts(0/0)):
# LAN_INET_HOST_OPEN_xxx="0/0>1.2.3.4~80"
# Advanced:
# (Allow port 20 & 21 on INET host 1.2.3.4 for all LAN hosts(0/0) and
# allow port 80 on INET host 1.2.3.4 for LAN host 192.168.0.10 (only)):
# LAN_INET_HOST_OPEN_xxx="0/0>1.2.3.4~20,21 192.168.0.10>80"
# IP protocol example:
# (Allow protocols 47 & 48 on INET host 1.2.3.4 for all LAN hosts(0/0))
# LAN_INET_HOST_OPEN_IP="0/0>1.2.3.4~47,48"
# NOTE 1: If no SRCIPx is specified, any source host is used
# NOTE 2: If no port is specified, any port is used
LAN_INET_HOST_OPEN_TCP=""
LAN_INET_HOST_OPEN_UDP=""
LAN_INET_HOST_OPEN_IP=""
# Put in the following variables which DMZ hosts you want to deny to certain
# hosts/services on the internet.
# TCP/UDP form:
# "SRCIP1,SRCIP2,...>DESTIP1~port \
# SRCIP3,...>DESTIP2~port"
# IP form:
# "SRCIP1,SRCIP2,...>DESTIP1~protocol \
# SRCIP3,...>DESTIP2~protocol"
# TCP/UDP examples:
# Simple (Deny port 80 on INET host 1.2.3.4 for all LAN hosts(0/0)):
# LAN_INET_HOST_DENY_xxx="0/0>1.2.3.4~80"
# Advanced (Deny port 20 & 21 on INET host 1.2.3.4 for all LAN hosts(0/0) and
# deny port 80 on INET host 1.2.3.4 for LAN host 192.168.0.10 (only)):
# LAN_INET_HOST_DENY_xxx="0/0>1.2.3.4~20,21 192.168.0.10>1.2.3.4~80"
# IP protocol example:
# (Deny protocols 47 & 48 on INET host 1.2.3.4 for all LAN hosts(0/0)):
# LAN_INET_HOST_DENY_IP="0/0>1.2.3.4~47,48"
# NOTE 1: If no SRCIPx is specified, any source host is used
# NOTE 2: If no port is specified, any port is used
LAN_INET_HOST_DENY_TCP=""
LAN_INET_HOST_DENY_UDP=""
LAN_INET_HOST_DENY_IP=""
# Firewall policies for the DMZ (EXPERT SETTINGS!) #
# DMZ_xxx = DMZ->localhost(this machine) input access rules #
# Enable this to allow ICMP-requests(ping) from the DMZ
DMZ_OPEN_ICMP=1
# Put in the following variables which DMZ hosts are permitted to connect to
# certain the TCP/UDP ports, IP protocols or ICMP. By default all (local)
# services are blocked for DMZ hosts.
DMZ_OPEN_TCP=""
DMZ_OPEN_UDP=""
DMZ_OPEN_IP=""
# Put in the following variables which DMZ hosts you want to allow for certain
# services. By default all (local) services are blocked for DMZ hosts.
# TCP/UDP port format (DMZ_HOST_OPEN_TCP & DMZ_HOST_OPEN_UDP):
# "host1,host2~port1,port2 host3,host4~port3,port4 ..."
# IP protocol format (DMZ_HOST_OPEN_IP):
# "host1,host2~proto1,proto2 host3,host4~proto3,proto4 ..."
DMZ_HOST_OPEN_TCP=""
DMZ_HOST_OPEN_UDP=""
DMZ_HOST_OPEN_IP=""
# INET_DMZ_xxx = Internet->DMZ access rules (forward) #
# Note: As of Version 2.0.0 the default policy has changed to DROP #
# Previous to Version 2.0.0 the default policy was ACCEPT #
# Enable this to make the default policy allow for ICMP(ping) for INET->DMZ
INET_DMZ_OPEN_ICMP=0
# Put in the following variables which INET hosts are permitted to connect to
# certain the TCP/UDP ports or IP protocols in the DMZ.
INET_DMZ_OPEN_TCP=""
INET_DMZ_OPEN_UDP=""
INET_DMZ_OPEN_IP=""
# Put in the following variables which INET hosts are NOT permitted to connect
# to certain the TCP/UDP ports or IP protocols in the DMZ.
INET_DMZ_DENY_TCP=""
INET_DMZ_DENY_UDP=""
INET_DMZ_DENY_IP=""
# Put in the following variables which INET hosts you want to allow to certain
# hosts/services on the DMZ net. By default all services are dropped.
# TCP/UDP form:
# "SRCIP1,SRCIP2,...>DESTIP1~port \
# SRCIP3,...>DESTIP2~port"
# IP form:
# "SRCIP1,SRCIP2,...>DESTIP1~protocol \
# SRCIP3,...>DESTIP2~protocol"
# TCP/UDP examples:
# Simple (Allow port 80 on DMZ host 1.2.3.4 for all INET hosts(0/0)):
# INET_DMZ_HOST_OPEN_xxx="0/0>1.2.3.4~80"
# Advanced (Allow port 20 & 21 on DMZ host 1.2.3.4 for all INET hosts(0/0) and
# allow port 80 on DMZ host 1.2.3.4 for INET host 5.6.7.8 (only)):
# INET_DMZ_HOST_OPEN_xxx="0/0>1.2.3.4~20,21 5.6.7.8>1.2.3.4~80"
# IP protocol example:
# (Allow protocols 47 & 48 on INET host 1.2.3.4 for all DMZ hosts )
# INET_DMZ_HOST_OPEN_IP="0/0>1.2.3.4~47,48"
# NOTE 1: If no SRCIPx is specified, any source host is used
# NOTE 2: If no port is specified, any port is used
INET_DMZ_HOST_OPEN_TCP=""
INET_DMZ_HOST_OPEN_UDP=""
INET_DMZ_HOST_OPEN_IP=""
# Put in the following variables which INET hosts you want to deny to certain
# hosts/services on the DMZ net.
# TCP/UDP form:
# "SRCIP1,SRCIP2,...>DESTIP1~port \
# SRCIP3,...>DESTIP2~port"
# IP form:
# "SRCIP1,SRCIP2,...>DESTIP1~protocol \
# SRCIP3,...>DESTIP2~protocol"
# TCP/UDP examples:
# Simple (Deny port 80 on DMZ host 1.2.3.4 for all INET hosts(0/0)):
# INET_DMZ_HOST_DENY_xxx="0/0>1.2.3.4~80"
# Advanced (Deny port 20 & 21 on DMZ host 1.2.3.4 for all INET hosts(0/0) and
# deny port 80 on DMZ host 1.2.3.4 for INET host 5.6.7.8 (only)):
# INET_DMZ_HOST_DENY_xxx="0/0>1.2.3.4~20,21 5.6.7.8>1.2.3.4~80"
# IP protocol example:
# (Deny protocols 47 & 48 on DMZ host 1.2.3.4 for all INET hosts):
# INET_DMZ_HOST_DENY_IP="0/0>1.2.3.4~47,48"
# NOTE 1: If no SRCIPx is specified, any source host is used
# NOTE 2: If no port is specified, any port is used
INET_DMZ_HOST_DENY_TCP=""
INET_DMZ_HOST_DENY_UDP=""
INET_DMZ_HOST_DENY_IP=""
# DMZ_INET_xxx = DMZ->internet access rules (forward) #
# Note that when both DMZ_INET_OPEN_xxx & DMZ_INET_HOST_OPEN_xxx are NOT #
# used, the default policy for this chain is accept (unless denied #
# through DMZ_INET_DENY_xxx and/or DMZ_INET_HOST_DENY_xxx)! #
# Enable this to make the default policy allow for ICMP(ping) for DMZ->INET
DMZ_INET_OPEN_ICMP=1
# Put in the following variables the TCP/UDP ports or IP
# protocols TO (remote end-point) which the DMZ hosts are
# permitted to connect to via the external (internet) interface.
DMZ_INET_OPEN_TCP=""
DMZ_INET_OPEN_UDP=""
DMZ_INET_OPEN_IP=""
# Put in the following variables the TCP/UDP ports or IP protocols TO (remote
# end-point) which the DMZ hosts are NOT permitted to connect to
# via the external (internet) interface. Examples of usage are for blocking
# IRC (TCP 6666:6669) for the internal network.
DMZ_INET_DENY_TCP=""
DMZ_INET_DENY_UDP=""
DMZ_INET_DENY_IP=""
# Put in the following variables which DMZ hosts you want to allow to certain
# hosts/services on the internet. By default all services are allowed.
# TCP/UDP form:
# "SRCIP1,SRCIP2,...>DESTIP1~port \
# SRCIP3,...>DESTIP2~port"
# IP form:
# "SRCIP1,SRCIP2,...>DESTIP1~protocol \
# SRCIP3,...>DESTIP2~sprotocol"
# TCP/UDP examples:
# Simple (Allow port 80 on INET host 1.2.3.4 for all DMZ hosts(0/0)):
# DMZ_INET_HOST_OPEN_xxx="0/0>1.2.3.4~80"
# Advanced (Allow port 20 & 21 on INET host 1.2.3.4 for all DMZ hosts(0/0) and
# allow port 80 on INET host 1.2.3.4 for DMZ host 5.6.7.8 (only)):
# DMZ_INET_HOST_OPEN_xxx="0/0>1.2.3.4~20,21 5.6.7.8>1.2.3.4~80"
# IP protocol example:
# (Allow protocols 47 & 48 on INET host 1.2.3.4 for all DMZ hosts):
# DMZ_INET_HOST_OPEN_IP="0/0>1.2.3.4~47,48"
# NOTE 1: If no SRCIPx is specified, any source host is used
# NOTE 2: If no port is specified, any port is used
DMZ_INET_HOST_OPEN_TCP=""
DMZ_INET_HOST_OPEN_UDP=""
DMZ_INET_HOST_OPEN_IP=""
# Put in the following variables which DMZ hosts you want to deny to certain
# hosts/services on the internet.
# TCP/UDP form:
# "SRCIP1,SRCIP2,...>DESTIP1~port \
# SRCIP3,...>DESTIP2~port"
# IP form:
# "SRCIP1,SRCIP2,...>DESTIP1~protocol \
# SRCIP3,...>DESTIP2~protocol"
# TCP/UDP examples:
# Simple (Deny port 80 on INET host 1.2.3.4 for all DMZ hosts(0/0)):
# DMZ_INET_HOST_DENY_xxx="0/0>1.2.3.4~80"
# Advanced (Deny port 20 & 21 on INET host 1.2.3.4 for all DMZ hosts(0/0) and
# deny port 80 on INET host 1.2.3.4 for DMZ host 5.6.7.8 (only)):
# DMZ_INET_HOST_DENY_xxx="0/0>1.2.3.4~20,21 5.6.7.8>1.2.3.4~80"
# IP protocol example:
# (Deny protocols 47 & 48 on INET host 1.2.3.4 for all DMZ hosts(0/0)):
# DMZ_INET_HOST_DENY_IP="0/0>1.2.3.4:47,48"
# NOTE 1: If no SRCIPx is specified, any source host is used
# NOTE 2: If no port is specified, any port is used
DMZ_INET_HOST_DENY_TCP=""
DMZ_INET_HOST_DENY_UDP=""
DMZ_INET_HOST_DENY_IP=""
# DMZ_LAN_xxx = DMZ->LAN access rules (forward) #
# Enable this to make the default policy allow for ICMP(ping) for DMZ->LAN
DMZ_LAN_OPEN_ICMP=0
# Put in the following variables which DMZ hosts you want to allow to certain
# hosts/services on the LAN (net).
# TCP/UDP form:
# "SRCIP1,SRCIP2,...>DESTIP1~port \
# SRCIP3,...>DESTIP2~port"
# IP form:
# "SRCIP1,SRCIP2,...>DESTIP1~protocol \
# SRCIP3,...>DESTIP2~protocol"
# TCP/UDP examples:
# Simple (Allow port 80 on LAN host 1.2.3.4 for all DMZ hosts(0/0)):
# DMZ_LAN_HOST_OPEN_xxx="0/0>1.2.3.4~80"
# Advanced (Allow port 20 & 21 on LAN host 1.2.3.4 for all DMZ hosts (0/0) and
# allow port 80 for DMZ host 5.6.7.8 (only) on LAN host
# 1.2.3.4):
# DMZ_LAN_HOST_OPEN_xxx="0/0>1.2.3.4~20,21 5.6.7.8>1.2.3.4~80"
# IP protocol example:
# (Allow protocols 47 & 48 on LAN host 1.2.3.4 for all DMZ hosts(0/0)):
# DMZ_LAN_HOST_OPEN_IP="0/0>1.2.3.4~47,48"
# NOTE 1: If no SRCIPx is specified, any source host is used
# NOTE 2: If no port is specified, any port is used
DMZ_LAN_HOST_OPEN_TCP=""
DMZ_LAN_HOST_OPEN_UDP=""
DMZ_LAN_HOST_OPEN_IP=""
# Firewall policies for the external (inet) interface (default policy = drop) #
# Put in the following variable which hosts (subnets) you want have full access
# via your internet (EXT_IF) connection(!). This is especially meant for
# networks/servers which use NIS/NFS, as these protocols require all ports
# to be open.
# NOTE: Don't mistake this variable with the one used for internal nets.
FULL_ACCESS_HOSTS=""
# Put in the following variable which TCP/UDP ports you don't want to
# see broadcasts from (eg. DHCP (67/68) on your EXTERNAL interface. Note that
# to make this properly work you also need to set "EXTERNAL_NET"!
BROADCAST_TCP_NOLOG=""
#BROADCAST_UDP_NOLOG="67 68"
# Put in the following variables which hosts you want to allow for certain
# services.
# TCP/UDP port format (HOST_OPEN_TCP & HOST_OPEN_UDP):
# "host1,host2~port1,port2 host3,host4~port3,port4 ..."
# IP protocol format (HOST_OPEN_IP):
# "host1,host2~proto1,proto2 host3,host4~proto4,proto4 ..."
# ICMP protocol format (HOST_OPEN_ICMP):
# "host1 host2 ...."
HOST_OPEN_TCP=""
HOST_OPEN_UDP=""
HOST_OPEN_IP=""
HOST_OPEN_ICMP=""
# Put in the following variables which hosts you want to DENY(DROP) for certain
# services (and logged).
# to DENY(DROP) for certain hosts.
# TCP/UDP port format (HOST_DENY_TCP & HOST_DENY_UDP):
# "host1,host2~port1,port2 host3,host4~port3,port4 ..."
# IP protocol format (HOST_DENY_IP):
# "host1,host2~proto1,proto2 host3,host4~proto4,proto4 ..."
# ICMP protocol format (HOST_DENY_ICMP):
# "host1 host2 ...."
HOST_DENY_TCP=""
HOST_DENY_UDP=""
HOST_DENY_IP=""
HOST_DENY_ICMP=""
# Put in the following variables which hosts you want to DENY(DROP) for certain
# services but NOT logged.
# TCP/UDP port format (HOST_DENY_xxx_NOLOG):
# "host1,host2~port1,port2 host3,host4~port3,port4 ..."
# IP protocol format (HOST_DENY_IP_NOLOG):
# "host1,host2~proto1,proto2 host3,host4~proto4,proto4 ..."
# ICMP protocol format (HOST_DENY_ICMP_NOLOG):
# "host1 host2 ...."
HOST_DENY_TCP_NOLOG=""
HOST_DENY_UDP_NOLOG=""
HOST_DENY_IP_NOLOG=""
HOST_DENY_ICMP_NOLOG=""
# Put in the following variables which hosts you want to REJECT (instead of
# DROP) for certain TCP/UDP ports.
# TCP/UDP port format (HOST_REJECT_xxx):
# "host1,host2~port1,port2 host3,host4~port3,port4 ..."
HOST_REJECT_TCP=""
HOST_REJECT_UDP=""
# Put in the following variables which hosts you want to REJECT (instead of
# DROP) for certain services but NOT logged.
# TCP/UDP port format (HOST_REJECT_xxx_NOLOG):
# "host1,host2~port1,port2 host3,host4~port3,port4 ..."
HOST_REJECT_TCP_NOLOG=""
HOST_REJECT_UDP_NOLOG=""
# Put in the following variables which services THIS machine is NOT
# permitted to connect TO (remote end-point) via the external (internet)
# interface. For example for blocking IRC (tcp 6666:6669).
DENY_TCP_OUTPUT=""
DENY_UDP_OUTPUT=""
DENY_IP_OUTPUT=""
# Put in the following variables to which hosts THIS machine is NOT
# permitted to connect TO for certain services (remote end-point)
# via the external (internet) interface. In principle you can also
# use this to put your machine in a "virtual-DMZ" by blocking all traffic
# to your local subnet.
# TCP/UDP port format (HOST_DENY_TCP_OUTPUT & HOST_DENY_UDP_OUTPUT):
# "host1,host2~port1,port2 host3,host4~port3,port4 ..."
# IP protocol format (HOST_DENY_IP_OUTPUT):
# "host1,host2~proto1,proto2 host3,host4~proto4,proto4 ..."
HOST_DENY_TCP_OUTPUT=""
HOST_DENY_UDP_OUTPUT=""
HOST_DENY_IP_OUTPUT=""
# Enable (1) to make the default policy allow for IPv4 ICMP (ping) for INET access
# Note: Other ICMP variables apply to both IPv4 and IPv6 unless otherwise noted.
OPEN_ICMP=0
# Disable (0) to make the default policy drop IPv6 ICMPv6 for INET access
# Note: Other ICMP variables apply to both IPv4 and IPv6 unless otherwise noted.
OPEN_ICMPV6=1
# Put in the following variables which ports or IP protocols you want to leave
# open to the whole world.
OPEN_TCP=""
OPEN_UDP=""
OPEN_IP=""
# Put in the following variables the TCP/UDP ports you want to DENY(DROP) for
# everyone (and logged). Also use these variables if you want to log connection
# attempts to these ports from everyone (also trusted/full access hosts).
# In principle you don't need these variables, as everything is already blocked
# (denied) by default, but just exists for consistency.
DENY_TCP=""
DENY_UDP=""
# Put in the following variables which ports you want to DENY(DROP) for
# everyone but NOT logged. This is very useful if you have constant probes on
# the same port(s) over and over again (code red worm) and don't want your logs
# flooded with it.
DENY_TCP_NOLOG=""
DENY_UDP_NOLOG=""
# Put in the following variables the TCP/UDP ports you want to REJECT (instead
# of DROP) for everyone (and logged).
REJECT_TCP=""
REJECT_UDP=""
# Put in the following variables the TCP/UDP ports you want to REJECT (instead
# of DROP) for everyone but NOT logged.
REJECT_TCP_NOLOG=""
REJECT_UDP_NOLOG=""
# Put in the following variable which hosts you want to block (blackhole,
# dropping every packet from the host).
BLOCK_HOSTS=""
# Blocked Hosts are by default blocked in both Inbound and Outbound directions.
# If only Inbound blocking is desired, set to 0 to disable bidirectional blocking.
BLOCK_HOSTS_BIDIRECTIONAL=1
# Uncomment & specify here the location of the file that contains a list of
# hosts(IPs) that should be BLOCKED. IP ranges can (only) be specified as
# w.x.y.z1-z2 (eg. 192.168.1.10-15). Note that the last line of this file
# should always contain a carriage-return (enter)!
#BLOCK_HOSTS_FILE="/etc/arno-iptables-firewall/blocked-hosts"
Service status:
$ 0.status arno-iptables-firewall.service
arno-iptables-firewall.service - A secure stateful firewall for both single and multi-homed machine
Loaded: loaded (/usr/lib/systemd/system/arno-iptables-firewall.service; enabled)
Active: active (exited) since Tue 2013-02-19 12:45:30 CET; 38s ago
Main PID: 7781 (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/arno-iptables-firewall.service
which is a bit confusing as it says 'active' and 'exited' at the same time...
and then I get into my phone through adb shell, and I run:
root@android:/ # su
root@android:/ # netcfg usb0 dhcp
action 'dhcp' failed (Timer expired)
So apparently something is wrong, -
Bridge internet connection problem
Have been using playbook and bridge to my torch since November no problem. Yesterday had browser say my provider did not support the connection to my phone. Next time I connected no problem and no problems using it until this afternoon. No connection, no Internet via playbook but Internet on torch works great. Reinstalled bridge on the torch, no luck.
Any suggestions?Maybe Telus wants you to do a tether plan. Did you do a battery pull for 30 seconds and delete the bridge connection on both before the battery pull and try it again.
Be a Shepard and not an iSheep. -
How to change the NAT type to Open on a Imac using bridged connections
Hey everyone I have a problem. I play xbox live with my friends and i just moved and dont have a wireless adapter anymore. so i have bridged connections with my imac and xbox via ethernet. It works perfectly, but the only problem is that when i connect it say that my NAT type is strict. To play with all my friends i need a open NAT type. Does anyone know how to make the NAT type on the Imac open. And i do have a D-link router model DIR-625. When i called D-link they said to port forward, i did and it still didnt work, they said it must be the fire wall on the mac, microsoft said the same thing, that it might be the fire wall. I checked the fire wall and it said "All Incoming connections are allowed".
I would really much appreciate it if someone helped me. Thank you!Yes, most likely. Microsoft has provided a list of XBox LIVE!-compatible routers. Since the OS X Internet Sharing feature is limited, there is no way to configure port mapping or placing the XBox in a DMZ with it. Typically, you either use a compatible router or configure port mapping/DMZ for non-compatible routers.
-
HP Deskjet 460 wireless printer connection problem
I just replaced my Airport Extreme (pre-n) with a Time Capsule. My HP Deskjet 460 WiFi printer no longer connects through wireless. However, configuring the Time Capsule wireless mode to "802.11g/b only" (i.e. no 802.11n) resolves the connection problem.
Any suggestion on how to get the printer to connect with 802.11n enabled?
Thanks in advance,
- gaelI also have an HP 460wbt and have similarly replaced my old airport base station with the TC. Without any wireless security the printer connected fine - but couldn't get connection using WPA or WEP. I've tried every combination I can - but have gone back to reconnecting the airport base station alongside the TC with bridging to the ADSL netgear modem I use. This seems a bit like overkill but I just can't get the WPA on the printer to work with the WPA personal options of the TC. Have you any ideas on this one?
-
I recently upgraded to 10.4.5. When I used 10.3.9 my wireless connection was fast and dependable. Since my upgrade my connection and download speeds are a tenth of what they were using 10.3.9. Looking through these posts I see lots of people are experiencing connectivity problems with 10.4.5. I am almost ready to back up, reformat and go back to 10.3.9. Maybe somebody has some suggestions. My setup is as follows:
1) Cable modem connected to a Linksys Wireless G Access Point.
2) Third party (Buffalo) Wireless G card in the G4 (worked great with 10.3.9).
3) Unencrypted wireless network (my house is far enough from the neighbors that security isn't really a concern).
4) 2 windows computers connected via ethernet cables to the access point.
5) 1 windows computer with a wireless G USB adapter.
6) Wireless bridge connecting game consoles.
Thanks,
RickI have upgraded my network to 10.4.5 and have not experieced any issues with my ibook and my collegues powerbook which connect wirelessly.
I have a cable modem connected to a linksys wifi router without any issues.
However I am not using 3rd party wireless cards. It would sound like the airport driver that ran your card worked better for you under 10.3.9. Rather than revert your OS back to 10.3.9 have you considered using the older airport driver?
There are 2 airport kernel extensions on my 10.4.5 system
/System/Library/AppleAirport.kext
/System/Library/AppleAirport2.kext
You could use a utility such as pacifist to extract the airport.kexts from your panther disk and replace them in your current OS.
This hack may or may not work, I have not tried it myself. I dont endorse hacking systems other than my own or provide a guarantee it will work it is just an idea. So be sure to make a backup of your original extensions. -
9780 and Playbook bluetooth connection problem
I have never experienced bluetooth connecting problems between my 9780 and Playbook 64 previously ... but for last few days I cannot connect them. I have deleted both devices and re-paired successfully. I have turned both fully off (removed 9780 battery) and still no connection.
I have tested both devices by successfully connecting each of them to other bluetooth devices. They just will not connect to each other for some reason.
The only change was the recent Playbook Software update.
I use the Bridge and Tethering all the time and so need Bluetooth to be working ... thanks for any assistance.
Solved!
Go to Solution.maybe you can uninstall then reinstall the Bridge app on your 9780.
The search box on top-right of this page is your true friend, and the public Knowledge Base too: -
JDBC ODBC bridge connections using 2.1.1
Hi,
I have reviewed a lot of postings related to JDBC and third party drivers and understand how to connect to the packaged drivers such as MySQL and MS SQL Server/Sybase. Where I'm stuck is the reference in the Connections help to JDBC. We have a ODBC system DSN that's not part of the existing JDBC drivers. The help implies it's possible to create a JDBC:ODBC bridge connection and that JDBC:ODBC bridge functionality is part of the JDK therefore should not require additional jar files. However, the JDBC tab is not an available connection type by default. I traced the JDBC ODBC bridge to the rt.jar and tried adding that to the third party extensions but that has not resulted in the JDBC tab becoming available.
Is the JDBC tab only available when using commercial JDBC ODBC bridge drivers ?
For all other connections (DB2, TimesTen, Teradata etc) the help is very specific about which jar files you need and any other requirements but the JDBC section it is unclear how you enable JDBC connectivity.
Thanks
Steven
Edited by: slisint on 14-Jan-2011 18:07We are using the JDBC-ODBC bridge to do a prepared
statement. I have seen other bugs that suggest this
is problematic with older version of JRE, but was
supposedly fixed in later versions.
java.sql.SQLException: General errorIf it is not too late, check the following link:
http://java.sun.com/j2se/1.3/docs/guide/jdbc/getstart/GettingStartedTOC.fm.html
Sections 6.1.3 and 8 (especially tables at the end).
I had the same case, and the problem was that the field in the Oracle database was defined as NUMBER(4), witch is equivalent to INTEGER in JDBC types, and function setInt should be used with INTEGER, instead of setLong.
This is explained in sections I mentioned. -
3 way SLI bridge connection works with only 2 GPU's
NF980=G65 Mobo.
I've read at least one post here a while back about somebody having a problem with a jumpy or flashing screen when in SLI mode with 2 GPU's. He stated that he tried using 2 ribbon connections & that fixed the problem.
Well, I'd like to report that I have 2 GTX 260 GPU's installed in SLI mode & they each have 2 ribbon connections.
This made me wonder if I can use the solid 3 way SLI bridge connection instead of only one ribbon.
Answer= Yes,, it works,, & it seems that I do have a faster transfer rate when I swap pages from one page to another.
Example. When I play my favorite online games I always use Ventrilo or Teamspeak2 VOIP applications to talk to my friends & team mates during game play. If I need to see who is on Ventrilo, I use the windows key to swap or change the screen back & forth from the game screen to the Ventrilo screen. I notice that the transfer rate or the time it takes to change screens is almost instant using the 3 way SLI bridge with my 2 duel ribbon connection GTX 260's. Try it if you have GPU's like this. You'll see. Happy gamingThanks for reporting your findings.
-
Bridge Connection Drops & Wont Reconnect
So, I totally love the PlayBook and think the Bridge concept is awesome!
I've been having a consistent problem where the Bridge connects and works fine. Then when I wake up in the morning there is no Bridge connection and fails to reconnect. I've found if I uninstall Bridge and reinstall there is no issue with connecting then, but I grow tired of this routine. Any ideas? I have a Curve 8520 on v5.0.0.900 and the PlayBook is on 1.0.3.1868 and I appreciate any advice.
Thanks!Do you have more than one Bluetooth device paired with your BlackBerry?
-
Can i use my playbook as a GPS without wifi niether bridge connection?
can i use my playbook as a GPS without wifi niether bridge connection?
please help me!!!
Solved!
Go to Solution.@vanawful, the GPS capability comes from the TI WiLink 7 chip (WL-1283) that provides all the wireless capabilities for the WiFi-only PlayBook.
Although the jury's still out on whether different units may behave differently, so far it appears likely every unit *can* work, under the right conditions, but problems in the software (OS level) or possibly in the chip itself (nobody's saying yet) mean that it's quite unreliable.
There is no need to have WiFi enabled for it, and I've used the GPS frequently now with WiFi off and no nearby hotspots, no tethering (I don't even have a smartphone), and just the GPS running.
If you pick a clear day (i.e. no big rain clouds off to the south, etc), are out in the open without buildings or other things blocking the view of the sky, make certain you are not covering up the lower-right corner of the PlayBook where it appears the GPS antenna is, run the Compass app, and let it sit for 5-10 minutes (if this is your first time using it) so it can find and download ephemeris data from each satellite, you should see it start reporting lat/long positions after that.
If you do this, and it doesn't work, try again. Then try again. Maybe try another time. Preferably do this on different days too, and possibly after a reboot. Yes, it appears to be that flaky sometimes...
I've written my own GPS recording app (no fancy map... just records the readings) and done numerous tests at this point. The readings, when they arrive, are generally exceptionally good. The main problem is getting them to actually arrive and, so far, I've found nothing that can force the issue. Even with my own app, I sometimes have to start it up and leave it alone for some minutes, 4-5 times, before I get the first reading, and there are days I've just given up and moved on. The next day it will simply work. It's largely random.
The three single biggest things you need to remember to get any readings: be outdoors away from big buildings, don't pick a heavily overcast day, and do NOT hold the unit with your right hand covering the bottom right corner (when held in the default landscape orientation with the cameras on top, that is).
Peter Hansen -- (BB10 and dev-related blog posts at http://peterhansen.ca.)
Author of White Noise and Battery Guru for BB10 and for PlayBook | Get more from your battery! -
RG54G2 Wireless Router Internet Connection Problem
Hi,
(apologies for the long message - trying to cover all details - summary: wireless router often drops internet connection)
I recently bought an RG54G2 Wireless Router, a CB54G2 PCMCIA Wireless card and a D-Link GWL-630 PCMCIA Wireless card. In addition to two laptops connected to the wireless router WLAN, I have two PCs (one Win WP Pro SP 1 and one Win98SE) connected to the router via wired LAN. I also have a SurfBoard SB3100 Cable Modem connected to the WAN port (this connects to my ISP - Optusnet (Australia) via DHCP).
The problem I have is that the internet connection is disconnected many times a day (often every few minutes, sometimes an hour or so). I am able to reconnect by resetting the wireless router via the wireless router configuration page. When the internet is disconnected I am still able to access the computers on the LAN/WLAN (via Windows Explorer and Ping), I am also able to ping the router and the Cable Modem, but nothing outside of the cable modem.
Also, when the internet is disconnected the System Status page indicates that the router is still connected to the internet, and the Diagnostics page passes the Test Connection test, though no external pings work.
I did not have this problem when the cable modem was connected directly to the Win98SE PC (and other PCs via ICS).
I have disabled the WLAN and the problem still exists with only the wired LAN.
I have changed numerous settings in the wireless router config page with no success (eg disabling DHCP and setting each IP address, minimising LAN and WLAN speeds to 10 and 11MBps plus others).
I have upgraded the wireless router firmware to R1.0.6.0 (no change to the problem).
Searching on Google I have found several other cases of routers with unstable internet connections (none refering to the MSI routers), but none had solutions that helped my situation (most replies suggested updating the firmware).
Any suggestions of how to make the router internet connection stable?
Thanks,
Mikemaybe this is the FIX 4 wireles router internet connection problem
please let me know if any one fix the problem with this tips
thankz
M. B. Feb 6 2004, 8:20 am hide options
Newsgroups: comp.os.ms-windows.networking.windows
From: "M. B." - Find messages by this author
Date: Fri, 06 Feb 2004 16:20:48 GMT
Local: Fri, Feb 6 2004 8:20 am
Subject: SOLUTION to my router loosing connection to Windows XP
Reply | Reply to Author | Forward | Print | Individual Message | Show original | Report Abuse
I am happy to report that after 8 days of constant battles, reboots, phone
calls, cable pulling, router changing, it seems that I finally have found a
combination that has had me using Verizon DSL account for over 12 hours so
far without any kind of interruptions.
Since so many of you tried giving me comments and suggestions, I felt that
it is necessary for me to post this here so that the next person will not
(hopefully) need to go through this hell as I did!
My original problem was that when after I purchased a D-Link Wireless Router
DI-624, I would get disconnected from Verizon DSL at least once every 2
hours or so. My internet access would "freeze" and then a little popup box
at the bottom right system tray would tell me that the "LAN cable has been
unplugged". After about a minute or so, my internet connection would be
back working This was NEVER happening during the 2+ years I was using my
Westell modem alone (running in router mode).
Please keep in mind: The problem I was having was not wireless related as
it was happening to the desktop computer to which the router/westell was
connected to!
During these last 8 days, I tried: one DI-624 wireless router, two Netgear
614v3 routers and two Linksys WRT54G v.2 routers. In addition, I received a
brand new Westell 2200 modem from Verizon. I also tried about four
different CAT-5 cables. Here is the final outcome:
I have the Linksys WRT54G (version 2) wireless router connected to the
Netgear Fast Ethernet FA310TX network card in Auto-Sense mode (using the
built-in XP drivers, as Netgear told me that there was never a newer
revision released). I have DISABLED the built-in 3Com Gigabit LOM (3C940)
network card (via the ASUS P4C800 Deluxe motherboard BIOS), DISABLED the
Zero Wireless Configuration service, and have put in the IP/Gateway/DNS
address numbers inside my Windows XP Network Connections | LAN setup. My
operating system is Windows XP Pro SP1 and the modem is a Westell 2200
configured as bridge only.
If my situation continues to be stable, I *might* try to go back to the 3Com
built-in card (disable any power management) and then re-enabling the Zero
Wireless Configuration services. But in reality, I am happy with the way
things are and have already spent enough time trying to get my router to
work with Verizon DSL without having it drop connections!
Now, the next step will be setting up the WIRELESS part of this. I don't
even yet have a laptop with me on the premises, but the 802.11g card that I
already have is the D-Link DWL-G650. I hope and assume that this will work
okay with the Linksys...
One thing I must say is that I never realized that how many problems other
users are having. I would have thought that since 802.11x has been around
in the mainstream by now 2+ years, that things would have been much more
"system friendlier". And again, my issues were not even WIRELESS related.
All 3 tech supports were not really helpful, as none of them realized that
the problem is somehow between the router and Windows XP (Ethernet card?)
loosing a connection, which of course results in Verizon DSL loosing the
connection also.
One other comment about the Netgear 614 v.3 router: A number of people have
responded to tell me that they have had this random "router resetting"
happen to them (where the routers behaves as if someone turned the power off
and then back on, and the lights flash) just as if you first turn it on). I
was lucky to witness it myself during one of the "disconnects" that I had.
This was actually the reason why I went back to try the Linksys one more
time. So, I would definitely recommend staying way from this 614 (version
3) model.
Once again - THANK YOU everyone! -
Timeouts and connection problems after 5.1(2) upgrade
AIM/chat and some other programs are having timeout/connection problems after upgrade to 5.1(2). I am using S241 also. The connection problems stopped when the IPS was set to bypass. Rebuilt IPS and left sigs at default settings and problem is still happening. I am not seeing any of the IPs that are having the problem in the Event Viewer or on the Events in the IDM.
Any known issues with the 5.1(2) that would cause this type of problem?I don't know specifically, but I did notice that 5.1(3) was released today.
-
Hi, i am having trouble with my mac mail account, i cannot send or receive any emails because of the server connection problems. Message says it could not be connected to SMTP server. Thanks in advance for your help.
Hello Sue,
I have an iPad 3, iPad Mini and iPhone 5S and they are all sluggish on capitalisation using shift keys. I hope that Apple will solve the problem because it is driving me crazy.
I find using a Microsoft Surface and Windows 8 phone, which I also have, work as well as all the ios devices before the ios 7 upgrade.
It has something to do with the length of time that you need to hold the shift key down. The shift key needs to be held longer than the letter key for the capitalisation to work. For some reason, this is a major change in the way we have learnt to touch type on computers. I am having to relearn how to type!
Michael -
RFC Receiver adpater Connection problem , Help us to solve ?
Hi Friends ,
Our scenarilo is Mail to RFC. It was running fine. In RFC Receiver adapter i have given <b>Maximium connection property to 1</b> .
While multiple set data passed to rfc will connection problem will come ?
Most data not uploaded . I am getting the following error.
<b> If i set max connection to 5 . It is 5 times or more than that it is pusing the data .</b>
i am getting the following error <b>while i set the Max connection to 1 .</b> . <b>Any other place i need to change configuration ?</b>
<i><b> - Error: 2007-09-24 10:51:22 GMT-05:30: Message processed for interface YRFC_EXT_WARR: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: resource error: could not get a client from JCO.Pool: com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Connection pool RfcClient[CC_EXTE_WAREN_2W_RFC_RECEIVER]e7fa21f86ec535e883636c0beffc0f0c is exhausted. The current pool size limit (max connections) is 1 connections.</b></i>
Please give the description . I have referred many likns . Help us to solve this problem .
Regards.,
V.Rangarajan<b></b>
Message was edited by:
ranga rajanHi,
Have a look at this.This will help you.
1.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f3f93ee7-0c01-0010-2593-d7c28b5377c2
2. https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3103eb90-0201-0010-71af-be6f4a6f61d1
Regards,
Akshay Jamgaonkar.
Reward points if find useful.
Message was edited by:
Akshay Jamgaonkar
Maybe you are looking for
-
Java.lang.UnsatisfiedLinkError.Can't find dependent libraries
Hello, I call in an applet a library "ezmodJava.dll" in order to execute a native method. It works very well in my computer (Windows 98). I've put "ezmodJava.dll" and a dependent library "ezmod.dll" in directory C:\Windows. That works very well. Now
-
Need advice on how to make this all work together
Not really sure where to post this, so I decided to post here. I'm trying to streamline devices and move more into the cloud. Because of some weird network issues it is complicated. Currently I have a MacMini at home. I am a teacher so office-ty
-
How do I successfully merge MXF and DV files in a sequence?
I have a Panasonic with a P2 card (and DV film). I have a reader. I have successfully transferred all the files to my computer, and imported them into PP6, no problem. My only issue is this: if I want to consolidate the MXF files with the camera's
-
How to unistall x code at mac pro
evening , how to remove x code at mac pro 13". thaks
-
General Tips for Success with ePrint
I just wanted to impart some of my knowledge on sending successful ePrint Jobs to the printer. Keeping the following items in mind when using ePrint will improve your success rates of sending jobs to the printer. ePrint Supported File Types are the F