Re: Comcast/@Home cable modems with OpenBSD/ connected finally

[Paul Greene <pgreene_(_at_)_patriot_(_dot_)_net>]

I think I resolved my own problem .............

I changed the line in ipnat.rules from -

>> map dc0 192.168.0.0/24  -> dc0/32  portmap  tcp/udp  10000:20000

to

map dc0 192.168.0.0/24 -> "my-comcast-ip-address"/32 portmap tcp/udp 
10000:20000

and also pinged the news server and mail server to get their actual IP 
address, and entered those in the news and e-mail program setup, and all 
worked fine after that.

I don't know technically what did the trick; I don't see how using 
numerical IP addresses would have solved the problem (if I could ping it 
with the host name, and get the IP address, I don't think it would be a DNS 
problem (?)), but the small change in ipnat.rules doesn't seem that 
significant either.

If someone can answer the question "why", I'd love to hear it.

Paul Greene


> and then all the systems had no problem at all connecting to web access. 
> No firewalling has been enabled yet (that'll be the next step).
>
> All web access to the rest of my home LAN worked great (6 systems total; a 
> mix of Windows, Linux, and Openbsd), and I'm able to retrieve e-mail from 
> my old ISP no problems.
>
> However, I can't get through with any newsgroup access now, at least using 
> Free Agent on the Win2K box. The error message is "you do not have connect 
> permissions in the access file". I suspect the NAT on the OpenBSD box is 
> messing up the newsgroup connection. I did call the @Home tech support; 
> naturally they didn't have a clue as to what to do with it.
>
> Anyone know of a solution?
>
> Paul Greene
>
> At 06:01 PM 8/1/2001 -0400, you wrote:
> > Paul,
> >
> > No problems at all. Works a lot better than my previous Verizon ADSL
> > hookup. I'm in Wilmington DE, but I setup my sister with the same type
> > of configs (She lives in Falls Church).
> >
> > You use dhcp to get an IP lease, but they don't change your IP address.
> > You just send them your hostname and you get back your IP and DNS info.
> > Here is my dhclient.conf file (I xx'd out my hostname):
> >
> > # $OpenBSD: dhclient.conf,v 1.1 1998/09/08 20:26:41 marc Exp $
> > #
> > # DHCP Client Configuration
> > #
> > # See dhclient.conf(5) for possible contents of this file.
> > initial-interval 1;
> > send host-name "xxxxxxx.newcas1.de.home.com";
> > request subnet-mask, broadcast-address, routers,
> >        domain-name, domain-name-servers, host-name;
> >
> > Paul Hartzler http://256.2y.net http://ignatius.2y.net http://ijr.2y.net
> > =============================================
> >  There are two types of people in this world who are hated: Those who
> > succeed and those who fail...
> >
> > ----- Original Message -----
> > From: "Paul Greene" <pgreene_(_at_)_patriot_(_dot_)_net>
> > To: <misc_(_at_)_openbsd_(_dot_)_org>
> > Sent: Wednesday, August 01, 2001 4:50 PM
> > Subject: Comcast/@Home cable modems with OpenBSD
> >
> >
> > > Hi;
> > >
> > > By chance, anyone on the list using the Comcast/@Home cable modem
> > service
> > > with OpenBSD?
> > >
> > > (Preferably, someone in the Metro DC/Northern Virginia area)
> > >
> > > I'd like to get some feedback/suggestions as to any service issues
> > with
> > > these guys and OpenBSD, any technical glitches encountered (and
> > hopefully
> > > overcome), etc etc.
> > >
> > > Feel free to contact me offline to avoid unnecessary list noise.
> > >
> > > Thanks
> > >
> > > Paul Greene