Smoothwall/IpCop NTL Cable for my NTL servic

p

Hey,

trying ot setup a home gateway for my NTL cable modem service.

I setup smoothwall & IPCop but it wouldn't connect to the net, although the home network was fine.

Anyone else have problems like that and know how to fix it?

Also, is there any alternative/better solutions?

Thanks,

- Kevin

p

c'mon people.

Surely someone's used it or have some help.

Even osmeone telling me they got it working woul dbe useful, cause then I might be able to figure out if it's a problem with my setup.

MiCr0

care to give any info?
logs?
tracert?

p

Originally posted by MiCr0
care to give any info?
logs?
tracert?

logs, tracert you say?

*scratches head*

- Kevin

spongebob

seeing as you run unix.

log in to unix box
run csh

Run the 2 following commands (should be the same result)

traceroute 192.125.2.240
traceroute ns.iol.ie

paste the traceroute results back in here

MiCr0

also
netstat -rn
cat /etc/hosts
ifconfig -a

p

Don't have change to do that just yet since I have to hook stuff back up.

But from what I was doing, the cable modem nic wasn't getting allocated an IP address at all.

It wasn't even getting the 169.* ones
the ip and netmask were still set as 0.0.0.0

I'll post up the other stuff asap.


- Kevin

MiCr0

what sort of network layout have you got?

Inspector Gadget

...but those 169.* addresses, they were 169.254.*, weren't they?

TCP/IP addresses reserved for 'private' networks are:

10.0.0.0 to 10.255.255.255
172.16.0.0 to 172.31.255.255
192.168.0.0 to 192.168.255.255
and as of July 2001
169.254.0.0 to 169.254.255.255

...as far as I know, 192.168.* is the most common IP range assigned to (small) internal networks, especially those using DHCP (for example, Windows Internet Connection Sharing uses this range by default). Perhaps some of your hardware or software is configured to use this range instead of 169.254.*, causing netmask woes?

Other silly questions...

1. USB or Ethernet ADSL modem? if USB, have you installed the (proprietary) driver (mgmt.o)? Also if USB, check the web sites to see if the chipset in your modem is supported in the product you're using (you may need to go to Smoothwall 2.0 beta to get support for some USB chipsets, I understand)
2. Have you configured the green and red interfaces in Smoothwall correctly? (Red = ADSL, Green = LAN)
3. Have you specified the username and password etc. in the Smoothwall/IPCop configuration?
4. Have you looked at the logs to see what's going wrong? (Smoothwall can display them in the web interface... haven't tried IPCop, but I understand it's derived from Smoothwall and very similar)

HTH,
Gadget

bricks

You'll need a machine with 2 network cards.
Attach one network card to the Ethernet port on the Cable modem (Red). Attach the other to your Hub/Switch.(Green)
Use the Green+Red setup.
Now during setup set the Red interface to use DHCP.
(You don't need to fill in any ip addresses for DNS or gateways etc..)
Then set the Green interface up with something similar to the following addresses:
IP: 192.168.0.1
Subnet: 255.255.255.0
When you boot the machine up it should pick up a valid IP address on the Red interface via DHCP.
Type ifconfig to confirm this.
Also try pinging a few different IP addresses to confirm that the firewall is connecting okay to the internet.
Setup the PC's connected to the LAN with the following IP settings
IP: 192.168.0.2, 192.168.0.3 etc...
Subnet: 255.255.255.0
Gateway: 192.168.0.1
Nameserver: 192.168.0.1

As for anyone who has tested it, It should work fine but I haven't heard of anyone using it. I use Istream with it and it works okay.

bricks

http://mailman.lug.org.uk/pipermail/sderby/2002-September/000170.html

MagicBusDriver

Unless you have a spare pc around and plenty of time or are interested in unix a H/W router is alot less effort. Wingate is also good with many usefull features. Smoothwall is for techies and people with an understanding of unix and networking.