Jim,
My Bering installs have always been pretty much out of the box as far as
Shorewall rules. I really doubt your basic setup is in conflict with
them. The first place I would look is at ip addressing. Are you using
the firewall as a dhcp server? In the past this was a default. Now I
think y
Jim,
My Bering installs have always been pretty much out of the box as far as
Shorewall rules. I really doubt your basic setup is in conflict with
them. The first place I would look is at ip addressing. Are you using
the firewall as a dhcp server? In the past this was a default. Now I
t
Jim,
Did you read the dnsmasq documentation in the Bering-uClibc section:
http://leaf.sourceforge.net/doc/guide/bucu-dnsmasq.html
I think the problem is that the provider's DNS servers are not passed to
dnsmasq (read the section "Using dnsmasq with dhcpcd").
Eric
> Jim,
>
>
> My Bering instal
Jim,
Did you read the dnsmasq documentation in the Bering-uClibc section:
http://leaf.sourceforge.net/doc/guide/bucu-dnsmasq.html
I think the problem is that the provider's DNS servers are not passed to
dnsmasq (read the section "Using dnsmasq with dhcpcd").
Eric
Thanks Eric.
I've l
Hello Jim,
>
> Thanks Eric.
>
>
> I've looked at the above guide but noticed that it instructs that the
> resolv-file should point to /etc/dhcpc/resolv.conf. There isn't a dhcpc
> directory in my /etc! Should I create one and add an empty resolv.conf
> file in it? I tried pointing resolv-file=/etc/
Thanks again, Eric
> The etc/dhcpc/resolv.conf is only created when you use the dhcpcd package.
> Because you didn't tell much about your setup I have to guess a bit:
> -You have a dynamic ip-address from your provider:
That's me!. My ISP assigns me a dynamic IP address. My firewall is connect
Hello Jim,
> It worked! But an oddity is that even though I uncommented the range of
> IP addresses
> to allocate starting at 192.168.1.1, my Win XP machine gets allocated
> 192.168.1.65.
> When I plug my Linux laptop in (with the Win XP machine still connected),
> it gets 192.168.1.2. So why does
> Whilst I can ssh into the firewall (very useful) I can't access it with a
> browser. I've noticed that my syslog file has entries "cannot execute
> /usr/sbin/sh-httpd: no such file
> or directory". I guess that it ought to be mini-httpd that should be
> called. I've tried starting mini-htt
>The only piece of the jigsaw that needs sorting out now is a NAT problem
with
my Azereus bittorrent client. I guess it needs a line in
/etc/shorewall/rules
to allow UDP connections on port 6881 (but I might change the port).
Jim,
If using the bittorent client on an internal machine, the rule lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Spakman wrote:
| Hello Jim,
|
|> It worked! But an oddity is that even though I uncommented the range of
|> IP addresses
|> to allocate starting at 192.168.1.1, my Win XP machine gets allocated
|> 192.168.1.65.
|> When I plug my Linux laptop in
Charles Steinkuehler wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Spakman wrote:
| Hello Jim,
|
On your windows box, try the following at a prompt:
Or, if you really want your windows box to get a consistent IP, just
add a
stanza for it in the dhcpd config file:
~host mywi
11 matches
Mail list logo
