I have a local area network, What can I do control users with pppoe user id and password. I have up to 160 users on my network, I am using also isa 2004, where it is possible to control users with pppoe dialup.any other os or other control software?

Dani AI

Generated

Short answer: run a PPPoE access concentrator (server) on the gateway and authenticate/account with a RADIUS backend. That gives per-username login, per-session IP assignment, accounting, and the hooks to apply per-user limits or profiles. Remote-control tools like TeamViewer only let you manage a machine — they do not provide network-level PPPoE authentication or accounting. (freeradius.com)

Two practical stacks to consider. Option A (open source): a Linux box running rp-pppoe/pppd as the PPPoE AC and FreeRADIUS for AAA and accounting; that plugs into a SQL/LDAP user store and lets you use RADIUS attributes to push IPs, filters, or bandwidth settings. Option B (appliance/router): use a router OS with a built-in PPPoE server (MikroTik, Cisco, Juniper) and point it at FreeRADIUS — easier to manage and includes built-in per-user queues and session controls. (manpages.debian.org)

Minimal checklist to implement (keeps your ISA/TMG proxy role separate):

  1. build the PPPoE AC on the gateway; 2) configure FreeRADIUS (or commercial AAA) as the authentication + accounting store; 3) create an IP pool or assign per-user IPs; 4) integrate NAT/firewall or proxy for Internet egress; 5) enforce bandwidth via router queues or RADIUS attributes. Watch MTU/MRU (PPPoE normally reduces usable MTU to 1492 unless negotiated) and enable MSS clamping on the firewall. Test auth with radtest and debug pppd/radius logs. (rfc-editor.org)

Troubleshooting & sizing tips: enable debug on pppd and FreeRADIUS (-X) to see Access-Request / Access-Accept flows; verify RADIUS shared secret and CHAP/PAP modes; check address-pool size (you can run out of remote addresses); and size CPU/RAM for the number of concurrent PPP sessions (router docs show per-session memory/CPU guidance). For ~160 users a small dedicated gateway or a midrange router with PPPoE AC is usually preferable to a general-purpose desktop. (manpages.debian.org)

If endpoint dialers are impractical, consider captive-portal or proxy-auth for HTTP access instead — but those are separate architectures from PPPoE and trade lower-layer control for easier client-side deployment.

Recommended Answers

All 3 Replies

If you want to control user you can always use a remote management software like Team viewer.

I am using also isa 2004, I like to share internet through my server to my clients, i have a mini local area network. I manage it with isa server 2004,and there are no easy way to provide internet to my clients, suddenly I saw a network who using client side only pppoe dialer and use internet like a isp client, what he can use server side.

So what you want now, is to able to share internet access to your clients so they are able to access internet. Am i right so far?

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.