Default Route on a Netgear DG834GT

to0kenZA

New member
Has anyone here every tried putting a default route on one of these bad boys?

I tried, but it doesn't support it. Lol?

So basically what I was trying do do is this:

IS static router --> Juniper5GT --> DG384GT

The Netgear must be setup up with Wireless and DHCP. Then you add a static default route (0.0.0.0 0.0.0.0 gateway) on the netgear, but when you put in those figures under static routes, it just says "Incorrect IP Address, Incorrect Subnet mask specified".

So I take it these things just doesn't have the functionality? You can only add static routes to other networks, but not a default route.

Has anyone managed this?
 
Why you routing through a Juniper gateway??? :confused:

what subnet are you using as well?? and with that static route are you trying to attempt some form of IPsec tunneling??

EDIT: Nevermind I forgot thats a firewall...
 
Last edited:
Why you routing through a Juniper gateway??? :confused:

what subnet are you using as well?? and with that static route are you trying to attempt some form of IPsec tunneling??

EDIT: Nevermind I forgot thats a firewall...

The IPSEC tunneling will be through the Juniper, that's why it needs to be the gateway or at least have a default route pointing to it so that traffic can route through IT instead of the stupid netgear. :mad: I can't believe this Netgear is so noob!

Anyhow, the network ranges and subnets are not applicable here. It's just a default route. You know, like on a Cisco?

ip route 0.0.0.0 0.0.0.0 192.168.0.254

Anyhow, screw it. I think I just figured out the thing can't do it. Try google "Can you set a default route on a Netgear DG834GT" and not one result comes up with the keywords "default route".

I had to resort giving the wireless devices static IPs, can you believe it :rolleyes:
 
The IPSEC tunneling will be through the Juniper, that's why it needs to be the gateway or at least have a default route pointing to it so that traffic can route through IT instead of the stupid netgear. :mad: I can't believe this Netgear is so noob!

Anyhow, the network ranges and subnets are not applicable here. It's just a default route. You know, like on a Cisco?

ip route 0.0.0.0 0.0.0.0 192.168.0.254

Anyhow, screw it. I think I just figured out the thing can't do it. Try google "Can you set a default route on a Netgear DG834GT" and not one result comes up with the keywords "default route".

I had to resort giving the wireless devices static IPs, can you believe it :rolleyes:


I actually tried IPsec tunneling using a draytek router and a cisco ASA and what a Fail also tried to do the default route method but its the rules that are entirely different, in the end we used a draytek firewall to setup rules to the cisco firewall and then creating a dmz just for the IPsec tunnels, between the draytek routers and the draytek firewall...

Apparently these companies hate it when people use other products, thats why the rules are setup differently to fsck you over and give you endless hell....
 
I actually tried IPsec tunneling using a draytek router and a cisco ASA and what a Fail also tried to do the default route method but its the rules that are entirely different, in the end we used a draytek firewall to setup rules to the cisco firewall and then creating a dmz just for the IPsec tunnels, between the draytek routers and the draytek firewall...

Apparently these companies hate it when people use other products, thats why the rules are setup differently to fsck you over and give you endless hell....

Geez dude, that sounds like you guys made it a bit more complicated than it should be lol.

I just can't believe this stupid thing cannot have a default route, I mean fsck me- it's a freakin' router?! Any router should have that capability. Oh and as for the rules being different, you must check this fail out, bru! You can't set the static route's metric to 0. A static route's default metric is always 0, now this thing wants me to set it to 2 as a minimum. Wtf?

See dude, this is the part where I say take out this crap and get the right equipment. I guess you get what you pay for. (Btw, wasn't my decision to use this thing :p)
 
Geez dude, that sounds like you guys made it a bit more complicated than it should be lol.

I just can't believe this stupid thing cannot have a default route, I mean fsck me- it's a freakin' router?! Any router should have that capability. Oh and as for the rules being different, you must check this fail out, bru! You can't set the static route's metric to 0. A static route's default metric is always 0, now this thing wants me to set it to 2 as a minimum. Wtf?

See dude, this is the part where I say take out this crap and get the right equipment. I guess you get what you pay for. (Btw, wasn't my decision to use this thing :p)

Actually we didn't make it difficult at all, we managed to setup a bypass on the draytek but the minute the failsafe kicked into 3G our firewall could see the router but the router wasn't able to see headoffice...

Yeh you know what, just reprogram the fscking thing lmao :p

all routers should have default metrics on 0, i dunno why netgear would be any different :confused:
 
Lol I don't know dude... :/ It's really silly IMO!

Actually we didn't make it difficult at all, we managed to setup a bypass on the draytek but the minute the failsafe kicked into 3G our firewall could see the router but the router wasn't able to see headoffice..

That's why I LOVE Juniper VPNs dude. :) As long as the router has break-out, the VPN is up :D
 
Lol I don't know dude... :/ It's really silly IMO!



That's why I LOVE Juniper VPNs dude. :) As long as the router has break-out, the VPN is up :D
sjoe so they make it quite plain and simple... I guess I love cisco because as long as it has web interfaces then I'm sorted, I HATE typing commands with a passion...
 
sjoe so they make it quite plain and simple... I guess I love cisco because as long as it has web interfaces then I'm sorted, I HATE typing commands with a passion...

Well it's not really simple, but simple in practise :D



Omg dude I'm being a complete idiot though. I just figured it out! I was thinking too technical, sigh, while forgetting about the basic principles..I just need to put the Netgear in bridge, have it broadcast a wireless network. Give it an IP on the network range and have the Juniper issue DHCP. The Juniper's DHCP server will respond to any DCHP requests originating from that network. Sigh, now I look like a chop. :/ But it's still lame that you cannot set up a static route! :p

Issue solved.
 
Well it's not really simple, but simple in practise :D



Omg dude I'm being a complete idiot though. I just figured it out! I was thinking too technical, sigh, while forgetting about the basic principles..I just need to put the Netgear in bridge, have it broadcast a wireless network. Give it an IP on the network range and have the Juniper issue DHCP. The Juniper's DHCP server will respond to any DCHP requests originating from that network. Sigh, now I look like a chop. :/ But it's still lame that you cannot set up a static route! :p

Issue solved.

loooooooooooooooooooooooooool you see talking about it helps :p
 
Back
Top