FreeBSDwiki - User contributions [en]

Network, troubleshooting

2005-09-23T21:04:10Z

213.83.138.185:

If you suddenly can't get to the internet, the best thing to do is to find out exactly what's broken first. Makes sense, right?
So, a quick checklist of things:
# run [[ifconfig]] and see the state of your interfaces; if a cable's come unplugged, you'll see that the interface isn't connected.
# ping your gateway to see if it's your LAN that's down
# ping something on the other side of your gateway (something in another subnet or outside your network, for example).
# ping a known-pingable IP address on the internet. If you can ping 216.239.37.99 but not google.com, then you know something is wrong with your [[DNS]]. Other public places that respond to public pings are: cisco.com, yahoo.com, apple.com, google.com and freebsdwiki.net. It might not be a bad idea to write down the IP addresses of one or two of those places for future reference.
# If it's been narrowed down to DNS, find out if it's your DNS or the DNS lookup itself that's causing a problem: try using [[dig]] or [[nslookup]] to do lookups against another DNS server.

[[Category : New_User_Tips_and_FAQs ]]

Talk:Firewall, Configuring

2005-09-07T21:10:40Z

213.83.138.185: Start/stop

ok, so how do you start and stop the firewall? In linux it's a simple "iptables stop" (or start) -- or the redhat dumbed down version is "service iptables stop"....curious how it's done in FreeBSD (haven't had a need to put a FW on one yet...)

--[[User:Dave|Dave]] 10:58, 6 Sep 2005 (EDT)

== also, typo? ==

# let everything on your internal network talk to the firewall
$cmd 01101 allow all from any to any via $iif keep-state

shouldn't this be
# let everything on your internal network talk to the firewall
$cmd 01101 allow all from $inside to any via $iif keep-state

== $inside to any via $iif ==

If you're concerned with preventing address spoofing FROM your internal network going OUT to the real world, yes.

I tend to prefer my firewalls to let me-the-user do pretty much anything I want to, as a general rule. It shouldn't really make a whole lot of difference, in practice. --[[User:Jimbo|Jimbo]] 00:13, 7 Sep 2005 (EDT)

== starting and stopping the firewall ==

There isn't any real "omg this stops and starts it" sort of command - you just issue the rule commands you want, either directly from the command line or from a script.

For instance that ruleset in the article? Notice that the first line is #!/bin/sh - you guessed it, it's a Bourne shell script, so to start a firewall with that ruleset you would just run that script. You have to define what a "stopped" condition is before I can tell you how to "stop" the firewall. By "stop the firewall" do you mean "drop all traffic" or "pass all traffic"? --[[User:Jimbo|Jimbo]] 00:17, 7 Sep 2005 (EDT)

== Start/stop ==

In this article, the IPFW is loaded via the kernel, if the firewall was loaded via kernel module, you could issue a "kldunload ipfw.ko".

PuTTY

2005-08-31T19:40:03Z

213.83.138.185: