Re: Linksys hacking?

From: here_we_go_again (netops@captainbeer.com)
Date: 01/23/02 

From: "here_we_go_again" <netops@captainbeer.com>
Date: Wed, 23 Jan 2002 18:48:12 +0000 (UTC)

i must be doing something wrong when typing.

yes, i fully understand the concept of connecting through port 80 on the
LAN side. I also fully understand that this is done throu your "web
browser" on the standard HTTP port, "TCP" port "80". Now, i've looked
through my last few posts and did see EVERY SINGLE TIME, i specified
UDP... NOT TCP. UDP.

UDP. <- Read this part... cause that's what i'm talking about.

TCP = NO
UDP = YES

did everyone catch that? here, i'll do it again... watch closely cause
it goes by fast!

TCP = NO
UDP = YES

not to beat a dead horse or anything but....

LAN side management = 80/TCP connection via web browser
WAN side DOS = 80/UDP (do you see the difference now? one side
is mangement, the other side just smacks the box down and makes it cry)

Got it? yes?

I can look back through my notes and find the exact firmware version for
this crappy box so you can test it out yourself... or i'd be happy to
even go one step furth and put the box out on the internet with the code
on it... WAN side locked down and would invite you to use any UDP
flooding tool and you can watch the thing blow itself up (its actually
kinda fun!).

::goodness:: would you like fries with that?

"Lars M. Hansen" <badnews@hansenonline.net> wrote in message
news:v69t4u8o3n55se9t2cg3ebok3en01cvq8d@4ax.com...

> On Wed, 23 Jan 2002 09:41:26 GMT, ßill spoketh
>
> >On Wed, 23 Jan 2002 03:41:12 +0000 (UTC), "linksys_stuff_has_no_pants"
> ><netops@captainbeer.com> wrote:
> >
> >>yeah, that's what you would think huh? a) even from the WAN if you're
> >>doing HTTP management, why would the box listen on port 80/UDP? b) why
> >>when you turn off WAN mgt does the box still listen to 80/UDP?
> >
> >a) you misssed it, it listens on 80 oon the LAN. It does not listen
> >on the WAN unless you have remote management enabled. The open port 80
> >is on the lan side only by default.
>
> Actually, it listens ONLY on port 80 on the LAN side. Remote Management
> can be enabled to allow management on the WAN side, but that's on port
> 8080. The only reason why it might appear from the LAN side that you can
> connect to the WAN side for management is the loopback feature. People
> actually on the WAN side cannot connect to port 80 on the Linksys router
> (with or without Remote Management) and get anywhere...
>
>
> Lars M. Hansen
> http://www.hansenonline.net
> (replace 'badnews' with 'lars' in e-mail address) 

-- 
Posted via Mailgate.ORG Server - http://www.Mailgate.ORG

Relevant Pages

  • Re: Current status?
    ... The highest-priority MX record is the WAN ... which gets forwarded to the cluster alias. ... On my ROUTER, of course, not on my LAN. ... should be allowed to communicate with the outside world over port 25. ...
    (comp.os.vms)
  • Re: sonicwall port configuration
    ... It sounds as if you wish to keep the world out of your LAN... ... This blocks all traffic from the WAN to your LAN. ... ignore the port scans that you see logged. ... adding the rule "Deny File Transfer (FTP) LAN to WAN ...
    (comp.security.firewalls)
  • RE: Syntax to block TCP/UDP port 135-139 on D-Link NAT?
    ... Allow Allow to Ping WAN port WAN,* LAN,192.168.0.1 ICMP,8 ... By default dlink routers block all traffic from *,* to the LAN ... The Firewall rules control traffic between the lan and wan. ...
    (microsoft.public.windowsxp.security_admin)
  • Changing the way IIS answers to PASV commands?
    ... LAN IP address of server is 192.168.1.5 ... when I connect through the WAN (from 192.168.1.2 to ... Secondly, port 1024-4000~ are used for other things on my network, and I ... one, it didn't have an effect on the PASV replies, and two, that's just the ...
    (microsoft.public.inetserver.iis.ftp)
  • Re: Linksys hacking?
    ... >>on the WAN unless you have remote management enabled. ... it listens ONLY on port 80 on the LAN side. ...
    (comp.security.firewalls)