goat0brain0balls0
Newbie
I am a new user in airtel. Earlier I was into sify and had Netgear WGR614v5 router working perfectly fine with . Now I want to configure the router for airtel broadband . Can anyone point me as to how to do it ? any help would be appreciated.
As mentioned in the thread, I had the installation guy change the IP of the beetel Airtel modem to 192.168.1.5 so that there is no IP conflict. But still when I try to configure the netgear wireless router , I am not able to connect to it
IP's of the different CPE (customer premise equipment)? beetel and netgear? check if they are in the same subnet. i would recommend subnet calculator. its a nice tool for those who always gets stuck with IP addressing. and a few more things i would check again and again if i had to put my feet in your shoes (feet size and shoe size does matter still and inspite) #1. ip address of the CPE #2. subnet #3. gateway #4. broadcast #5. cable (if any used i.e. wireless) #6. get a first aid book on IP addressing. most of troubles we face daily is mormally happening trillions of time and as per history records same mistakes tend to occur again and again. relax and check all these options first. before you think of fixing it.
p.s. wireless is a tricky thing, as no wires are used to traceback issues unlike wired n/w. so give us debuggers aka bugs as much info relating to issues as you can. perform the basic checks. and make an entry. as we are human we will make similar mistakes again and again, we are programmed like that.
PC/Notebook IP address must not be same as beetel and netgear, beetel and netgear IP addres should also not be the same. disable PAT (port address translation if enabled/present)
check for subnet screw ups. like if you put/pool CPE into different subnets? then route them properly routing is imp here. w/o routes no destination is visible.
broadcast any subnet's x.x.x.255 is a broadcast and must not be used and also sometime used as a multicast in multihome env.
gateway must be unique. dont restrict the gateway from entering Internet and dont block 127 series in blocked IP in firewall. leave the gateway as transparent as possible.
when wired? check for reachability of the gateway and some Internet host and repeat the same with wireless.
LASTLY? if you screw up? backtrace it, go back in time and think which step onwards you started to spit swears wide open to all and yourself. ;-) good luck. provide info enough to troubleshoot, limited info leads to maximum confusion.
As mentioned in the thread, I had the installation guy change the IP of the beetel Airtel modem to 192.168.1.5 so that there is no IP conflict. But still when I try to configure the netgear wireless router , I am not able to connect to it
IP's of the different CPE (customer premise equipment)? beetel and netgear? check if they are in the same subnet. i would recommend subnet calculator. its a nice tool for those who always gets stuck with IP addressing. and a few more things i would check again and again if i had to put my feet in your shoes (feet size and shoe size does matter still and inspite) #1. ip address of the CPE #2. subnet #3. gateway #4. broadcast #5. cable (if any used i.e. wireless) #6. get a first aid book on IP addressing. most of troubles we face daily is mormally happening trillions of time and as per history records same mistakes tend to occur again and again. relax and check all these options first. before you think of fixing it.
p.s. wireless is a tricky thing, as no wires are used to traceback issues unlike wired n/w. so give us debuggers aka bugs as much info relating to issues as you can. perform the basic checks. and make an entry. as we are human we will make similar mistakes again and again, we are programmed like that.
PC/Notebook IP address must not be same as beetel and netgear, beetel and netgear IP addres should also not be the same. disable PAT (port address translation if enabled/present)
check for subnet screw ups. like if you put/pool CPE into different subnets? then route them properly routing is imp here. w/o routes no destination is visible.
broadcast any subnet's x.x.x.255 is a broadcast and must not be used and also sometime used as a multicast in multihome env.
gateway must be unique. dont restrict the gateway from entering Internet and dont block 127 series in blocked IP in firewall. leave the gateway as transparent as possible.
when wired? check for reachability of the gateway and some Internet host and repeat the same with wireless.
LASTLY? if you screw up? backtrace it, go back in time and think which step onwards you started to spit swears wide open to all and yourself. ;-) good luck. provide info enough to troubleshoot, limited info leads to maximum confusion.
