Network Configuration - Revision history

Tigersharke at 06:57, 24 April 2013

2013-04-24T06:57:38Z

Tigersharke at 10:27, 22 April 2013

2013-04-22T10:27:07Z

Drulavigne at 16:00, 16 April 2013

2013-04-16T16:00:04Z

Drulavigne: Marked this version for translation

2013-04-12T19:36:31Z

Marked this version for translation

Show changes

Drulavigne at 19:36, 12 April 2013

2013-04-12T19:36:23Z

Tigersharke at 11:02, 1 April 2013

2013-04-01T11:02:23Z

Tigersharke: Fairly decent until images themselves are changed (ie resolution/size).

2013-03-02T10:27:18Z

Fairly decent until images themselves are changed (ie resolution/size).

Show changes

Tigersharke: /* Known Issues */

2013-02-19T09:58:15Z

‎Known Issues

Tigersharke: /* Useful Files and Commands */

2013-02-19T09:46:48Z

‎Useful Files and Commands

Tigersharke: /* Useful Files and Commands */

2013-02-19T09:45:35Z

‎Useful Files and Commands

@@ Line 1: / Line 1: @@
-<translate>
+<noinclude><translate>
 <!--T:1-->
-<noinclude>{{NavHeader|back=Scanner|forward=Firewall Manager}}</noinclude>
+{{NavHeader|back=Scanner|forward=Firewall Manager}}</noinclude>
 <!--T:2-->
@@ Line 366: / Line 366: @@
 <noinclude>
 {{refheading}}
 [[category:Network Configuration]]
 [[category:troubleshooting]]
 </translate>
 <languages/>

← Older revision		Revision as of 10:27, 22 April 2013
Line 372:		Line 372:
	</noinclude>		</noinclude>
	</translate>		</translate>
		+	<languages/>

← Older revision		Revision as of 16:00, 16 April 2013
Line 1:		Line 1:
−	<translate><!--T:1-->	+	<translate>
		+
		+	<!--T:1-->
	<noinclude>{{NavHeader\|back=Scanner\|forward=Firewall Manager}}</noinclude>		<noinclude>{{NavHeader\|back=Scanner\|forward=Firewall Manager}}</noinclude>

@@ Line 1: / Line 1: @@
-<noinclude>{{NavHeader|back=Scanner|forward=Firewall Manager}}</noinclude>
+<translate><noinclude>{{NavHeader|back=Scanner|forward=Firewall Manager}}</noinclude>
 During installation, PC-BSD® configures your Ethernet interfaces to use DHCP and provides a [[Connect to a Wireless Network | post-install configuration screen to configure your wireless connection]]. In most cases, this means that your connected interfaces should "just work" whenever you use your PC-BSD® system.
@@ Line 266: / Line 266: @@
 [[category:troubleshooting]]
 </noinclude>

@@ Line 69: / Line 69: @@
 * '''WPA Enterprise:''' if you click WPA Enterprise then the ''Configure'' button, you will see the screen shown in Figure 8.15j. Select the authentication method (EAP-TLS, EAP-TTLS, or EAP-PEAP); input the EAP identity; browse for the CA certificate, client certificate and private key file; and input and verify the password.
-{{note|width=48.5%|if you are unsure which type of encryption is being used, ask the person who setup the wireless router. They should also be able to give you the value of any of the settings seen in these configuration screens.}}
+{{note|width=48.5%|icon64=if you are unsure which type of encryption is being used, ask the person who setup the wireless router. They should also be able to give you the value of any of the settings seen in these configuration screens.}}
 [[File:Network8a.jpeg|thumb|393px|'''Figure 8.15h: WEP Security Settings''']]
@@ Line 125: / Line 125: @@
 '''Enable wireless/wired failover via lagg0 interface:''' the {{citelink|url=http://www.freebsd.org/cgi/man.cgi?query=lagg|txt=lagg}} interface allows you to seamlessly switch between using an Ethernet interface and a wireless interface. If you want this functionality, check this box.
-{{note|width=48.5%|some users experience problems using lagg. If you have problems connecting to a network using an interface that previously worked, uncheck this box and remove any references to "lagg" in your ''/etc/rc.conf'' file.}}
+{{note|width=48.5%|icon64=some users experience problems using lagg. If you have problems connecting to a network using an interface that previously worked, uncheck this box and remove any references to "lagg" in your ''/etc/rc.conf'' file.}}
 If you make any changes within this window, click the ''Save'' button to apply them.
@@ Line 169: / Line 169: @@
 When reading through your own file, look for lines that begin with ''ifconfig''. For a wireless interface, also look for lines containing ''wlans''.
-{{note|width=48.5%|unlike Linux interface driver names, FreeBSD/PC-BSD® interface driver names indicate the type of chipset. Each driver name has an associated man page where you can learn which devices use that chipset and if there are any configuration options or limitations for the driver. When reading the man page, do not include the interface number. In the above example, you could read '''man em''' and '''man run'''.}}
+{{note|width=48.5%|icon64=unlike Linux interface driver names, FreeBSD/PC-BSD® interface driver names indicate the type of chipset. Each driver name has an associated man page where you can learn which devices use that chipset and if there are any configuration options or limitations for the driver. When reading the man page, do not include the interface number. In the above example, you could read '''man em''' and '''man run'''.}}
 '''/etc/wpa_supplicant.conf'''

@@ Line 284: / Line 284: @@
 The bge(4) Ethernet driver has a {{citelink|url=http://www.freebsd.org/cgi/query-pr.cgi?pr=155442|txt=known issue}} where the interface is seen but does not respond to networking requests. Carefully adding this line to ''/boot/loader.conf'' and rebooting should solve this issue.
- hw.pci.enable_msi="0"
+{{txtbox|box=hw.pci.enable_msi="0"}}
 <noinclude>{{refheading}}</noinclude>

@@ Line 232: / Line 232: @@
 This command lists the hardware that was probed during boot time and will indicate if the associated driver was loaded. If you wish to search the output of this command for specific information, pipe to '''grep''' as seen in the following examples:
-{{txtbox|wrap|box='''dmesg | grep Ethernet'''
+{{txtbox|wrap|box='''dmesg {{pipe}} grep Ethernet'''
 re0: <RealTek 8168/8111 B/C/CP/D/DP/E PCIe Gigabit Ethernet> port 0xc000-0xc0ff mem 0xd0204000-0xd0204fff,0xd0200000-0xd0203fff irq 17 at  device 0.0 on pci8
 re0: Ethernet address: 60:eb:69:0b:dd:4d

@@ Line 236: / Line 236: @@
 re0: Ethernet address: 60:eb:69:0b:dd:4d
-'''dmesg |grep re0'''
+'''dmesg {{pipe}} grep re0'''
 re0: <RealTek 8168/8111 B/C/CP/D/DP/E PCIe Gigabit Ethernet> port 0xc000-0xc0ff mem 0xd0204000-0xd0204fff,0xd0200000-0xd0203fff irq 17 at  device 0.0 on pci8
 re0: Using 1 MSI messages
@@ Line 247: / Line 247: @@
 re0: link state changed to UP
-'''dmesg | grep run0'''
+'''dmesg {{pipe}} grep run0'''
 run0: <1.0> on usbus3
 run0: MAC/BBP RT3070 (rev 0x0201), RF RT2020 (MIMO 1T1R), address 00:25:9c:9f:a2:30
@@ Line 256: / Line 256: @@
 If your interface does not show up in '''ifconfig''' or '''dmesg''', it is possible that a driver for this card is not provided with the operating system. If the interface is built into the motherboard of the computer, you can use the '''pciconf''' command to find out the type of card. Here is an example:
-{{txtbox|box='''pciconf -lv | grep Ethernet'''
+{{txtbox|box='''pciconf -lv {{pipe}} grep Ethernet'''
 device     = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)'
-'''pciconf -lv | grep wireless'''
+'''pciconf -lv {{pipe}} grep wireless'''
 device     = 'Realtek RTL8191SE wireless LAN 802.11N PCI-E NIC (RTL8191SE ?)'}}