Is there any firewall rule on the router/BSD Server for traffic coming
from the internet? Normally it is blocked for security reason. If yes,
pls open SNMP UDP 161/162. To troubleshoot this further, can you turn on
the logging or tcpdump to see  if SNMP is coming in?

Alex
sB Tech Support
 
 


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Roger Howard
Sent: Thursday, July 24, 2003 10:40 PM
To: '[EMAIL PROTECTED]'
Subject: Re: [smartBridges] Can't log in...


Default gateway is set correctly to the IP of the T1 router. Primary
port is set to wireless on the client devices and Ethernet on the access
point.

I can ping the devices just fine from over the internet. Just can't log
in using simple monitor.

Thanks,
Roger
----- Original Message -----
From: "Billy Huddleston" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 24, 2003 8:43 AM
Subject: Re: [smartBridges] Can't log in...


> Be sure you have the gateway set on the unit, and have the primary 
> DHCP
port
> set to WIRELESS regardless if your using DHCP or static IP's
>
>
>
> ----- Original Message -----
> From: "Roger Howard" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, July 24, 2003 8:22 AM
> Subject: Re: [smartBridges] Can't log in...
>
>
> > Thanks, that's good to know... but my main problem is that I can't 
> > log
> into
> > the client radios unless I'm on the LAN.
> >
> > Anyone?
> >
> > Thanks
> > ----- Original Message -----
> > From: "Del Thompson" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, July 24, 2003 7:06 AM
> > Subject: RE: [smartBridges] Can't log in...
> >
> >
> > > Roger,
> > > If you are on the the same AP as the clients you are trying to log
into,
> > > that is stopped by disabling the client to client communications 
> > > on
the
> > AP.
> > > If this is the case, you should be able to log into clients on 
> > > another
> AP
> > > provided that the routing is correct.
> > > You are correct that the client to client traffice will be sent to

> > > the router.  The issue as I see it, is that the router will not 
> > > forward IP traffic back through the same interface that it 
> > > received that traffic
> from
> > > (provided it came fromt the same subnet).
> > > We have the same situation but realized that the client to client
> traffic
> > on
> > > the same AP would be blocked during the design phase.  To minimize

> > > the impact that this would have, we force all of our business 
> > > customers to
> use
> > a
> > > router provided by us which is on a seperate subnet.  That way the

> > > residential clients and the business clients on a particular AP 
> > > can
> still
> > > communicate with each other.
> > > Hope this helps.
> > > Del
> > >
> > > -----Original Message-----
> > > From: Roger Howard [mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, July 23, 2003 9:33 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: [smartBridges] Can't log in...
> > >
> > >
> > > I've been trying to figure out why I can't log into my 
> > > smartbridges
> > devices
> > > from over the Internet. Let's take the aPPO as an example. It has 
> > > a
> public
> > > IP addresses, correct default gateway and subnet mask, I can ping 
> > > it
> fine,
> > > Configuration port is set to both wired and wireless, Primary port

> > > is
> set
> > to
> > > ethernet side.
> > >
> > > Network looks like this
> > >
> > > Me.... Internet.....T1router....crossover cable....FreeBSD server
> > configured
> > > as bridge.....switch.....APPO... wireless....airBridges
> > >
> > > I can't log into the APPO or any of the airBridges.
> > >
> > > Another thing I noticed that might be relevant... when I disable
client
> to
> > > client communications in the APPO, I understood it would make it 
> > > pass
> the
> > > data bound for other clients on the LAN back through the FreeBSD
server
> to
> > > the T1 router, which would then direct the traffic back onto the 
> > > local network and back out of the APPO. This doesn't work. Clients

> > > can not
see
> > > each other when set up like this.
> > >
> > > Does anyone have any idea what might be wrong with my setup? The 
> > > T1
> router
> > > is a managed router by ACC. I have a feeling the problem may be 
> > > with
my
> > > freeBSD bridge. But what, because it passes normal traffic just 
> > > fine.
> It's
> > > there primarily for running dummynet and bandwidth throttling.
> > >
> > > Any tips?
> > >
> > > Thanks,
> > > Roger
> > >
> > > The PART-15.ORG smartBridges Discussion List
> > > To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe 
> > > smartBridges <yournickname> To Remove: mailto:[EMAIL PROTECTED]

> > > (in the body type unsubscribe
> > > smartBridges)
> > > Archives: http://archives.part-15.org
> > > The PART-15.ORG smartBridges Discussion List
> > > To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe
> > smartBridges <yournickname>
> > > To Remove: mailto:[EMAIL PROTECTED] (in the body type 
> > > unsubscribe
> > smartBridges)
> > > Archives: http://archives.part-15.org
> >
> > The PART-15.ORG smartBridges Discussion List
> > To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe
> smartBridges <yournickname>
> > To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe
> smartBridges)
> > Archives: http://archives.part-15.org
> >
>
> The PART-15.ORG smartBridges Discussion List
> To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe
smartBridges <yournickname>
> To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe
smartBridges)
> Archives: http://archives.part-15.org

The PART-15.ORG smartBridges Discussion List
To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe
smartBridges <yournickname> To Remove: mailto:[EMAIL PROTECTED] (in
the body type unsubscribe smartBridges)
Archives: http://archives.part-15.org  

The PART-15.ORG smartBridges Discussion List
To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges 
<yournickname>
To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges)
Archives: http://archives.part-15.org  

Reply via email to