TOPIC: Tomato Users (Seeking advice)

Salamat boss jhezzy.

Pero yung list ng CVEs na yung ang mga affected ay cctv at dvrs. IOTs will unlikely to be secured anyway. Probable reasons are due to their limited computing power (which renders them unable to process secure crypto); and being half-baked products.

Yung binabanggit ni WiredIdeas ay yung tomato-flashed devices being vulnerable via DHCP requests sent by wireless clients (IOTs or otherwise).

homer_simpson wrote: Pasensya na, medyo naco-confuse lang ako. As per your previous reply, ang issue na ito affects wireless LAN. Tapos concern ka na pwede ma-trigger ang vuln via DHCP packets. Well, kung authenticated at associated ang isang wireless LAN in the first place, getting an IP is less of your concern. They can just assign any static IP within your range and they're good to go. Ang katapat nito sa wired LAN, is they are able to physically plug in their ethernet cable sa switch. The mere fact that they are able to authenticate and associate with your Access Point should be your immediate concern.

And they don't need to go anywhere, they just need to go direct to your router interface and trigger the said vuln.

Unusual spike sa traffic? DHCP packets are really, really small and not enough to cause any spike at all.

Pasensya na, gusto ko lang din malinawan dito.

Actually parang na confuse ka nga, ganto kasi yun, ang chinese made cctv camera can work in two ways wireless and wired. Eto ata ang di ko na expound. Ang siste kasi yung wifi cctv camera eh nakakabit sa network through wired lan cable (so, di ginamit ang wifi feature nya) So ang setting is like this, in order for that camera to start it needs to get an IP address which at that time is supplied via dhcp.

So, what i did is assign all client PC's their own corresponding static ip add then disable dhcp then walla! pag tingin ko sa logs waley na sila hehe

WiredIdeas wrote:

homer_simpson wrote: Pasensya na, medyo naco-confuse lang ako. As per your previous reply, ang issue na ito affects wireless LAN. Tapos concern ka na pwede ma-trigger ang vuln via DHCP packets. Well, kung authenticated at associated ang isang wireless LAN in the first place, getting an IP is less of your concern. They can just assign any static IP within your range and they're good to go. Ang katapat nito sa wired LAN, is they are able to physically plug in their ethernet cable sa switch. The mere fact that they are able to authenticate and associate with your Access Point should be your immediate concern.

And they don't need to go anywhere, they just need to go direct to your router interface and trigger the said vuln.

Unusual spike sa traffic? DHCP packets are really, really small and not enough to cause any spike at all.

Pasensya na, gusto ko lang din malinawan dito.

Actually parang na confuse ka nga, ganto kasi yun, ang chinese made cctv camera can work in two ways wireless and wired. Eto ata ang di ko na expound. Ang siste kasi yung wifi cctv camera eh nakakabit sa network through wired lan cable (so, di ginamit ang wifi feature nya) So ang setting is like this, in order for that camera to start it needs to get an IP address which at that time is supplied via dhcp.

So, what i did is assign all client PC's their own corresponding static ip add then disable dhcp then walla! pag tingin ko sa logs waley na sila hehe

Wired or wireless, irrelevant yun. Kasi either way, a client acquires an IP either via DHCP or manual method (katulad ng ginagawa mo). Ngayun, kung vuln ang tomato-flashed router sa DHCP traffic, irrelevant din kung ang client mo ay cctv o laptop o smartphone o kahit anong networked device.

WiredIdeas wrote: Ang siste kasi yung wifi cctv camera eh nakakabit sa network through wired lan cable (so, di ginamit ang wifi feature nya) So ang setting is like this, in order for that camera to start it needs to get an IP address which at that time is supplied via dhcp.

sa tingin mo hindi aplikable sa wired LAN, considering that wired clients also obtain IP via DHCP? Hmm...

WiredIdeas wrote: ... ang chinese made cctv camera can work in two ways wireless and wired.

kelangan paba banggitin yan? It's already implied, isn't it?.

WiredIdeas wrote: So, what i did is assign all client PC's their own corresponding static ip add then disable dhcp then walla! pag tingin ko sa logs waley na sila hehe

Natural, tin-turnoff mo yung dhcp client by statically assigning IP. Walang sorpresa dyan.

By the way, wala ako makita CVE na related sa tomato firmware na vulnerable sa dhcp.

^


Relax lang bossing ok lang ang tomato :) Wala kang makita baka ako palang naka discover nito or i'm just hallucinating, either way walang problema basta putting out the info lang para kung ma experience ng ibang users may reference na sila.

naka fiber 100Mbps na po ako, kaso 20 mbps lang nakukuha kapag dumaan kay tomato chinese 5354u.
anu-ano pong router model ang pwede pamalit? yung pwede pa din po and dual wan, dalawa ISP pa din po kasi ang ikakabit ko. salamat po.

pwede po MT, linksys,cisco,asus

oracle wrote: naka fiber 100Mbps na po ako, kaso 20 mbps lang nakukuha kapag dumaan kay tomato chinese 5354u.
anu-ano pong router model ang pwede pamalit? yung pwede pa din po and dual wan, dalawa ISP pa din po kasi ang ikakabit ko. salamat po.

Tenda N60 po nabasa ko dito, ano po alternatives kapag walang available na N60? specific brand and model po sana.

meatloaf0518 wrote: ^
HIRAP MAG HANAP NG n60 Sir xD
\

nakakita ako online isa piraso available. binili ko na sana ok pag deliver.

prone sa overheat ang N60.

Sumudoy wrote: prone sa overheat ang N60.

ay ganun po ba, sayang na order ko na haha. ano po ba magandang pang dual wan tomato, for 100Mbps internet fiber