Untangle interface confusion

[bilbo]

Hi all,

I'm new to Untangle and hope to replace our existing setup.

I've been playing around with Untangle and had it working OK in bridge mode but trying to get it working as a router seems to be hard work.
I've searched though the Wiki and the forums but I seem to be missing something quite fundamental as I can't get it to work, although to be fair, some of the Wiki entries either state the obvious or tell you virtually nothing at all.

In the current setup we have the modem (x.x.x.0) > router/firewall (external IP x.x.x.6 / internal IP 192.168.0.1) > LAN

I have tried modem (x.x.x.0) on the external interface and set this in UT to x.x.x.6 and then set the internal interface to 192.168.0.1
However this does not work.

Now I figure I'm making some pretty fundamentally stupid mistake somewhere but I can't see it!

Any help, pointers or documentation appreciated!

Bill

[sky-knight]

If you have documented a working router with x.x.x.6 as it's WAN IP x.x.x.0 as it's gateway and an internal IP of 192.168.0.1.

All that you need is to install UT in router mode assign those IP addresses to the appropriate fields and it starts to work.

Now all that said if your "modem" is the cable variety you need to know that cable networks often do mac filtration to control what device gets an IP address. This prevents you from setting up more computers than what you pay for.

Generally speaking power cycling the cable modem after it is connected to UT should clear the error. If it doesn't you need to call your ISP and get them to manually clear the arp cache on your node. Heck in some cases you have to call them and manually give them the MAC address of your WAN interface.

[bilbo]

Hi Sky-Knight,

Thanks for the reply!

If you have documented a working router with x.x.x.6 as it's WAN IP x.x.x.0 as it's gateway and an internal IP of 192.168.0.1.
All that you need is to install UT in router mode assign those IP addresses to the appropriate fields and it starts to work.


I'm confident that this is what I've done but it just won't connect to the internet!
The modem is ADSL not cable but I can't see this would affect anyhing? I don't believe any MAC filtering is going on and as for clearing the ARP cache I can tell you what glorious British Telecom would say to that...

Just to clarfy...
Modem is set as x.x.x.0 > UT external interface static x.x.x.6/gateway x.x.x.0 UT internal interface static 192.168.10.1? Have i got this right?

Do I need to set the modem to bridge?

I'm going to give this one last stab tomorrow...

Bill

[mdh]

Normally an address like x.x.x.0 means that you are referring to a subnet that goes from x.x.x.1 through x.x.x.255. I would bet that it should be x.x.x.1 instead. Also make sure that the netmask is set properly. A good address with a bad netmask equals no connection.

Also, if you had it working in bridge mode but its not working in router mode, there is a question of whether you are trying to make contact with the outside world from a browser on the Untangle console (click on HELP from any Untangle window to bring one up), or from a computer behind Untangle. Your modem likely has a public external address and a private internal address, meaning that you have two routers in a row. Two routers equals confusion for the uninitiated.

[sky-knight]

Yes, if you have adsl involved I would stick with a bridge. Unless that craptiontech or whatever has magically grown the ability to be a bridge itself. Double NAT is not for the faint in heart.

[bilbo]

Thanks all for the replies.

I believe I have the right IP's as these are laid out by my ISP. ..0 modem, ..6 router and ..1, ..2, ..3, ..4, ..5 static IP's. I figure that the modem (Zyxel 660R) isn't bridging properly or is trying to do something too clever.

Based on this and your input I think my best option is bridged mode.

Onward and upward!

Bill

[sky-knight]

My kingdom for a DSL router that actually DMZ's, port forwards, or heaven help me bridges properly. Ever since the Cisco 678's died out I've been forced to all but abandon DSL as a viable Internet connection because of this.