Help with router problem
eu9gu4 at gmail.com
Thu Feb 7 02:24:10 UTC 2008
I tried everything you guys told me and it still doesn't work :
- tried to set a static address as Derek indicated
- commented out the ipv6 line in rc.conf, even if it was already set to "NO"
- the answer to Kevin's questions follow:
# ping -I dc0 192.168.1.1
ping: invalid multicast interface: `dc0'
# arp -a
? (192.168.1.1) at (incomplete) on dc0 [ethernet]
# ifconfig -a
dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
inet 192.168.1.33 netmask 0xffffff00 broadcast 192.168.1.255
media: Ethernet autoselect (100baseTX <full-duplex>)
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
ping 192.168.1.1 and traceroute 192.168.1.1 give "Network is unreachable"
I even connected directly to the cable modem as it was before I bought the
router and... surprise: it works! Put the router back and BSD stops working
again. I'm writing this post from Linux, so this one works.
The /etc/hosts and /etc/dhclient.conf are the original ones, coming from BSD
What else can I do ?
On Feb 6, 2008 8:36 AM, Derek Ragona <derek at computinginnovations.com> wrote:
> At 07:40 AM 2/6/2008, Eugen wrote:
> Thanks for all your input. For now I am posting my rc.conf, but I will try
> your suggestions this evening when I come back from work.
> If anyone needs additional details, please ask and I'll repost my
> initial cry for help.
> ### Console options
> ### Mouse daemon
> ### IPv6 options
> ### PF firewall
> # pf_enable="YES" # Enable PF (load
> module if required)
> # pf_flags="" #
> additional flags for pfctl startup
> # pf_rules="/etc/pf.conf" # rules
> definition file for pf
> # pflog_enable="YES" # start pflogd(8)
> # pflog_flags="" # additional
> flags for pflogd startup
> # pflog_logfile="/var/log/pflog" # where pflogd
> should store the logfile
> ### Miscellaneous administrative options
> kern_securelevel="-1" # range: -1..3 ;
> `-1' is the most insecure
> kern_securelevel_enable="NO" # kernel security level
> (see init(8)),
> clear_tmp_enable="YES" # Clear /tmp at startup.
> devfs_system_ruleset="devfsrules_local" # The name of a ruleset to apply to
> dmesg_enable="YES" # Save dmesg(8) to
> update_motd="YES" # update version
> info in /etc/motd (or NO)
> virecover_enable="NO" # Perform
> housekeeping for the vi(1) editor
> usbd_enable="YES" # Run the usbd daemon.
> usbd_flags="" # Flags to
> usbd (if enabled).
> I almost always set my FreeBSD systems up to use a static IP, even behind a
> router. I don't know if you want to access your FreeBSD system from ONLY
> the LAN, or if you want some access through your router. I prefer a static
> IP on my FreeBSD systems as they are all providing some server functions
> (file sharing, DNS, etc.)
> Below are typical lines you would have in your /etc/rc.conf:
> #set the default router to your router's IP, often 192.168.1.1
> #set your hostname to match the enty in /etc/hosts
> #set your IP to one not in any DHCP range
> ifconfig_dc0="inet 192.168.1.10 netmask 255.255.255.0"
> These are all you need to get it working.
> If you want the FreeBSD to have a LAN address but access through the router
> you need to set that up in your router.
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> MailScanner thanks transtec Computers for their support.
More information about the freebsd-questions